From: Pekka Paalanen <ppaalanen@gmail.com>
To: Steven Kucharzyk <stvr_8888@comcast.net>
Cc: DRI Development <dri-devel@lists.freedesktop.org>,
wayland-devel@lists.freedesktop.org
Subject: Re: [RFC] Plane color pipeline KMS uAPI
Date: Tue, 9 May 2023 11:17:40 +0300 [thread overview]
Message-ID: <20230509111740.006136cd@eldfell> (raw)
In-Reply-To: <20230508185409.07501f40@n2pa>
[-- Attachment #1: Type: text/plain, Size: 1428 bytes --]
On Mon, 8 May 2023 18:54:09 -0500
Steven Kucharzyk <stvr_8888@comcast.net> wrote:
> I'd like to ask if there is a block/flow chart/diagram that has been
> created that represent the elements that are being discussed for this
> RFC? If so, would you be so kind as to point me to it or send it to me?
Hi Steven,
the whole point of the design is that there is no predefined block
diagram or flow chart. It would not fit hardware well, as hardware
generations and vendors do not generally have a common design. Instead,
the idea is to model what the hardware can do, and for that each driver
will create a set of specific pipelines the hardware implements.
Userspace then choose a pipeline that suits it and populates its
parameters.
As for the elements themselves, we can hopefully define some commonly
available types, but undoubtedly there will be a few hardware-specific
elements as well. Otherwise some piece of special hardware functionality
cannot be used at all.
The job of defining a generic pipeline model and mapping that to actual
hardware elements is left for a userspace library. I expect there will
be multiple pipeline models, more to be introduced over time. Hence
putting that in a userspace library instead of carving it in stone at
the kernel UAPI.
Next time, please do use reply-to-all, you have again dropped everyone
and other mailing lists from the CC.
Thanks,
pq
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-05-09 8:17 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 15:22 [RFC] Plane color pipeline KMS uAPI Simon Ser
2023-05-04 21:10 ` Harry Wentland
2023-05-05 11:41 ` Pekka Paalanen
2023-05-05 13:30 ` Joshua Ashton
2023-05-05 14:16 ` Pekka Paalanen
2023-05-05 17:01 ` Joshua Ashton
2023-05-09 11:23 ` Melissa Wen
2023-05-09 11:47 ` Pekka Paalanen
2023-05-09 17:01 ` Melissa Wen
2023-05-11 21:21 ` Simon Ser
2023-05-05 15:28 ` Daniel Vetter
2023-05-05 15:57 ` Sebastian Wick
2023-05-05 19:51 ` Daniel Vetter
2023-05-08 8:24 ` Pekka Paalanen
2023-05-08 9:00 ` Daniel Vetter
2023-05-05 16:06 ` Simon Ser
2023-05-05 19:53 ` Daniel Vetter
2023-05-08 8:58 ` Simon Ser
2023-05-08 9:18 ` Daniel Vetter
2023-05-08 18:10 ` Harry Wentland
[not found] ` <20230508185409.07501f40@n2pa>
2023-05-09 8:17 ` Pekka Paalanen [this message]
2023-05-05 20:40 ` Dave Airlie
2023-05-05 22:20 ` Sebastian Wick
2023-05-07 23:14 ` Dave Airlie
2023-05-08 9:37 ` Pekka Paalanen
2023-05-08 10:03 ` Jonas Ådahl
2023-05-09 14:31 ` Harry Wentland
2023-05-09 19:53 ` Dave Airlie
2023-05-09 20:22 ` Simon Ser
2023-05-10 7:59 ` Jonas Ådahl
2023-05-10 8:59 ` Pekka Paalanen
2023-05-11 9:51 ` Karol Herbst
2023-05-11 16:56 ` Joshua Ashton
2023-05-11 18:56 ` Jonas Ådahl
2023-05-11 19:29 ` Simon Ser
2023-05-12 7:24 ` Pekka Paalanen
2023-05-10 8:48 ` Pekka Paalanen
[not found] ` <20230505160435.6e3ffa4a@n2pa>
2023-05-08 8:49 ` Pekka Paalanen
2023-05-09 8:04 ` Pekka Paalanen
[not found] ` <4341dac6-ada1-2a75-1c22-086d96408a85@quicinc.com>
2023-06-09 15:52 ` Christopher Braga
2023-06-09 16:30 ` Simon Ser
2023-06-09 23:11 ` Christopher Braga
2023-06-12 9:21 ` Pekka Paalanen
2023-06-12 16:56 ` Christopher Braga
2023-06-13 8:23 ` Pekka Paalanen
2023-06-13 16:29 ` Christopher Braga
2023-06-14 9:00 ` Pekka Paalanen
2023-06-15 21:44 ` Christopher Braga
2023-06-16 7:59 ` Pekka Paalanen
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=20230509111740.006136cd@eldfell \
--to=ppaalanen@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=stvr_8888@comcast.net \
--cc=wayland-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.