Search Linux Wireless

Broadcom sprom

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I had a look at the sprom parsing, as the SoC sprom parsing code is
dated and does not fill in some fields introduced in updates of struct
ssb_sprom. I had a look at the brcm/include/bcmsrom_tbl.h file found in
the Broadcom SoC SDK containing the positions and names of the sprom
values. For the old sprom versions <= 4 our struct ssb_sprom contains
mostly all fields available in the sprom, but for more recent it misses
some/many values. I searched brcmsmac for some of them and they are
mostly parsing the same values for v8 and v9 as the Broadcom SoC SDK
does, but they do not use all of them.

How should we proceed? Should I extend struct ssb_sprom to support all
sprom values available or found in the Broadcom SDK in sprom version 1
to 9 and add the parsing code to bcm47xx arch code, ssb (for old
versions) and bcma, or just the ones currently needed by any driver? As
even brcmsmac does not use all of them some seam to be unused at all.

As the struct would be under 1KB if we put in all sprom values we know
of I am for adding all these values into it and we do not have to deal
with sproms till version 10 is released. ;-)

What are you opinions about this?

Hauke
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux