All of lore.kernel.org
 help / color / mirror / Atom feed
From: keithp@keithp.com ("Keith Packard")
To: "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>
Subject: liboutput: thoughts about shared library on top of DRM/KMS
Date: Sat, 05 Oct 2019 12:09:11 -0400	[thread overview]
Message-ID: <87y2xzqimw.fsf@keithp.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1155 bytes --]


During XDC this year, we heard a few presentations and had a lot of
hallway talk about sharing code for driving DRM/KMS for display.

I think the general consensus is that there is enough shared
functionality between all of the various DRM/KMS clients that we can
start thinking about building a library that deals with the complexity
of DRM/KMS and can help take full advantage of the hardware.

I've started writing up some ideas, mostly just goals, but also some
random thoughts about how this might work. This is all in the
'liboutput' project on freedesktop.org:

        https://gitlab.freedesktop.org/xorg/liboutput

I picked a spot in the 'xorg' namespace, not to confine this to X
systems, but to reflect the goal that this be a library shared across
all x.org-related projects, including Wayland compositors, EGL and
Vulkan direct applications and the X server.

All there is at this point is a README.md file; I'd like to generate
some consensus on a direction for the project before we start writing
any actual design documents.

Please submit MRs to that repo, or respond to this email as you prefer.

-- 
-keith

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2019-10-05 16:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-05 16:09 "Keith Packard" [this message]
2019-10-05 20:36 ` liboutput: thoughts about shared library on top of DRM/KMS Robert Foss
2019-10-06  1:12   ` Keith Packard
2019-10-07 17:35 ` Daniel Stone
2019-10-07 17:40   ` Daniel Stone
2019-10-07 18:16   ` Keith Packard
2019-10-07 18:28     ` Daniel Stone
2019-10-08  7:15     ` Pekka Paalanen
2019-10-08  9:31     ` Daniel Stone
2019-10-08 14:35       ` Alex Deucher
2019-10-08 14:52         ` Daniel Vetter
2019-10-08  9:33     ` Heinrich Fink
2019-10-08  7:52 ` Neil Armstrong
2019-10-08 23:38   ` Keith Packard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y2xzqimw.fsf@keithp.com \
    --to=keithp@keithp.com \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.