05:21 <bshah> btw

05:22 <bshah> I am trying to run chromium on lima (yes I know I know)

05:22 <bshah> my current issue is : https://github.com/raspberrypi/firmware/issues/20 similar to this one

05:22 <bshah> (well not exactly chromium but qtwebengine which uses chromium internally)

05:24 <anarsoul> we do support depth24_stencil8

05:25 <bshah> https://groups.google.com/a/chromium.org/forum/#!topic/graphics-dev/kOb-yuhPUok .. found another thread (who have same hardware as me)

05:25 <bshah> appearantly

05:26 <bshah> "Actually, not supporting RGB textures as framebuffer attachments is allowed by GLES2.0 spec. GLES2.0 implementations are allowed to choose just one texture attachment format that they support (section 4.4.5). If a driver only supports RGBA, it's not a driver bug as such. To investigate this, you could make a simple native OpenGL app that creates an RGB FBO and see if that succeeds. I don't think that Chromium currently has code to handle the case where RGB is not

05:26 <bshah> natively supported, so if RGB FBO attachments are not supported WebGL will fail like this. You could file a Chromium bug about this."

05:27 <anarsoul> yeah, we don't support RGB render targets

05:27 <bshah> :/

05:27 <anarsoul> bshah: blob doesn't expose it, so we don't know how to do that :)

05:28 <bshah> makes sense

05:28 <bshah> although meh.. I guess I will file chromium bug

15:36 <MoeIcenowy> bshah: doesn't Chromium just blacklist Mali400?