Orcan Ogetbil wrote:
PS: Currently we have RPM's for rt2860, rt2870 and rt3070 chipsets.
they are included in drivers/staging, and rt3070 should be included for .30 release.
rt3070 supports more HW, but basicaly is a rt2870+patches. And currently they overlap some device ID's.
FYI: two weeks ago, I sent to Ivo a bunch of new ID's for detect new devices: http://git.kernel.org/?p=linux/kernel/git/ivd/rt2x00.git;a=tree;f=drivers/ne...
regards,
On Tue, 2009-03-17 at 19:51 +0100, Xose Vazquez Perez wrote:
Orcan Ogetbil wrote:
PS: Currently we have RPM's for rt2860, rt2870 and rt3070 chipsets.
they are included in drivers/staging, and rt3070 should be included for .30 release.
Remember, drivers/staging is for known crappy and broken drivers, among other things.
AFAIK the staging wireless drivers aren't going to get enabled in Fedora kernels for the reasons that have already been discussed (and if they are, I'll find whoever did it and punch them in the face).
First, they use a *completely* separate wireless stack, and the kernel should not and will not have more than one wireless stack. Effort should be focused on helping Ivo get rt2x00 working with the new hardware. Second, those drivers, while they may work for some people, aren't generally acceptable to kernel wireless developers for a number of reasons (including the duplicate 802.11 stack). They are essentially ports of the Windows drivers and have not been vetted for quality or SMP safety or a whole host of other things.
It would be nice if Ralink worked with upstream instead of doing their own drivers.
Dan
-
Dan Williams -
Xose Vazquez Perez