2 ms·
What is in it for the maintainers who would then have to support hardware they do not neccessarly have access to, adding development time to the linux kernel ma
by themoonisachees 4y ago
What is in it for the maintainers who would then have to support hardware they do not neccessarly have access to, adding development time to the linux kernel maintainers who honestly would be better off spending their time improving linux further instead of supporting potentially thousands of users at best?
Imo the responisibility lies with the hardware vendors. Sell your hardware with working software, and support it for x years guaranteed. When the support period ends they can decide to extend it (they wont, but they could) instead of relying on developers who have nothing to do with the product and are working for free for the hardware vendor.
Either that or contract kernel maintainers to upstream it for x years and they do the heavy lifting, but that's always going to be more expensive than doing it in-house.
- happymellon 4y agoWhy do these things have to be mutually exclusive? They already hire kernel hackers to build their drivers and bespoke images in the first place.
- TheLoafOfBread 4y agoThis is exactly what I am struggling with as well - what's the point of having it in the upstream, when developers CAN'T TEST THE DRIVER WITH THE DEVICE. Just provide some stable API for drivers and let hardware developers do their job. Microsoft Windows understood this, why is it so difficult for Linux Kernel do get the memo.