Re:Intro to Low-Level Graphics on Linux
by shmerl on Wednesday August 30, 2017 @11:26PM
(#15137959)
I thought its whole point is to work around idiosyncrasies of bionic, and translate it into glibc proper. Or you mean that Android drivers architecture is very different from proper Linux drivers?
[ Parent
| on HN ]
Yes completely different. This how the graphics stack look like on Android, a mix of Java, C and C++ code.
Android can use Mesa, so that's not convincing.
No Android handset is being sold with Mesa instead of SurfaceFlinger.
Can you please prove me wrong?
Re:Intro to Low-Level Graphics on Linux
by kllrnohj on Thursday August 31, 2017 @12:17PM
(#15141347)
Mesa and SurfaceFlinger do two completely different things. You can absolutely use Mesa on Android (the emulator does, for example). But just like on desktop you're typically using the GPU vendors' accelerated GL implementation instead of Mesa. But if the vendors driver uses Mesa, like the Intel GPUs, that still works fine on Android.
> the emulator does, for example
No it doesn't.
"Android Studio: The Mesa software renderer is deprecated. Use Swiftshader for software rendering"
https://stackoverflow.com/questions/39568455/android-studio-...
Intel has dropped out of Android market.
SurfaceFlinger is a compositor. Mesa is lower level. Search yourself (Android with Mesa).
Which means you cannot answer my question.
Which means you don't know what you are talking about. Did you search what I said? It's not the first time you do it for the sake of flaming.
The FOSS religion days are well behind me for worrying about flame wars.
The very fact that you cannot prove me wrong, tells it all.
Given that I also work with Android, are you so naive to think I need to search for whatever you want me to find?!?
Sure there is Mesa on the emulator, which is deprecated by the way.
Oh and in those Intel devices that are no longer being sold.
Re:Intro to Low-Level Graphics on Linux
by kllrnohj on Wednesday August 30, 2017 @11:35PM
(#15137983)
bionic is largely just a subset of glibc. There's not really any idiosyncrasies to workaround going from bionic to glibc (the hard part is the reverse as people commonly use non-portable glibc extensions)
libhybris is more things like converting Surfaceflinger calls into Wayland ones. Looks like there's some media, camera, and input stuff, too, which is all outside the realm of bionic/glibc.