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
SVN-Revision: 30422
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>
SVN-Revision: 26949
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)
SVN-Revision: 26801
Hauke Mehrtens