On Tue, 10 Jan 2006 17:42:04 -0600 Travis Friesen <[EMAIL PROTECTED]> wrote:
> Forgive my gross ignorance of code and 802.11, but somethign still > does not seem right. Yes, I can see how it's beautifully optimized, > what with the fall through and all, but it begs for a closer look. Plus you shouldn't think the compiler is so dumb. It actually would have done a lot of optimizations, even if the code was written the other way around. > If we're using 802.11a, all the bitrates are set. Ok, I don't know > much about 802.11a, but let's assume that's right. No, it wasn't. IEEE 802.11a amendment states that only OFDM rates are supported. Actually, it looks like that this amendment - and the other ones, too - were written aiming to confuse people, but I hope I got it. Sure I got headache. However, this doesn't really matter, as A PHYs are far away from working with this driver. > if we're using 802.11g, all the bit rates get set. Definetly good. > > However, the problem appears to come if we're using 802.11b, because > instead of the standard 1,2,5,11, 802.11b gets 6,9,12, etc. Those are > the g standards. > > From my read of the snippet, the blocks beneath case BCM43xx_PHYTYPE_g > and case BCM43xx_PHYTYPE_b should be swapped, so that 11b gets only > 1,2,5,11 and not 6,9,etc Yes, fixed. Please note that B PHYs as well are almost unsupported by this driver. B/G cards have a G PHY, anyway. > Unless of course, I completely misunderstand how this is supposed to > work. Which is entirely possible. > > I look forward to using the bcm43xx on my laptop, particularly in > monitor mode. Speaking of, what is the status of monitor? Monitor mode was the first mode supported by this driver. It should work fine. -- ciao st3 _______________________________________________ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de http://lists.berlios.de/mailman/listinfo/bcm43xx-dev
