Hardcoding channel number to 11 is a bad idea, it may be even not
available on some devices. If there are two single-band radios, the
one for 5GHz doesn't have 11 channel.
Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@36479 3c298f89-4303-0410-b956-a3cf2f4a3e73
wl_attach expects a physical address, as it performs the mapping internally.
Signed-off-by: Nathan Hintz <nlhintz@hotmail.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@34671 3c298f89-4303-0410-b956-a3cf2f4a3e73
* The device should get a unique name at the beginning and not wl%d.
* load the nvram just one time into the own buffer, also when there is
more than one device.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@34381 3c298f89-4303-0410-b956-a3cf2f4a3e73
When using the Broadcom SDK the SSB bus is emulated as an PCI bus so
the PCI bus number of the first real pci bus is increased by one. The
variable names in the nvram are created with that structure in mind. To
fix this we have ti increases the pci bus number by one. This was also
done for ssb some time ago.
This is based on a patch by nlh.
This closes#10917
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@30422 3c298f89-4303-0410-b956-a3cf2f4a3e73
* this adds sflash support for ssb devices
* the flash is now a platform device
* minor updates
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@27902 3c298f89-4303-0410-b956-a3cf2f4a3e73
- refresh and reorder patches
- introduce a unified BCMA/SSB glue driver to accomodate for both bus types on brcm47xx
- extend wlunbind init script to detach device from bcma-pci-bridge as well
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@27751 3c298f89-4303-0410-b956-a3cf2f4a3e73
broadcom-wl driver bound to ssb device with ssb driver probe
have osh handle struct pdev pointer value initialized with
ssb_device pointer. Later on pdev is used with legacy pci
dma api as pci_dev thus causing oops sometimes.
The patch replaces legacy pci dma api and pass relevant
device struct pointer to avoid crashes.
Signed-off-by: George Kashperko <george@znau.edu.ua>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@26949 3c298f89-4303-0410-b956-a3cf2f4a3e73
It was causing an occasional kernel oops.
Signed-off-by: Nathan Hintz <nlhintz@hotmail.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@26948 3c298f89-4303-0410-b956-a3cf2f4a3e73
If there is no sprom on an ssb based pci device on the brcm47xx
architecture ssb now asks the architecture code to look into the nvram
to get some sprom data for this device. Now we are able to read out
pci/1/1/ foo or pci/1/3/ foo config options.
This will fix some problems where the wireless devices does not got an
mac address and the following message was show:
ssb: WARNING: Invalid SPROM CRC (corrupt SPROM)
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@26801 3c298f89-4303-0410-b956-a3cf2f4a3e73
For kernel 2.6.36 some additional pcmcia backpots would be needed, but
this should not depend on pcmcia.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@23899 3c298f89-4303-0410-b956-a3cf2f4a3e73
- update to v5.10.56.27.3
- get fallback SPROM from SSB if neither on-device SPROM nor nvram is available
- working brcm63xx support
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@22173 3c298f89-4303-0410-b956-a3cf2f4a3e73
This will allow us to get rid of brcm-2.4 soon.
[ ... and there was much rejoicing ]
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@21809 3c298f89-4303-0410-b956-a3cf2f4a3e73
Hauke Mehrtens
Florian Fainelli
Jo-Philipp Wich
Felix Fietkau
Claudio Mignanti
Nicolas Thill
Gabor Juhos