On 21/06/14 20:52, Christian Lamparter wrote: > On Saturday, June 21, 2014 06:45:07 PM Kristina Martšenko wrote: >> On 20/06/14 23:52, Christian Lamparter wrote: >>> rtl8192su development is chugging along. It just doesn't take place on >>> driverdev list. The driver reached "feature parity" with rtl8192cu for >>> some time ago. >> >> Great, thanks for letting me know. If you plan to keep working on it, do >> you think it would be a good idea to add yourself and a link to your >> github to the staging driver's TODO file? That way people who find it >> and want to work on it can join your effort, instead of starting their own. > > Actually, this is already happening. I get mails about rtl8192su. So, > people who are interested are definitely following the development. Ah, that's good then. > However the hurdles for rtl8192su driver are quite high > (3.15+ kernel [1]). This is due to the driver being based on rtlwifi > framework (the devices shares a lot of common code with the > rtl8192SE - the pcie version). The development takes place on > top of wireless-testing.git, so it can be merged with the rest of > the drivers. Yeah, I can see how that would slow development. > (If someone is interested in the details: how a wireless drivers are > mainlined. There's a nifty process plan right here: [0] - check it out!). > > (NB: my stance on the TODO: Leave it the way it is. After all, you want > those free checkpatch.pl and smatch/sparse fixes, right?) I don't think it would affect the checkpatch/sparse cleanups, they'd still be sent for the staging driver. I just thought it might point people who want to help with the mac80211 conversion in your direction. But it's your call. >>> But as with rtl8192cu, I would recommend adding just a friendly "printk". >> >> I'm not sure what printk you're referring to. > I think there's a reason why the development takes so long > (The RTL8192S* chips have been around since 2008, 2009) > and why we all have better things to do and write harsh > responses. As far as I can tell, It would be great if Realtek > could have a few dedicated devs, which take care of integrating > their own linux drivers into /drivers/net/wireless instead of > dumping it into /driver/staging. > > This might sounds like hobbyists wifi-devs are a bunch of *****. > However, other (wifi-)vendor (e.g.: Intel, Qualcom, TI, Broadcom > and Marvell) have been participating for some time now. And > their end-users are very happy as a result of this. Now, if only > Realtek would join the party; that would be "awesome". > > Regards, > Chr > > [0] <http://wireless.kernel.org/en/developers/process#Maintainer_chain> > [1] <https://github.com/chunkeey/rtl8192su/issues/2> Kristina _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
