On Friday 18 April 2008 17:51:29 Stefanik Gábor wrote:
> Bisection complete!
> After testing numerous settings for BoardFlags, I found that the only ones
> to have a benefical effect on the card is 0x4049/0x4249 and 0x0048/0x0248,
> which differs from the original 0x0049 only in the BFL_BTCMOD bit, which is
> 0 by default, but 1 in this configuration. Not only that, setting BoardFlags
> to 0x4049 and leaving everything else as is in the original Asus SPROM fixes
> BOTH the "No TX" and the "ping time cycle" bugs! Even
> monitoring/packetspamming while operating works perfectly. The setting
> 0x4249 produces the same (perfectly-working) result, only with Afterburner
> marked as supported. (Not sure if it actually gets enabled, though.) Setting

The afterburner bit is not used in the driver.

> BFL_FEM to 1 (0x4849 or 0x4A49) introduces the "ping cycle" bug, most likely
> because the card doesn't actually support the Front-End Module. BFL_HGPA=1
> (0x6049/0x6249) causes ping packet loss /duplicate count to increase
> somewhat, likely because the card doesn't have a high-gain PA. 0x0048 and
> 0x0248 also work fine, although this setting disables Bluetooth coexistence
> (BFL_BTCOEXIST).

As the card doesn't have a BT chip, this is the correct thing to do.

> So, it looks like BoardFlags was intended to be 0x4249, but 

I'm not too sure on the afterburner bit. The packaging box of my card
does not tell anything about supported rates beyond 54MBit. So it most
likely does not support afterburner.

> Asus incorrectly sets it to 0x0049, which completely breaks transmission in
> b43.
> 

> "0x0001: BFL_BTCOEXIST: Board implements Bluetooth coexistance[sic]". I
> don't know if "coexistance" is a misspelling or if it's the correct spelling
> in British, but if it's unintended, then it should be fixed. (Just
> nit-picking, sorry.)

That bit is most likey what is actually the wrong one.

-- 
Greetings Michael.
_______________________________________________
Bcm43xx-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Reply via email to