-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The rt2x00 project provides ongoing support for the rt2400 rt2500 and rt2570 chipsets that were open sourced (GPL) by RaLink. The chipset is quite popular and used by a few dozen vendors (linksys most notably here in US) in various PCI and USB based hardware: http://rt2x00.serialmonkey.com/wiki/index.php/Hardware http://ralink.rapla.net/ RT2x00 is aiming for eventual adoption into the kernel but a large number of distros have taken initiative and included them in their latest releases. A few of those distros: * SuSE since 10.0 * debian (contrib) * Gentoo (portage) * Mandriva Does fedora have any plans to include support for this hardware in FC5? Fedora sure could use some help in the wireless support department and I think this is a good addition that will get a large number of people off of the inherent dangers of ndiswrapper. If you visit the site you will notice 4 codebases (1 each 2400/2500/2570 and one 2x00 unification project). While the unified project is most tempting it is also the least developed and just began supporting association this week. The 3 individual projects however have a very stable codebase and report very high success rates. I am also willing to help in any way possible. - -mf

Fedora tracks upstream fairly closely so if it gets upstream it get into Fedora. In the mean time various people on the list have been kicking around ideas for improving the add on driver support in Fedora extras and that seems to be the right place to start

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Alan Cox wrote: > Fedora tracks upstream fairly closely so if it gets upstream it get into Fedora. > In the mean time various people on the list have been kicking around ideas for > improving the add on driver support in Fedora extras and that seems to be the right > place to start I was afraid i was going to get a alexendar dumas style "wait and hope" response. It is also probably the right one in order to maintain a semblance of sanity in the kernel maintenance department. With releases coming every few months i suppose it isnt much to ask people to wait for its inclusion. I'll see what i can chase down in extras in the meantime. Thanks for the response.

Would you suggest trying to get the (more stable) separate drivers included upstream while the unified driver codebase settles down? Meaning, is it a smart move to try to push something in that will be functionally replaced in a year? If it isnt terribly difficult to

transition from one driver to the next then where should i start? I've never tried to push any patches into the upstream kernel and don't know the politics (link or short explanation would be great). :) Thanks.

On Fri, Nov 04, 2005 at 03:29:01AM -0600, Michael Favia wrote: > > Would you suggest trying to get the (more stable) separate drivers > included upstream while the unified driver codebase settles down? > Meaning, is it a smart move to try to push something in that will be > functionally replaced in a year? If it isnt terribly difficult to a year is a long time, so long that I'd say try the existing one.

RT2x00 is aiming for eventual adoption into the kernel but a large number of distros have taken initiative and included them in their latest releases. A few of those distros: * SuSE since 10.0 * debian (contrib) * Gentoo (portage) * Mandriva

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The rt2x00 project provides ongoing support for the rt2400 rt2500 and rt2570 chipsets that were open sourced (GPL) by RaLink. The chipset is quite popular and used by a few dozen vendors (linksys most notably here in US) in various PCI and USB based hardware:

Speaking about rt2500 driver (I use beta3 and I installed it with 'make; make install-fedora'), I never managed to set up my WEP key with system-config-network tool so I put some script in my /etc/rc.local file. Besides that, system-config-network-tui doesn't have the wireless network entry, and FC4 Rawhide doesn't have system-config-network-tui at all (?). Do you have any plans to improve system-config-network tool, and the ncurces based version of that tool?