3 ms·
The problem are the SoC that often have weird peripheral and drivers that require patched kernels (and often it's to interface with proprietary hardware that's
by 908B64B197 5y ago
The problem are the SoC that often have weird peripheral and drivers that require patched kernels (and often it's to interface with proprietary hardware that's under IP constrains).
- R0b0t1 5y agoTwo options: the claimed IP on the interface is removed or said to never have existed in the first place, and/or prevent bootloader locking. First one is a very good idea, as older IP law actually holds that interfaces aren't copyrightable. US IP law is schizophrenic on this last point considering the Oracle ruling. E.g. you're free to implement an interface for compatibility.
- neop1x 5y ago>> SoC that often have weird peripheral and drivers that require patched kernels This is a sad industry-wide mess which should have been fixed long time ago IMO. It is unfortunately common for an Android device to come with a custom patched 2.x kernel with no plans for 3.x support. Then when a next Android is released it has a hard requirement of 3.x kernel. So no Android update for that SoC/device and no way to port this mess into the newer kernel. If SoC/peripheral manufacturers only supply "software" as a custom hacked 2.x kernel branch they are basically supplying unfinished PoC-quality un-updatable garbage and such software should have never been released with a production device. This is non-existent on desktop and laptop space where you often have mainline support for all the essential components.