Thanks for the quick response. I already use git and kernel source from kernel.org so I'll branch out, follow the bisect instructions in git man/docs, and see what I can come up with ... Adrian Bassett > Date: Mon, 16 Mar 2009 09:40:15 -0500 > From: Larry.Finger@xxxxxxxxxxxx > To: adrian.bassett@xxxxxxxxxxxxx > CC: linux-wireless@xxxxxxxxxxxxxxx > Subject: Re: rtl8180 Bit Rate regression in 2.6.29 > > Adrian Bassett wrote: >> >> (I'm not currently subscribed so please Cc: in any response ...) >> >> Using PCI device 1799:700f and the rtl8180 kernel wireless driver. >> >> With the vanilla 2.6.29-rc releases (rc8 most recently but also with predecessors) I've noticed that the Bit Rate of my wireless device appears to be more or less fixed at 1 Mb/s. Occasionally, iwconfig reports higher values but, as the stats below show, no attempts are successful at higher Bit Rates with this kernel version. >> >> With the 2.6.28 series, however, the Bit Rate will vary in the normal way, with the majority of the network activity happening at the higher end, if not the highest(54 Mb /s) point, of the range supported by this device. > > It would be immensely helpful if you, or someone else with this hardware and the > problem, could use git to download the mainline tree and find the bad commit > using bisection. In a review of the commit log, I found only one change in the > rtl8180 code in the 2.6.28 to 2.6.29-rcX range, and without it the rtl8180 would > not work at all. As a result, I cannot suggest a trial patch. > > My system says that there are 6172 commits between 2.6.29-rc8 and 2.6.28, thus > it will take roughly 13 kernel builds to bisect the problem. > > Larry _________________________________________________________________ View your Twitter and Flickr updates from one place – Learn more! http://clk.atdmt.com/UKM/go/137984870/direct/01/-- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
