Has Ralf seen the arch/mips patches?
On Sun, Feb 19, 2012 at 07:32:14PM +0100, Hauke Mehrtens wrote:
> This patch series fixes some errors in the sprom structures and extends
> it to contain members for all sprom values for sprom version 1 to 9.
> This was done by looking into the open source part of the Broadcom SDK.
> This also adds a fallback sprom registration method to bcma.
> It also contains some small fixes for the bcma47xx arch code and a
> rewrite of the code to provide the sprom from flash. It now also
> provides sprom from flash for devices using bcma to control the system
> This patch series is based on wireles-testing. I think it is the best
> way to merge this through John's wireless tree as the changes in the
> sprom struct should be used in further patches extending the pci sprom
> parsing and the usage of struct sprom by the brcmsmac driver.
> Hauke Mehrtens (11):
> ssb: sprom fix some sizes / signedness
> ssb: remove 5GHz antenna gain from sprom
> ssb: fix per path sprom vars
> ssb: add ccode
> ssb: add some missing sprom attributes
> bcma: export bcma_find_core
> bcma: add support for sprom not found on the device.
> MIPS: BCM47XX: return number of written bytes in nvram_getenv
> MIPS: BCM47XX: fix signature of nvram_parse_macaddr
> MIPS: BCM47XX: move and extend sprom parsing
> MIPS: BCM47XX: provide sprom to bcma bus
> arch/mips/bcm47xx/Makefile | 2 +-
> arch/mips/bcm47xx/nvram.c | 3 +-
> arch/mips/bcm47xx/setup.c | 188 ++-------
> arch/mips/bcm47xx/sprom.c | 618
> arch/mips/include/asm/mach-bcm47xx/bcm47xx.h | 3 +
> arch/mips/include/asm/mach-bcm47xx/nvram.h | 2 +-
> drivers/bcma/main.c | 3 +-
> drivers/bcma/sprom.c | 75 +++-
> drivers/net/wireless/b43legacy/phy.c | 2 +-
> drivers/ssb/pci.c | 40 +--
> drivers/ssb/pcmcia.c | 12 +-
> drivers/ssb/sdio.c | 12 +-
> include/linux/bcma/bcma.h | 7 +
> include/linux/ssb/ssb.h | 102 ++++-
> 14 files changed, 844 insertions(+), 225 deletions(-)
> create mode 100644 arch/mips/bcm47xx/sprom.c
John W. Linville Someday the world will need a hero, and you
email@example.com might be all we have. Be ready.