If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

It's the part of the Direct Rendering Infrastructure (DRI) that Manages access to the GPU so multiple programs can perform "direct rendering" (talking directly to the GPU as opposed to handing everything off to the X server to be drawn) at the same time without stepping on each others toes.

...plus, I believe it's old enough that "copy protection" was what people called Digital Restrictions Management at the time.

Comment

Does this mean an open source user space driver will eventually follow? Not sure if I remember this correctly, but I once read something about kernel drivers not being merged if all user space components using it are only binary blobs.

Comment

Does this mean an open source user space driver will eventually follow? Not sure if I remember this correctly, but I once read something about kernel drivers not being merged if all user space components using it are only binary blobs.

This is modesetting only, which doesn't require an userspace component.

Comment

Because it is a drm driver.. kms is part of drm. Display-only drm/kms drivers are becoming more common with SoC's, and expect to eventually start seeing some render/gpu-only drm drivers for the gpu side of things (ex. etnaviv/vivante) which would share buffers via dmabuf/prime (+ the new fence stuff) with whichever display-only driver is appropriate for the SoC..

Comment

Because it is a drm driver.. kms is part of drm. Display-only drm/kms drivers are becoming more common with SoC's, and expect to eventually start seeing some render/gpu-only drm drivers for the gpu side of things (ex. etnaviv/vivante) which would share buffers via dmabuf/prime (+ the new fence stuff) with whichever display-only driver is appropriate for the SoC..