Sending to the list: Daniel Lenski wrote: > > On that note, is there a way to identify the ucode-version of b43 > firmware without reloading the b43 driver?
The dmesg output has it. > A quick glance at the drivers/net/wireless/b43/main.c suggests that the > driver actually loads the firmware, then queries the device for its > version number... but maybe there's some kind of heuristic? The ucode file that is loaded is dictated by the revision number of the 802.11 core. The output from 'dmesg | egrep "ssb|b43"' on my system shows the following: ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x16, vendor 0x4243) ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x0F, vendor 0x4243) ssb: Core 2 found: PCMCIA (cc 0x80D, rev 0x0A, vendor 0x4243) ssb: Core 3 found: PCI-E (cc 0x820, rev 0x09, vendor 0x4243) ssb: Found rev 1 PMU (capabilities 0x02A62F01) ssb: SPROM revision 8 detected. ssb: Sonics Silicon Backplane found on PCI device 0000:04:00.0 b43-phy0: Broadcom 4312 WLAN found (core revision 15) b43-phy0 debug: Found PHY: Analog 6, Type 5, Revision 1 b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2062, Revision 2 b43 ssb0:0: firmware: requesting b43/ucode15.fw b43 ssb0:0: firmware: requesting b43/lp0initvals15.fw b43 ssb0:0: firmware: requesting b43/lp0bsinitvals15.fw b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23) Note that 0x0F in ssb core 1 => ucode15. The version is stored within that file. A number of different versions are likely to work with a given card. In fact, there may not be any difference in the ucode5 file between firmware version 410.XXX and 508.XXX. One would have to look at the binary differences to tell if anything other that the version number had changed. Larry _______________________________________________ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
