Dale Walsh wrote:
>
> On Jun 12, 2008, at 05:16 AM, Michael Buesch wrote:
>
>> On Thursday 12 June 2008 04:20:04 Larry Finger wrote:
>>> Dale Walsh wrote:
>>>> I've been in touch with Broadcom a since I am considering having a card
>>>> OEM'ed and it was discussed acquiring the API and a framework for
>>>> driver
>>>> programming in a custom OS so now I'm just waiting on approval.
>>>>
>>>> Is there any other action I can take that would help???
>>>>
>>>> Here is some information on the 11n based cards I have, I'm working on
>>>> getting the b43 driver to recognize the card in the hopes that I can
>>>> obtain a dump of the sprom data in case it's usefull.
>>>
>>> I'm not sure the SPROM data will have any value at this time; however,
>>> you need to have ssb recognize the device in order to get to the SPROM
>>> values. That requires the PCI ID in ssb's tables. You will also need a
>>> fairly recent kernel (2.6.26-rcX) if the devices have a 400 byte SPROM
>>> that is not rev 4. It may be necessary for b43 to be loaded, but the
>>> SPROM can be read even if b43 doesn't recognize the device.
>>
>> You don't need to load b43. Just modify ssb, load it and read the sprom
>> via /sys/foobar/ssb_sprom
>>
>> --
>> Greetings Michael.
>>
>
> ok, got the new kernel (2.6.26-rc5) installed as recommended.
>
> Booted machine with WMP300N installed and did the following:
> _______________________________
>
> sudo -s
>
> uname -r
> 2.6.26.rc5-wifi-testing
>
> modprobe b43
>
> cd $(dirname $(find /sys/devices|grep sprom))
>
> cp ssb_sprom ${HOME}/orig_sprom; # try using cp
>
> ssb-sprom -i ${HOME}/orig_sprom -P
> Corrupt input data (crc: 0xA9, expected: 0xFF)
>
> rm ${HOME}/orig_sprom; # delete the file just in case
>
> cat ssb_sprom > ${HOME}/orig_sprom; # try using cat
>
> ssb-sprom -i ${HOME}/orig_sprom -P
> Corrupt input data (crc: 0xA9, expected: 0xFF)
>
> dmesg
> [19374.906129] ssb: Sonics Silicon Backplane found on PCI device
> 0000:04:00.0
> [19374.936377] b43-phy2: Broadcom 4321 WLAN found
> [19374.977459] b43-phy2 ERROR: FOUND UNSUPPORTED PHY (Analog 5, Type 4,
> Revision 1)
> [19374.977482] b43: probe of ssb0:0 failed with error -95
> [19374.977506] Broadcom 43xx driver loaded [ Features: PLR, Firmware-ID:
> FW13 ]
> _______________________________
>
> The results are the same for the WLI-PCI-G300N and as far as I can tell
> they physically appear to be the same card.
>
> I have verified by viewing the subsystem_device and subsystem_vendor
> files do contain the correct information for the installed card so I can
> confirm it is working to some degree, at least it's recognizing the cards.
>
> As I said, I don't need the wireless lan to be functional, just the
> ability to read/write the sprom data at this time.
For any SPROM not supported, ssb-sprom cannot handle it. If you 'cat
orig_sprom', you will get what you have. I expect it is a 440-byte
SPROM since ssb did not get a CRC error.
Be aware that you will have to figure out where the pertinent
information is located, and revise ssb-sprom to handle that revision
and layout before you will have any chance of modifying the data _AND_
update the CRC. If that is done wrong, and you write the SPROM with
faulty data, you will brick the device!
Larry
_______________________________________________
Bcm43xx-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
