3 ms·
The biggest problem for ANY alternative ROMs is the total and utter lack of transparency for chipset drivers and documentation. And even if the manufacturer pu
by mschuster91 11y ago
The biggest problem for ANY alternative ROMs is the total and utter lack of transparency for chipset drivers and documentation.
And even if the manufacturer publishes source trees for drivers, they're based on year-old kernel versions. Same goes for bootloaders.
And that's a problem for the entire embedded Linux ecosystem, not just phones.
I wonder what prevents the vendors from committing their drivers upstream? Can that be worked against, i.e. by the manufacturers or independent organisations financing people to integrate and maintain the drivers?
It 'd be a huge benefit for the entire embedded ecosystem if people could find and fix bugs in out-of-mainline drivers, there are a shitload of bugs in them.
edit: oh, and another thing, mainly concerning Android phones: the refusal of the Linux userland community to learn from Android and cut the craft accumulated in decades (x-server! the need for autotools which check for stuff that's been standardized for 10 years or longer without a way to cache certain tests systemwide! lack of really deep sleep, central to embedded systems! a shitload of "sound servers" resulting in 100+ms latencies!) to keep compatibility with even OLDER systems certainly does not help developers of alternative OSes.
- anonymfus 11y agoIt is not a problem for Windows ROMs because SoC/board specific initialisation is done by UEFI on Windows phones and Windows NT kernel has a stable binary API for drivers.
- gue5t 11y agoYou've hit the nail entirely on the head. Re: the reasons vendors never push code upstream, have you read http://lwn.net/Articles/662147/ http://lwn.net/Articles/662147/?
- mschuster91 11y agoYes. I seriously hope someone finds a local-root exploit for some out-of-tree driver used in a lot of devices, bonus points if it affects multiple vendors. Only when the pain/cost of going out-of-tree is too high, vendors will be forced to listen to the FOSS community instead of their bonehead lawyers telling that "drivers are our IP!!!!!!!!!!!". I'm shocked neither Heartbleed, Stagefright or that (iirc) Samsung kernel driver bug had enough of an effect. Or that Google does not require a (Github) published source tree for kernel+AOSP in order for certification.
- throwaway2048 11y agoThe problem is this: Ask a lawyer if arbitrary activity is a legal risk, they are always going to answer yes. After-all somebody can sue you for any reason whatsoever. Without a strong counterballacing party to that point of view, the default is always going to be closed with a collective shrug from developers that tacitly accept the "legal realities". It will probly take a worm of sasser-like porportions on android to break this pattern of closed drivers that work on one 3 year old kernel that never get updated.
- jschwartzi 11y agox-server is still pretty damn useful. It lets me forward the ui for the IDEs my job requires from my work laptop to the beast I have at home so I can be productive there.
- tubs 11y agoThe problem is, who is the vendor, and who owns the rights to distribute the driver code?