> To: nwi_sub@xxxxxxxxxxx > Subject: Re: Please pull 'upstream' branch of rt2x00 > Date: Fri, 2 May 2008 23:25:38 +0200 > CC: linux-wireless@xxxxxxxxxxxxxxx > From: ivdoorn@xxxxxxxxx > > On Friday 02 May 2008, Scott White wrote: >> >>>Was this patch series in time for the 2.6.26 merge window? >>> >>>If not, please consider merging at least the following patches since >>>they are real bugfixes: >>> >>>> rt2x00: Don't enable short preamble for 1MBs >>>> rt2x00: Fix quality/activity led handling >>>> rt2x00: Clarify supported chipsets in Kconfig >>> >>>The others are code cleanups which are "nice to have", but could otherwise >>>wait for 2.6.27. >> >> The merge window is still open at this time. I haven't seen a rc1 yet. Anyway I saw that only the 3 bugfixes are currently in the queue. As the owner of several (10 by the university and 2 personal) rt73 usb wireless cards, I would really like it if the latest version 2.1.5 made into 2.6.26. As someone who has used 2.6.24 and finished compiling 2.6.25 two days ago I find that the driver in both kernels is not good. Not good means I get a wireless signal and I get data transfers, but the speed fluctuates and have other issues. However with each release, the problems I have are slowing decreasing. I have been waiting patiently for 2.6.25-rc1 to have 2.1.5 since 2.1.5 was announced. I really think all of 2.1.5 should get in 2.6.25-rc1. > > Have you tried forcing the rate to 54Mbit instead of letting the rate selection algorithm doing its work? > It seems to have helped with several other users. > > Ivo No I haven't tried that. However I have 54Mbit (g) at home, but only 11Mbit (b only) at work. I guess I would have to change the rate when I change locations. Thanks, _________________________________________________________________ Make Windows Vista more reliable and secure with Windows Vista Service Pack 1. http://www.windowsvista.com/SP1?WT.mc_id=hotmailvistasp1banner-- 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
