On Thu, Aug 6, 2009 at 1:27 PM, Adam Williamson wrote: > On Thu, 2009-08-06 at 11:34 +0200, drago01 wrote: > >> > I'm not quite sure if I could catch what you meant. Are you being >> > sarcastic, implying that the rt2xxx staging drivers will stay in the >> > staging repo forever? I sure hope not :) Hey! Don't break my hopes! >> >> The rtxxxx vendor drivers are considered a dead end by the >> linux-wireless developers (just try to read the code and you would now >> why), the plan is to get rt2800pci and rt2800usb into shape and get >> them upstreamed. >> >> They get no support from the wireless developers at all, Greg added >> them to staging because "they are better than no drivers". > > Thanks for the clarification. From what I read, I inferred that the > driver in /staging was the serialmonkey driver, but it seems I read it > wrong, and what it actually means to say was 'this is the vendor driver, > it sucks, don't contribute any code to this driver, contribute to the > serialmonkey driver instead'. > I had the same confusion. So there are 3 drivers around: The vendor driver, the staging driver which is a fork of the vendor driver and the serialmonkey driver. Multiply that by 3 for rt2860, rt2870 and rt3070. And this leads to another confusion. Do (or will) the Fedora kernels have these staging drivers compiled by default? If that's the case and if the staging driver is as stable as the original vendor driver, I won't have to maintain those kmods anymore. Orcan -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
