From: Pekka Paalanen <ppaalanen@gmail.com>
To: "Jonas Ådahl" <jadahl@redhat.com>
Cc: "Sebastian Wick" <sebastian.wick@redhat.com>,
"Aleix Pol" <aleixpol@kde.org>,
"DRI Development" <dri-devel@lists.freedesktop.org>,
"xaver.hugl@gmail.com" <xaver.hugl@gmail.com>,
"Melissa Wen" <mwen@igalia.com>,
"Michel Dänzer" <mdaenzer@redhat.com>,
"Uma Shankar" <uma.shankar@intel.com>,
"Victoria Brekenfeld" <victoria@system76.com>,
wayland-devel <wayland-devel@lists.freedesktop.org>,
"Joshua Ashton" <joshua@froggi.es>
Subject: Re: [RFC] Plane color pipeline KMS uAPI
Date: Wed, 10 May 2023 11:59:28 +0300 [thread overview]
Message-ID: <20230510115928.42755c9d@eldfell> (raw)
In-Reply-To: <ZFtO2bMQOWVhRkSG@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1889 bytes --]
On Wed, 10 May 2023 09:59:21 +0200
Jonas Ådahl <jadahl@redhat.com> wrote:
> On Tue, May 09, 2023 at 08:22:30PM +0000, Simon Ser wrote:
> > On Tuesday, May 9th, 2023 at 21:53, Dave Airlie <airlied@gmail.com> wrote:
> >
> > > There are also other vendor side effects to having this in userspace.
> > >
> > > Will the library have a loader?
> > > Will it allow proprietary plugins?
> > > Will it allow proprietary reimplementations?
> > > What will happen when a vendor wants distros to ship their
> > > proprietary fork of said library?
> > >
> > > How would NVIDIA integrate this with their proprietary stack?
> >
> > Since all color operations exposed by KMS are standard, the library
> > would just be a simple one: no loader, no plugin, no proprietary pieces,
> > etc.
> >
>
> There might be pipelines/color-ops only exposed by proprietary out of
> tree drivers; the operation types and semantics should ideally be
> defined upstream, but the code paths would in practice be vendor
> specific, potentially without any upstream driver using them. It should
> be clear whether an implementation that makes such a pipeline work is in
> scope for the upstream library.
>
> The same applies to the kernel; it must be clear whether pipeline
> elements that potentially will only be exposed by out of tree drivers
> will be acceptable upstream, at least as documented operations.
In my opinion, a COLOROP element definition can be accepted in the
upstream kernel documentation only if there is also an upstream driver
implementing it. It does not need to be a "direct" hardware
implementation, it could also be the upstream driver mapping the
COLOROP to whatever hardware block or block chain it has.
For the userspace library I don't know. I am puzzled whether people
want to allow proprietary components or deny them.
Thanks,
pq
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-05-10 8:59 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
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 [this message]
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=20230510115928.42755c9d@eldfell \
--to=ppaalanen@gmail.com \
--cc=aleixpol@kde.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jadahl@redhat.com \
--cc=joshua@froggi.es \
--cc=mdaenzer@redhat.com \
--cc=mwen@igalia.com \
--cc=sebastian.wick@redhat.com \
--cc=uma.shankar@intel.com \
--cc=victoria@system76.com \
--cc=wayland-devel@lists.freedesktop.org \
--cc=xaver.hugl@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).