lwfinger / rtl8723bu

Driver for RTL8723BU
283 stars 143 forks source link

README.md: does not clarify why and how of this external, non-mainline-kernel driver #156

Closed andim2 closed 4 years ago

andim2 commented 4 years ago

Hello,

while the README.md does mention blacklisting of the mainline kernel driver module, it fails to list potential reasons for using (and also: creating!) this implementation code which is an external, not-[yet-]mainline driver.

Thank you!

lwfinger commented 4 years ago

This code will NEVER be in mainline. Why? It would take over a year of full-time work to rework it to reach the quality necessary. If you are willing to fund the effort, then I might consider it.

This driver was created by Realtek, the vendor of the chip. Their USB drivers "work" with Windows, FreeBSD, and Linux. As such, they contain a lot of code that is useless in Linux, but I "publish" them at GitHub so that people like you can have access to them. If you do not like what you see, you have two options - (1) Write your own driver, or (2) Update this one. I consider all suggestions that include actual code.

andim2 commented 4 years ago

Sorry, I had written this issue in a somewhat demanding, impolite manner, not unlikely because directly prior to this I was miffed about very questionable support status (in all newer versions of stable mainline kernel prior to v5.4-rcX!) of Not-so-Realtek hardware:

(1) Write your own driver

I have written my own driver ;) (albeit for original TI WLAN crap - acx100, which could be said to have been in an even more dire situation)

In closing, thank you very much for your very appreciable and major efforts of reducing the gap between what ought to be vendor-provided as a sufficiently robust, stable service and what all too often actually happens!

lwfinger commented 4 years ago

My only comment on the above rant is that rtl8xxxu was created without any Realtek input other than this external (crappy) driver. Yes, the patch quoted above fixed an error in the transcription; however, the author of the patch needed considerable effort to find that fix. Obviously, no one had devoted that effort, which is why it took 3 years to fix it. I'm not sure what Red Flag that indicates.