Anyway, the best thing that can be hoped for is that the new devices are on 4.4 rather than 3.18 or 4.1. It'll still be frozen.
-
-
Replying to @CopperheadOS
How big are the obstacles to using a mainline (4.7 or soon 4.8) kernel? Essential drivers hard to forward-port?
1 reply 0 retweets 0 likes -
Replying to @RichFelker
It's unrealistic to use mainline with Qualcomm devices. It's only feasible with NVIDIA Tegra and it would be a huge effort.
1 reply 0 retweets 0 likes -
Replying to @CopperheadOS @RichFelker
Unless you want to boot a serial console without support for the radio or other peripherals, it's a lot more than few drivers.
2 replies 0 retweets 0 likes -
Replying to @CopperheadOS
Maybe it's something that could be done incrementally as a project to use phones for non-phone/non-Android purposes.
1 reply 0 retweets 0 likes -
Replying to @RichFelker
Little can be done about the inability to update radio/bootloader/TrustZone and proprietary userspace blobs after EOL though.
1 reply 0 retweets 0 likes -
Replying to @CopperheadOS @RichFelker
Lack of support for firmware after a few months is already the norm for desktops/laptops so perhaps no one actually cares...
1 reply 0 retweets 0 likes -
Replying to @CopperheadOS @RichFelker
Lots of the kernel drivers are really just shims for userspace blobs where the real work is done. Upstreaming those is one step.
1 reply 0 retweets 0 likes -
Replying to @CopperheadOS
Are the drivers just proprietary userspace processes that run effectively with kernel privs via their shims?
1 reply 0 retweets 0 likes -
Replying to @RichFelker
Some of them are close to root, but in many cases there's a privilege boundary or at least there's supposed to be a boundary.
2 replies 0 retweets 0 likes
Are the radio (wifi, cellular network) drivers open source and included in the kernel, or are they also binary blobs?
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.