From: "Keith Packard" <keithp@keithp.com>
To: Neil Armstrong <narmstrong@baylibre.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: liboutput: thoughts about shared library on top of DRM/KMS
Date: Tue, 08 Oct 2019 19:38:22 -0400 [thread overview]
Message-ID: <87zhian6z5.fsf@keithp.com> (raw)
In-Reply-To: <62e06d9c-64ec-17c5-d89c-70ef6ac8debc@baylibre.com>
[-- Attachment #1.1: Type: text/plain, Size: 616 bytes --]
Neil Armstrong <narmstrong@baylibre.com> writes:
> Seeing the description, it seems to be a libdrm with steroids,
> why libdrm doesn't handle all this already ?
That'd be a lot of steroids; we're talking about creating helper
functions all the way up to rendering images into scanout buffers
(presumably using Vulkan?) for format conversion or flattening.
> Is there a plan to maybe use it as a foundation for projects like
> wlroots or drm_hwcomposer for example ?
Yes, the goal is to start to share code across a wide range of DRM
users, instead of having everyone roll their own.
--
-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
prev parent reply other threads:[~2019-10-08 23:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-05 16:09 liboutput: thoughts about shared library on top of DRM/KMS "Keith Packard"
2019-10-05 20:36 ` 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 [this message]
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=87zhian6z5.fsf@keithp.com \
--to=keithp@keithp.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=narmstrong@baylibre.com \
/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.