On Sat, 2008-10-04 at 23:16 -0700, Greg KH wrote: > On Sun, Oct 05, 2008 at 08:56:20AM +0300, Kalle Valo wrote: > > Greg KH <greg@xxxxxxxxx> writes: > > > In my quest to suck drivers into drivers/staging/ I noticed that the > > > at76_usb driver is being shipped by both Fedora and Ubuntu in their > > > kernels. > > > > Yes, that's the original at76_usb driver which has it's own 802.11 > > stack. Pavel Rosking was the maintainer of that driver. Based on the > > feedback in linux-wireless I then started porting the driver to use > > mac80211. > > > > (Maybe I should have renamed the port to something else than at76_usb > > because having two different drivers with the same name creates > > confusion.) > > > > > So I was wondering what the status of this driver is, and if I > > > could/should add it to drivers/staging/? > > > > The original at76_usb is working quite well, but it's unacceptable for > > the mainline because we cannot have two 802.11 stacks in kernel. > > I understand this, but for the issue of the drivers/staging/ tree, it's > ok for us to have as many 802.11 stacks in the kernel as we can cram in > there :) Well, you have to ask yourself then, what's the point of putting that driver with it's own 802.11 stack into staging when it's never going to go into the mainline kernel until it uses mac80211? Doesn't that direct effort away from porting the driver to mac80211, giving legitimacy to code that will never, ever get upstream until it's substantially rewritten anyway? Ideally we put Kalle's 802.11 port in staging and then people can actually move things forward. Same thing for linux-wlan-ng really; if people just keep fixing bugs and keep improving p80211 without porting it to the standard kernel wireless bits, what's the point of having it in staging? Dan > See my previous posts on lkml for details on the staging tree if you > have questions about it. > > So for now, if no one really screams, I'll put Pavel's driver into the > drivers/staging/ tree so that users can use their devices. When your > driver is merged, we can merely delete this driver instead. > > Sound good? > > > > And, did you merge the USB DFU code into the driver itself? > > > > Yes, someone implemented it in driver. > > > > > Having that kind of functionality in the USB core is fine with me if > > > you want me to add that portion there, no reason it needs to be > > > burried in individual drivers. > > > > USB DFU is a standard? So it seems: > > > > http://wiki.openmoko.org/wiki/USB_DFU > > > > Heh, I didn't know this. I though it was some Atmel proprietary > > interface :) > > Oh yeah, I wrote portions of that spec, oh so long ago :) > > > I might be interested in getting DFU into USB core, because I would > > like to learn more about USB. But first I need to get at76_usb stable. > > Fair enough, patches are always welcome. > > thanks, > > greg k-h > -- > 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 -- 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
