Stephen Clark wrote:
I find it really sad that a hardware vendor that is willing to write and develope drivers for Linux for their hardware aren't helped more by "the community"
It's hard to be more helpful without (a) explaining the problems with the current situation and suggesting corrections, or (b) doing it all myself.
or is the "the community" only interested in hacking drivers where the manufacturer give no or minimal support?
The more people working on drivers, the wider the workload is spread, which is a good thing.
The caveat being you cannot just throw any old crap into the kernel, just because you are a Big Hardware Vendor. Linux thrives precisely because of the system of engineering review and Internet-scale testing that we have set up.
We have an engineering process that has proven itself over the past 10+ years. You don't just chuck that out the window because someone doesn't want to follow the process. Making exceptions for Big Vendors who can't grok the rules is not how Linux became successful.
These processes all have carefully considered engineering rationale behind them. The obvious engineering breakdowns occur when you avoid the standard process... the process that has been delivering stable hardware support to you and other Linux users.
I appreciate Intel's support for being open and purposely bought a laptop that had an Intel graphics chipset and an Intel wireless card.
Intel gets five stars in the areas of open source CPU, platform, and graphics support. Intel graphics is really going to kick ass (not that it doesn't already), and Keith Packard (old-school X11 hacker) is leading the charge. And Intel networking definitely gets applause for doing open source networking as well.
But we just don't shove any old vendor driver into the kernel. Not when we have to maintain these drivers for a decade, often after the vendor themselves end-of-life's the chip.
Jeff - 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
