[07:23] <zzarr> hello!
[07:23] <RAOF> Hi!
[07:23] <zzarr> now I'm here again, new thoughts and ideas how to possibly solve my problem
[07:24] <zzarr> Mir on ASUS Chromebook Flip that is
[07:27] <zzarr> I know this is a hypothetical question or a theoretical maybe, but do you think I will be able to use the binary blob with libhybris now when Google enables Android apps on Chromebooks?
[07:27] <RAOF> Possibly?
[07:27] <zzarr> (not just a few apps, all of them)
[07:28] <RAOF> It depends on how they do their EGL layer.
[07:28] <zzarr> I know that it has a lot to do with how they solve the rendering
[07:28] <RAOF> They may well not expose HWC, which would mean “no”.
[07:28] <zzarr> RAOF, what is EGL?
[07:29] <RAOF> The cross-platform bind-a-GLish-API-to-a-native-window API.
[07:29] <RAOF> The abstraction of GLX, WGL, AGL, etc.
[07:30] <zzarr> okey, I'm a bit lost, I confess but I do have a clue
[07:31] <zzarr> I have a feeling that is the way they may solve it
[07:33] <RAOF> They probably *won't* expose HWC (which we need), because that's only needed for implementing SurfaceFlinger, and isn't exposed to Android apps AFAIK.
[07:33] <RAOF> What doesn't work on the Chromebook Flip, by the way?
[07:35] <zzarr> RAOF,could you specify "doesn't work"?
[07:36] <RAOF> What are you trying to do, and what's preventing you from doing it?
[07:37] <zzarr> RAOF, I wish to run an GPU accelerated Mir/Unity8 but it's not possible
[07:38] <RAOF> Why not?
[07:39] <zzarr> no drivers
[07:39] <RAOF> What GPU does it have?
[07:39] <zzarr> it's powered by a Rockchip RK3288 which have a Mali 764
[07:40] <zzarr> there are drivers for Android and for X11
[07:45] <zzarr> it's a bit sad, the Chromebook flip and Unity8's ability to change between desktop and tablet GUI is as made for each other
[07:45] <RAOF> If there are already drivers for android, why can't you use those?
[07:48] <zzarr> don't they require me to build the kernel for android?
[07:48] <RAOF> Yes.
[07:49] <zzarr> how do I do that?
[07:49] <RAOF> The Android OSP should have docs on that.
[07:49] <RAOF> I've not done it myself.
[07:50] <zzarr> okey, do you know if I can keep the rest of the drivers or if I need drivers for the touch, wifi, bluetooth and so on?
[07:51] <RAOF> You'll probably need android-userspace drivers for some of that.
[07:51] <RAOF> Hm, or maybe not.
[07:52] <RAOF> I'd expect touch, wifi, and bluetooth to all be kernel-only and happy with Ubuntu userspace.
[07:52] <zzarr> as it is now they work with Ubuntu
[07:57] <zzarr> RAOF, do you know how to configure the lid? (closed, open or over 180 degrees)
[07:58] <RAOF> No, sorry.
[07:58] <zzarr> okey
[11:50] <greyback> hey folks, in mesa, there is the big egl-platform-mir patch. But I don't see it actually creating a Mir platform, along side the GBM/X11/Wayland platforms.
[11:50] <greyback> e.g. there is no EGL_EXT_platform_mir
[11:52] <greyback>  hey folks, in mesa, there is the big egl-platform-mir patch. But I don't see it actually creating a Mir platform, along side the GBM/X11/Wayland platforms.
[11:52] <greyback>  e.g. there is no EGL_EXT_platform_mir
[12:22] <anpok> greyback: yes. As far as I know support for such an extension does not exist yet.