Stephen

@helloer A couple of questions. Which chromium build are you running? and are you running this under Wayland? I'm getting these errors at the moment, attempting to run it under...

I've spent a few hours working on this today and managed to get...not far. I've discovered that XFCE's display composition is what was causing the the EGL_BAD_MATCH errors (I think)....

I've reworked some stuff and got Chromium on X11 (with desktop GL) support sort of working, but it's quite a hack and very inefficient, and the resulting image isn't quite...

--ozone-platform=wayland is automatically passed with chromium-freeworld. Just tried regular chromium too, slightly different error: ``` [57047:57047:0724/154417.696624:WARNING:wayland_drm.cc(96)] Failed to get drm magic ``` rather than: ``` [55021:55021:0724/154043.238392:WARNING:wayland_drm.cc(96)] Drm prime capability is...

That branch is using quite the hack to get it to work. I'm having to do the YUV -> RGB conversion myself, and I doubt I got the right magic...

Ok, all the colours should be sorted now. However for the moment you'll need to run it with `NVD_BACKEND=direct` as I've completely reworked the copying code to work entirely on...

I've pushed an attempt at a fix for that issue. There's some system header that's defining Status as a macro which breaks the NVIDIA headers.

It looks like the NVIDIA headers are requiring the kernel headers to be install to build against it. I'm hesitant to modify those headers as they're taken directly from NVIDIA's...

Can you run chrome with `NVD_LOG=1`?

I'm not planning on releasing this branch until I've done more testing, and got it working (however well) with the EGL backend aswell. The direct backend is a dubious idea...