-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possible Kernel Mainline inclusion? #53
Comments
Your information is not correct. That ugly, horrid driver has never been submitted to the kernel. As far as I know, GitHub is one of the few places to get the driver. To answer the question, to get it into the kernel, the code would need to be changed to get rid of long lines, CaMeLcaSe variable names, most typedef statements, and general ugliness. In addition, it would need to be converted to use mac80211 and friends. That last step would be the hardest part. In case there is any question, I have no interest in placing the driver in the kernel. |
Thank you for your reply and your fine work maintaining the driver! I paid a few bucks for my Netgear N600 wifi modem only to find out it had no Linux driver (Windows only, CD included etc.). This page saved my investment. Thanks again! 👯♂️ |
@lwfinger are you interested if I clean the driver ? |
Fork it, and do whatever you want. After it passes through checkpatch, sparse, smatch, and whatever tool you choose, it will still be crap! You would be better to devote effort into updating rtl8xxxu to handle this chip. |
I understand this driver is in the kernel 'Staging' category. I was wondering what the process is to try for inclusion in the main Linux kernel source tree?
The text was updated successfully, but these errors were encountered: