BCM5354 SoC with LP Phy Wifi

BCM5354 SoC with LP Phy Wifi

[Hauke Mehrtens]

I got a device with a BCM5354 SoC and a LP-Phy Wifi core on it. With
current b43 it still fails with Out of memory when using a recent
firmware 666.2 and works with an old firmware 410.2160. I tried DMA and
PIO mode and had the same results. I added some printk's into the code
and implemented some parts b43 does not have but the Braodcom sdk and
brcmsmac has in the dma code, but I haven't resolved the issue.

I found out the error occurs when send some packages doing "ifconfig
wlan0 up" does not result in any problems, but when I try to scan with
"iw wlan0 scan" it oopes very soon. The problem seams to be related to
TX as there are many packages received, but the oops occurs after 4
calls to b43_dma_tx()

Larry, you wrote some more LP spec based on a newer driver is there a
list with updated docs or should I manually look into all packages if I
want to implement it like it is in the new wl driver.
As I see there are also many parts not implemented, but described in the
spec so looking over the hole code is probably needed.
My device has a sprom of revision 3 and not the expected version 8, does
this cause any trouble?

Hauke.

BCM5354 SoC with LP Phy Wifi

[Hauke Mehrtens]

On 01/29/2012 11:12 PM, Hauke Mehrtens wrote:
> I got a device with a BCM5354 SoC and a LP-Phy Wifi core on it. With
> current b43 it still fails with Out of memory when using a recent
> firmware 666.2 and works with an old firmware 410.2160. I tried DMA and
> PIO mode and had the same results. I added some printk's into the code
> and implemented some parts b43 does not have but the Braodcom sdk and
> brcmsmac has in the dma code, but I haven't resolved the issue.
> 
> I found out the error occurs when send some packages doing "ifconfig
> wlan0 up" does not result in any problems, but when I try to scan with
> "iw wlan0 scan" it oopes very soon. The problem seams to be related to
> TX as there are many packages received, but the oops occurs after 4
> calls to b43_dma_tx()
> 
> Larry, you wrote some more LP spec based on a newer driver is there a
> list with updated docs or should I manually look into all packages if I
> want to implement it like it is in the new wl driver.
> As I see there are also many parts not implemented, but described in the
> spec so looking over the hole code is probably needed.
> My device has a sprom of revision 3 and not the expected version 8, does
> this cause any trouble?
> 
> Hauke.
My device is the following:

ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x14, vendor 0x4243)
ssb: Core 1 found: Fast Ethernet (cc 0x806, rev 0x09, vendor 0x4243)
ssb: Core 2 found: MIPS 3302 (cc 0x816, rev 0x08, vendor 0x4243)
ssb: Core 3 found: USB 2.0 Host (cc 0x819, rev 0x02, vendor 0x4243)
ssb: Core 4 found: MEMC SDRAM (cc 0x80F, rev 0x04, vendor 0x4243)
ssb: Core 5 found: IEEE 802.11 (cc 0x812, rev 0x0D, vendor 0x4243)
ssb: Core 6 found: Roboswitch (cc 0x81C, rev 0x02, vendor 0x4243)

b43-phy0: Broadcom 5354 WLAN found (core revision 13)
b43-phy0 debug: Found PHY: Analog 6, Type 5, Revision 0
b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2062, Revision 1

When doing a passive scan with iw it works without any problems and I
get my results without any kernel oops, but when doing an active scan I
get an oops.

Hauke

BCM5354 SoC with LP Phy Wifi

[Rafał Miłecki]

2012/1/30 Hauke Mehrtens <hauke@hauke-m.de>:
> On 01/29/2012 11:12 PM, Hauke Mehrtens wrote:
>> I got a device with a BCM5354 SoC and a LP-Phy Wifi core on it. With
>> current b43 it still fails with Out of memory when using a recent
>> firmware 666.2 and works with an old firmware 410.2160. I tried DMA and
>> PIO mode and had the same results. I added some printk's into the code
>> and implemented some parts b43 does not have but the Braodcom sdk and
>> brcmsmac has in the dma code, but I haven't resolved the issue.
>>
>> I found out the error occurs when send some packages doing "ifconfig
>> wlan0 up" does not result in any problems, but when I try to scan with
>> "iw wlan0 scan" it oopes very soon. The problem seams to be related to
>> TX as there are many packages received, but the oops occurs after 4
>> calls to b43_dma_tx()
>>
>> Larry, you wrote some more LP spec based on a newer driver is there a
>> list with updated docs or should I manually look into all packages if I
>> want to implement it like it is in the new wl driver.
>> As I see there are also many parts not implemented, but described in the
>> spec so looking over the hole code is probably needed.
>> My device has a sprom of revision 3 and not the expected version 8, does
>> this cause any trouble?
>>
>> Hauke.
> My device is the following:
>
> ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x14, vendor 0x4243)
> ssb: Core 1 found: Fast Ethernet (cc 0x806, rev 0x09, vendor 0x4243)
> ssb: Core 2 found: MIPS 3302 (cc 0x816, rev 0x08, vendor 0x4243)
> ssb: Core 3 found: USB 2.0 Host (cc 0x819, rev 0x02, vendor 0x4243)
> ssb: Core 4 found: MEMC SDRAM (cc 0x80F, rev 0x04, vendor 0x4243)
> ssb: Core 5 found: IEEE 802.11 (cc 0x812, rev 0x0D, vendor 0x4243)
> ssb: Core 6 found: Roboswitch (cc 0x81C, rev 0x02, vendor 0x4243)
>
> b43-phy0: Broadcom 5354 WLAN found (core revision 13)
> b43-phy0 debug: Found PHY: Analog 6, Type 5, Revision 0
> b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2062, Revision 1
>
> When doing a passive scan with iw it works without any problems and I
> get my results without any kernel oops, but when doing an active scan I
> get an oops.

If you search for "out of memory b43" you will find the thread where
we were trying to find the issue. Unfortunately without the real
access to the hardware it wasn't easy to debug this. Sending patches
to someone, waiting for recompiling & testing, checking results... I
failed at that process :(

While I'll try to implement/update LP-PHY code, I think it still would
be nice to investigate this problem. Do we have some leak in b43? We
should fix it if so.

Could you check what exactly happens in b43_dma_tx please?

-- 
Rafa?

BCM5354 SoC with LP Phy Wifi

[Hauke Mehrtens]

On 01/30/2012 07:29 AM, Rafa? Mi?ecki wrote:
> 2012/1/30 Hauke Mehrtens <hauke@hauke-m.de>:
>> On 01/29/2012 11:12 PM, Hauke Mehrtens wrote:
>>> I got a device with a BCM5354 SoC and a LP-Phy Wifi core on it. With
>>> current b43 it still fails with Out of memory when using a recent
>>> firmware 666.2 and works with an old firmware 410.2160. I tried DMA and
>>> PIO mode and had the same results. I added some printk's into the code
>>> and implemented some parts b43 does not have but the Braodcom sdk and
>>> brcmsmac has in the dma code, but I haven't resolved the issue.
>>>
>>> I found out the error occurs when send some packages doing "ifconfig
>>> wlan0 up" does not result in any problems, but when I try to scan with
>>> "iw wlan0 scan" it oopes very soon. The problem seams to be related to
>>> TX as there are many packages received, but the oops occurs after 4
>>> calls to b43_dma_tx()
>>>
>>> Larry, you wrote some more LP spec based on a newer driver is there a
>>> list with updated docs or should I manually look into all packages if I
>>> want to implement it like it is in the new wl driver.
>>> As I see there are also many parts not implemented, but described in the
>>> spec so looking over the hole code is probably needed.
>>> My device has a sprom of revision 3 and not the expected version 8, does
>>> this cause any trouble?
>>>
>>> Hauke.
>> My device is the following:
>>
>> ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x14, vendor 0x4243)
>> ssb: Core 1 found: Fast Ethernet (cc 0x806, rev 0x09, vendor 0x4243)
>> ssb: Core 2 found: MIPS 3302 (cc 0x816, rev 0x08, vendor 0x4243)
>> ssb: Core 3 found: USB 2.0 Host (cc 0x819, rev 0x02, vendor 0x4243)
>> ssb: Core 4 found: MEMC SDRAM (cc 0x80F, rev 0x04, vendor 0x4243)
>> ssb: Core 5 found: IEEE 802.11 (cc 0x812, rev 0x0D, vendor 0x4243)
>> ssb: Core 6 found: Roboswitch (cc 0x81C, rev 0x02, vendor 0x4243)
>>
>> b43-phy0: Broadcom 5354 WLAN found (core revision 13)
>> b43-phy0 debug: Found PHY: Analog 6, Type 5, Revision 0
>> b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2062, Revision 1
>>
>> When doing a passive scan with iw it works without any problems and I
>> get my results without any kernel oops, but when doing an active scan I
>> get an oops.
> 
> If you search for "out of memory b43" you will find the thread where
> we were trying to find the issue. Unfortunately without the real
> access to the hardware it wasn't easy to debug this. Sending patches
> to someone, waiting for recompiling & testing, checking results... I
> failed at that process :(
Yeah this will work with obvious bugs, but this seams to be hard bug. I
will investigate deeper into it.
> 
> While I'll try to implement/update LP-PHY code, I think it still would
> be nice to investigate this problem. Do we have some leak in b43? We
> should fix it if so.
I haven't found a leak in b43 yet, just one in an OpenWrt switch driver,
while searching in b43. ;-)
It's nice to hear that you will work on the LP-PHY part, to me it looks
like ~30% of the spec is not implemented. have you started implementing
the GMAC Ethernet driver?
> 
> Could you check what exactly happens in b43_dma_tx please?
Yes I will look deeper into this.
Do you have a working LP-PHY device, so that I could give you some
patches and then compare the output?

Hauke

BCM5354 SoC with LP Phy Wifi

[Rafał Miłecki]

W dniu 30 stycznia 2012 20:45 u?ytkownik Hauke Mehrtens
<hauke@hauke-m.de> napisa?:
> On 01/30/2012 07:29 AM, Rafa? Mi?ecki wrote:
>> While I'll try to implement/update LP-PHY code, I think it still would
>> be nice to investigate this problem. Do we have some leak in b43? We
>> should fix it if so.
> I haven't found a leak in b43 yet, just one in an OpenWrt switch driver,
> while searching in b43. ;-)
> It's nice to hear that you will work on the LP-PHY part, to me it looks
> like ~30% of the spec is not implemented. have you started implementing
> the GMAC Ethernet driver?

I've started fighting with my router. I've tested it's working (on
original firmware), I'm trying now to get root access to get
partitions layout. I've already opened it (this required small Torx
screwdriver) and built 3,3V console. I'm working on creating console
pins (unfortunately they were removed from production==non-beta
boards).


>> Could you check what exactly happens in b43_dma_tx please?
> Yes I will look deeper into this.
> Do you have a working LP-PHY device, so that I could give you some
> patches and then compare the output?

My LP-PHY had some performance problems, probably some important
calibration is missing.

-- 
Rafa?

BCM5354 SoC with LP Phy Wifi

[Hauke Mehrtens]

On 01/30/2012 09:37 PM, Rafa? Mi?ecki wrote:
> W dniu 30 stycznia 2012 20:45 u?ytkownik Hauke Mehrtens
> <hauke@hauke-m.de> napisa?:
>> On 01/30/2012 07:29 AM, Rafa? Mi?ecki wrote:
>>> While I'll try to implement/update LP-PHY code, I think it still would
>>> be nice to investigate this problem. Do we have some leak in b43? We
>>> should fix it if so.
>> I haven't found a leak in b43 yet, just one in an OpenWrt switch driver,
>> while searching in b43. ;-)
>> It's nice to hear that you will work on the LP-PHY part, to me it looks
>> like ~30% of the spec is not implemented. have you started implementing
>> the GMAC Ethernet driver?
> 
> I've started fighting with my router. I've tested it's working (on
> original firmware), I'm trying now to get root access to get
> partitions layout. I've already opened it (this required small Torx
> screwdriver) and built 3,3V console. I'm working on creating console
> pins (unfortunately they were removed from production==non-beta
> boards).
I had the same problem with my Netgear device on the pictures made by
the FCC there are nice pins on the board and ASUS just leaves them there
for the production devices, but my Netgear devices did not had them.
The pin layout is probably the same as for the WNR3500L here:
http://wiki.openwrt.org/toh/netgear/wnr3500l

>>> Could you check what exactly happens in b43_dma_tx please?
>> Yes I will look deeper into this.
>> Do you have a working LP-PHY device, so that I could give you some
>> patches and then compare the output?
> 
> My LP-PHY had some performance problems, probably some important
> calibration is missing.

I got ~4MBit/s when running my device in AP mode with old firmware over
~0.5 meters.

Hauke

BCM5354 SoC with LP Phy Wifi

[Rafał Miłecki]

W dniu 2 lutego 2012 22:30 u?ytkownik Chris Martin <chris@martin.cc> napisa?:
> I have a device with a 5354 that I'm happy to donate.
> Can you let forward me a shipping address

Some time ago I was even trying to buy one but couldn't (it's a little
old hardware).

Let's first see what Hauke will discover. He's quite experienced
hacker, let's give him a chance :)

-- 
Rafa?

BCM5354 SoC with LP Phy Wifi

[Hauke Mehrtens]

On 01/30/2012 07:29 AM, Rafa? Mi?ecki wrote:
> 2012/1/30 Hauke Mehrtens <hauke@hauke-m.de>:
>> On 01/29/2012 11:12 PM, Hauke Mehrtens wrote:
>>> I got a device with a BCM5354 SoC and a LP-Phy Wifi core on it. With
>>> current b43 it still fails with Out of memory when using a recent
>>> firmware 666.2 and works with an old firmware 410.2160. I tried DMA and
>>> PIO mode and had the same results. I added some printk's into the code
>>> and implemented some parts b43 does not have but the Braodcom sdk and
>>> brcmsmac has in the dma code, but I haven't resolved the issue.
>>>
>>> I found out the error occurs when send some packages doing "ifconfig
>>> wlan0 up" does not result in any problems, but when I try to scan with
>>> "iw wlan0 scan" it oopes very soon. The problem seams to be related to
>>> TX as there are many packages received, but the oops occurs after 4
>>> calls to b43_dma_tx()
>>>
>>> Larry, you wrote some more LP spec based on a newer driver is there a
>>> list with updated docs or should I manually look into all packages if I
>>> want to implement it like it is in the new wl driver.
>>> As I see there are also many parts not implemented, but described in the
>>> spec so looking over the hole code is probably needed.
>>> My device has a sprom of revision 3 and not the expected version 8, does
>>> this cause any trouble?
>>>
>>> Hauke.
>> My device is the following:
>>
>> ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x14, vendor 0x4243)
>> ssb: Core 1 found: Fast Ethernet (cc 0x806, rev 0x09, vendor 0x4243)
>> ssb: Core 2 found: MIPS 3302 (cc 0x816, rev 0x08, vendor 0x4243)
>> ssb: Core 3 found: USB 2.0 Host (cc 0x819, rev 0x02, vendor 0x4243)
>> ssb: Core 4 found: MEMC SDRAM (cc 0x80F, rev 0x04, vendor 0x4243)
>> ssb: Core 5 found: IEEE 802.11 (cc 0x812, rev 0x0D, vendor 0x4243)
>> ssb: Core 6 found: Roboswitch (cc 0x81C, rev 0x02, vendor 0x4243)
>>
>> b43-phy0: Broadcom 5354 WLAN found (core revision 13)
>> b43-phy0 debug: Found PHY: Analog 6, Type 5, Revision 0
>> b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2062, Revision 1
>>
>> When doing a passive scan with iw it works without any problems and I
>> get my results without any kernel oops, but when doing an active scan I
>> get an oops.
> 
> If you search for "out of memory b43" you will find the thread where
> we were trying to find the issue. Unfortunately without the real
> access to the hardware it wasn't easy to debug this. Sending patches
> to someone, waiting for recompiling & testing, checking results... I
> failed at that process :(
> 
> While I'll try to implement/update LP-PHY code, I think it still would
> be nice to investigate this problem. Do we have some leak in b43? We
> should fix it if so.
> 
> Could you check what exactly happens in b43_dma_tx please?

I debugged my device again and found out that with the new firmware it
log 3 times this line:

b43-phy0 ERROR: b43_mac_enable(): The firmware should be suspended, but
current state is 0

This does not happen with firmware 410.2160. I haven't see any other
differences in the log. What could be the reason for this log entry?

Output with firmware 666.2, running "iw wlan0 scan passive" at first and
then "iw wlan0 scan"
http://hauke-m.de/files/bcm5354/2012-02-04/fail-1.log

Output with firmware 410.2160 running "iw wlan0 scan"
http://hauke-m.de/files/bcm5354/2012-02-04/working-1.log

Hauke

BCM5354 SoC with LP Phy Wifi

[Hauke Mehrtens]

On 02/04/2012 01:53 PM, Hauke Mehrtens wrote:
> On 01/30/2012 07:29 AM, Rafa? Mi?ecki wrote:
>> 2012/1/30 Hauke Mehrtens <hauke@hauke-m.de>:
>>> On 01/29/2012 11:12 PM, Hauke Mehrtens wrote:
>>>> I got a device with a BCM5354 SoC and a LP-Phy Wifi core on it. With
>>>> current b43 it still fails with Out of memory when using a recent
>>>> firmware 666.2 and works with an old firmware 410.2160. I tried DMA and
>>>> PIO mode and had the same results. I added some printk's into the code
>>>> and implemented some parts b43 does not have but the Braodcom sdk and
>>>> brcmsmac has in the dma code, but I haven't resolved the issue.
>>>>
>>>> I found out the error occurs when send some packages doing "ifconfig
>>>> wlan0 up" does not result in any problems, but when I try to scan with
>>>> "iw wlan0 scan" it oopes very soon. The problem seams to be related to
>>>> TX as there are many packages received, but the oops occurs after 4
>>>> calls to b43_dma_tx()
>>>>
>>>> Larry, you wrote some more LP spec based on a newer driver is there a
>>>> list with updated docs or should I manually look into all packages if I
>>>> want to implement it like it is in the new wl driver.
>>>> As I see there are also many parts not implemented, but described in the
>>>> spec so looking over the hole code is probably needed.
>>>> My device has a sprom of revision 3 and not the expected version 8, does
>>>> this cause any trouble?
>>>>
>>>> Hauke.
>>> My device is the following:
>>>
>>> ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x14, vendor 0x4243)
>>> ssb: Core 1 found: Fast Ethernet (cc 0x806, rev 0x09, vendor 0x4243)
>>> ssb: Core 2 found: MIPS 3302 (cc 0x816, rev 0x08, vendor 0x4243)
>>> ssb: Core 3 found: USB 2.0 Host (cc 0x819, rev 0x02, vendor 0x4243)
>>> ssb: Core 4 found: MEMC SDRAM (cc 0x80F, rev 0x04, vendor 0x4243)
>>> ssb: Core 5 found: IEEE 802.11 (cc 0x812, rev 0x0D, vendor 0x4243)
>>> ssb: Core 6 found: Roboswitch (cc 0x81C, rev 0x02, vendor 0x4243)
>>>
>>> b43-phy0: Broadcom 5354 WLAN found (core revision 13)
>>> b43-phy0 debug: Found PHY: Analog 6, Type 5, Revision 0
>>> b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2062, Revision 1
>>>
>>> When doing a passive scan with iw it works without any problems and I
>>> get my results without any kernel oops, but when doing an active scan I
>>> get an oops.
>>
>> If you search for "out of memory b43" you will find the thread where
>> we were trying to find the issue. Unfortunately without the real
>> access to the hardware it wasn't easy to debug this. Sending patches
>> to someone, waiting for recompiling & testing, checking results... I
>> failed at that process :(
>>
>> While I'll try to implement/update LP-PHY code, I think it still would
>> be nice to investigate this problem. Do we have some leak in b43? We
>> should fix it if so.
>>
>> Could you check what exactly happens in b43_dma_tx please?
> 
> I debugged my device again and found out that with the new firmware it
> log 3 times this line:
> 
> b43-phy0 ERROR: b43_mac_enable(): The firmware should be suspended, but
> current state is 0

This message is not show with firmware 478.104, but the memory problem
still exists, so this is probably unrelated.

> This does not happen with firmware 410.2160. I haven't see any other
> differences in the log. What could be the reason for this log entry?
> 
> Output with firmware 666.2, running "iw wlan0 scan passive" at first and
> then "iw wlan0 scan"
> http://hauke-m.de/files/bcm5354/2012-02-04/fail-1.log
> 
> Output with firmware 410.2160 running "iw wlan0 scan"
> http://hauke-m.de/files/bcm5354/2012-02-04/working-1.log

It looks to me that the memory leak is not in b43, but somewhere else.
I monitored every call from the workqueue, irq handler and the callbacks
from mac80211 and it is not loosing the memory in them.

Who could alloc some memory depending on the result of an tx?

An other log with firmware 478.104.
http://hauke-m.de/files/bcm5354/2012-02-04/fail-2.log

Hauke

BCM5354 SoC with LP Phy Wifi

[Hauke Mehrtens]

Hi William,

On 01/30/2012 04:39 PM, William R Agosto Padilla wrote:
> Mr. Hauke,
> 
> I am new to the reverse engineering process. However I am working on a
> project that
> requires me to use printk statements in the b43 device driver code, so I
> can see how it is
> really working during initialization, resetting, and suspension of the
> networking process. 
> 
> The first problem that I encountered was finding the b43 source code for
> download.
> I was only able to find the assembly code for the b43 firmware. Do you
> know of a specific download
> location where I can get the entire b43's ''C'' source code?
Just go to https://www.kernel.org/ and download the Linux kernel it has
b43 included in it in drivers/net/wireless/b43 or use
http://wireless.kernel.org/en/users/Download/stable/

>  Reading
> your email I realized that you
> have already done what I will be attempting to do. Mainly, using printk
> statements inside the b43 code.
> I have been at this for a couple of months without any luck. Would you
> mind if I ask a few questions 
> about the way you went about on doing so? Or advice on how to do it?
> 
> Did you added the printk statements into the b43 source code or the b43
> firmware code?
I do not have access to the source code of the broadcom firmware, but
there is an open source project developing an open Source firmware
http://www.ing.unibs.it/~openfwwf/
>I would like to try
> something similar. As I mentioned earlier, I was not able to see the
> b43's 'C' source code with my
> Linux Ubuntu 11.10 distribution. I found a copy of the firmware source
> code with the
> assembly language, etc. Is that the code that you used for the printk
> statements? 
I am just working on the driver and treating the firmware as a black box.
> I thought that since the b43 driver is included in the kernel that
> Ubuntu 11.10 has, it 
> would also include the source code--no luck with that.
> 
> Any insight that you can share would be very much appreciated.
> 
> Cheers
> 
> William

Hauke

BCM5354 SoC with LP Phy Wifi

[Rafał Miłecki]

2012/1/30 Hauke Mehrtens <hauke@hauke-m.de>:
> Hi William,
>
> On 01/30/2012 04:39 PM, William R Agosto Padilla wrote:
>> Mr. Hauke,
>>
>> I am new to the reverse engineering process. However I am working on a
>> project that
>> requires me to use printk statements in the b43 device driver code, so I
>> can see how it is
>> really working during initialization, resetting, and suspension of the
>> networking process.
>>
>> The first problem that I encountered was finding the b43 source code for
>> download.
>> I was only able to find the assembly code for the b43 firmware. Do you
>> know of a specific download
>> location where I can get the entire b43's ''C'' source code?
> Just go to https://www.kernel.org/ and download the Linux kernel it has
> b43 included in it in drivers/net/wireless/b43 or use
> http://wireless.kernel.org/en/users/Download/stable/
>
>> ?Reading
>> your email I realized that you
>> have already done what I will be attempting to do. Mainly, using printk
>> statements inside the b43 code.
>> I have been at this for a couple of months without any luck. Would you
>> mind if I ask a few questions
>> about the way you went about on doing so? Or advice on how to do it?
>>
>> Did you added the printk statements into the b43 source code or the b43
>> firmware code?
> I do not have access to the source code of the broadcom firmware, but
> there is an open source project developing an open Source firmware
> http://www.ing.unibs.it/~openfwwf/
>>I would like to try
>> something similar. As I mentioned earlier, I was not able to see the
>> b43's 'C' source code with my
>> Linux Ubuntu 11.10 distribution. I found a copy of the firmware source
>> code with the
>> assembly language, etc. Is that the code that you used for the printk
>> statements?
> I am just working on the driver and treating the firmware as a black box.
>> I thought that since the b43 driver is included in the kernel that
>> Ubuntu 11.10 has, it
>> would also include the source code--no luck with that.
>>
>> Any insight that you can share would be very much appreciated.

William, you're asking random people privately in random threads and
you're duplicating your questions.

If there is something we can explain to you, please just ask using
b43-devl mailing list. I'm sure you'll get some answers and we won't
waste our time responding on the questions you've already got
explained by sb else.

-- 
Rafa?