On Mon, 28 Apr 2014 10:30:02 +0300
Pekka Paalanen
wrote:
> Oh, that's the DRM set-master related thing. Once we move on to render
> nodes, you don't even need a VT to simply work on the GPU, let alone a
> display server. IOW, render nodes will just fix that, and you can use
> the GPU for computat
On Sun, 27 Apr 2014 18:25:45 +0300
Pekka Paalanen
wrote:
> Sorry?
> ...
> Huh?
See below for an example and link to a demonstrator
> For FBO, you can create the storage with e.g. glTexImage2D, or some
> of the renderbuffer functions.
Storage is one thing. Being able to actually use it the oth
On Sun, 27 Apr 2014 18:13:04 +0300
Pekka Paalanen
wrote:
> Do they, really? Or does it happen on-demand, slowly RAM<->VRAM,
> causing hickups, a bit like traditional swapping RAM to disk?
The OpenGL specification doesn't define it. Drivers can implement it as
they want to.
> Especially when re-
On Sun, 27 Apr 2014 13:57:45 +0200
John Kåre Alsaker
wrote:
> Since VGA is a ting of the past, I'm more interested in what the
> display do.
Display devices always were nonlinear in their signal response. That's
why gamma LUTs got introduced in the first place, to deal with the
saturation effect
On Sun, 27 Apr 2014 12:11:39 +0200
John Kåre Alsaker
wrote:
> I implemented support for ABGR16161616 framebuffers in mesa/wl_drm.
> My patch has bit-rotted a bit now, but it gives you an idea about
> what to do:
> https://github.com/Zoxc/mesa/commit/73f39f1366287bab02c993cb3537980e89b3cdca
>
> M
On Sun, 27 Apr 2014 11:35:37 +0200
Wolfgang Draxinger
wrote:
> > Btw. weren't FBConfigs a GLX thing?
>
> No, XRender actually; GLX just piggybacks on that.
Okay, that needs some explanation. While all functions that have
"FBConfig" in their name are part of GLX yo
On Sun, 27 Apr 2014 11:30:18 +0300
Pekka Paalanen
wrote:
> > I'm still trying to get an GBM configuration working that targets
> > an off-screen buffer so that OpenGL operations are carried out
> > toward it on the GPU but without attaching it to a CRTC.
>
> I think you should do that with an F
On Sat, 26 Apr 2014 17:10:38 -0400
"Jasper St. Pierre" wrote:
> Outside of an X11 environment, the only standard is EGL, with a
> Wayland backend for Wayland apps, or a GBM backend for native
> modesetting.
Well, GBM is just another backend for EGL. In my GBM experiments I
copy'n'pasted this cod
On Sat, 26 Apr 2014 23:38:32 +0300
Pekka Paalanen
wrote:
> Buffer types that support hardware acceleration of rendering and/or
> compositing have their own pixel format lists, e.g.
> http://cgit.freedesktop.org/mesa/mesa/tree/src/egl/wayland/wayland-drm/wayland-drm.xml#n39
> for Mesa EGL.
>
> ..
Hi,
could someone please fill me in, if and if yes, how deep color modes
(more than 8 bits per color channel) are (going to be) supported and
handled by the Wayland protocol, compositors and clients?
I'm currently toying around (for self educational purposes) with direct
access to the GPU (using
10 matches
Mail list logo
