i.e. you would end up using things like libhybris to run a non-Android distribution on there.
-
-
Replying to @CopperheadOS @Det_Conan_Kudo
I don't follow. Are you talking about userspace drivers?
1 reply 0 retweets 0 likes -
Replying to @RichFelker @Det_Conan_Kudo
Both. The drivers expose the API that Android expects, not the usual desktop stuff like dri3, etc.
2 replies 0 retweets 0 likes -
Replying to @CopperheadOS @Det_Conan_Kudo
So Android has its own wacky kernel APIs for video devices? Is there at least working /dev/fb0?
1 reply 0 retweets 0 likes -
Replying to @RichFelker @Det_Conan_Kudo
It has /dev/graphics/fb0 and it's probably different. Until dri3 desktop Linux APIs didn't support isolation.
1 reply 0 retweets 0 likes -
They did do a lot of NIH but they also NEEDED some stuff and the NIH goes both ways: https://lwn.net/Articles/697191/ ….
1 reply 0 retweets 0 likes -
Replying to @CopperheadOS @Det_Conan_Kudo
I would hardly call bus1 an example of "both ways" when it doesn't come from kernel folks but the kdbus lobby.
1 reply 0 retweets 0 likes -
Replying to @RichFelker @Det_Conan_Kudo
Sure but fd.o stuff is where most duplication happens in both directions. A fair bit has touched the kernel.
1 reply 0 retweets 0 likes -
The long time to adopt stuff like Wayland is starting to seem a bit silly when Android has it all since 2008.
1 reply 0 retweets 0 likes -
Android could have used pulseaudio since already existed then but it didn't do that for obvious reasons :P.
1 reply 0 retweets 0 likes
Well yes, fd.o and "desktop linux" stuff is awful. I just want http://X.org to work.
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.