4 ms·

I don't think there is any common low level way, even among the Linux flavors. Android's graphics stack, for example, is completely different and doesn't use an

I don't think there is any common low level way, even among the Linux flavors. Android's graphics stack, for example, is completely different and doesn't use any of this. If you want portable you're going to want something like SDL probably.

shmerl 9y ago
Andriod is a weird deviation, and kind of annoying because the rift goes all the way to libc, which makes Android blobs incompatible without translation hacks like libhybris. If in case of GPU you can at least get something like Freedreno to avoid such hacks, but good luck getting open drivers for the modem and the like. So those blobs are a necessary evil for some devices to be usable, and there are none for glibc.
- kllrnohj 9y ago
  libhybris would still exist if Android had been running glibc. You still have architecture-specific stuff at the end of the day. Just like how XWayland exists to map X11 to Wayland, even though both use the same glibc. Looking through the source of libhybris it looks like very little of it has anything to do with bionic itself.
  - shmerl 9y ago
    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?
    - kllrnohj 9y ago
      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.
    - pjmlp 9y ago
      Yes completely different. This how the graphics stack look like on Android, a mix of Java, C and C++ code. https://source.android.com/devices/graphics/ https://source.android.com/devices/graphics/ https://source.android.com/devices/graphics/architecture https://source.android.com/devices/graphics/architecture
      - shmerl 9y ago
        Android can use Mesa, so that's not convincing.
        pjmlp 9y ago
        No Android handset is being sold with Mesa instead of SurfaceFlinger. Can you please prove me wrong?
        shmerl 9y ago
        SurfaceFlinger is a compositor. Mesa is lower level. Search yourself (Android with Mesa).
        pjmlp 9y ago
        Which means you cannot answer my question.
        shmerl 9y ago
        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.
        pjmlp 9y ago
        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.

shmerl 9y ago

Andriod is a weird deviation, and kind of annoying because the rift goes all the way to libc, which makes Android blobs incompatible without translation hacks like libhybris. If in case of GPU you can at least get something like Freedreno to avoid such hacks, but good luck getting open drivers for the modem and the like. So those blobs are a necessary evil for some devices to be usable, and there are none for glibc.

kllrnohj 9y ago
libhybris would still exist if Android had been running glibc. You still have architecture-specific stuff at the end of the day. Just like how XWayland exists to map X11 to Wayland, even though both use the same glibc. Looking through the source of libhybris it looks like very little of it has anything to do with bionic itself.
- shmerl 9y ago
  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?
  - kllrnohj 9y ago
    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.
  - pjmlp 9y ago
    Yes completely different. This how the graphics stack look like on Android, a mix of Java, C and C++ code. https://source.android.com/devices/graphics/ https://source.android.com/devices/graphics/ https://source.android.com/devices/graphics/architecture https://source.android.com/devices/graphics/architecture
    - shmerl 9y ago
      Android can use Mesa, so that's not convincing.
      - pjmlp 9y ago
        No Android handset is being sold with Mesa instead of SurfaceFlinger. Can you please prove me wrong?
        shmerl 9y ago
        SurfaceFlinger is a compositor. Mesa is lower level. Search yourself (Android with Mesa).
        pjmlp 9y ago
        Which means you cannot answer my question.
        shmerl 9y ago
        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.
        pjmlp 9y ago
        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.