4 ms·
If it hasn't worked, why has no one forked the kernel and left Linus in the dust? Manufacturers ought to support their products for their full lifecycle instea
by uabstraction 9y ago
If it hasn't worked, why has no one forked the kernel and left Linus in the dust?
Manufacturers ought to support their products for their full lifecycle instead of behaving like e-waste factories. If they're not happy about unstable kernel ABIs, they can start making Windows devices.
- kuschku 9y agoThis isn't up to manufacturers, but up to SoC vendors. And not even just to them. They also just combine many chips into their systems, and also get precompiled driver blobs. You're asking the entire tech industry to change how they're doing things.
- pritambaral 9y agoAllow me to play The Devil's Advocate: Those aggrieved by the lack of a Linux driver ABI have indeed forked the kernel, and some of them even maintain their forks. They just happen to be focussed solely on their own needs and thus their forks happen to be specific to their business requirements alone. Take Qualcomm's CodeAurora hosted repos for one: maintained for years, with backporting and new releases based on new upstream releases, all merged with Qualcomm's drivers for their own hardware. The reason no one has left Linus['s repo] in the dust is because no one has taken the effort to put out and maintain a general purpose API-standardised fork instead of heavily-customised, specific-to-their-own-business codebases.
- deleted 9y ago[deleted]