From: Leon Romanovsky <leon@kernel.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Josh Triplett <josh@joshtriplett.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
ksummit@lists.linux.dev
Subject: Re: [MAINTAINER SUMMIT] User-space requirements for accelerator drivers
Date: Sat, 11 Sep 2021 13:31:02 +0300 [thread overview]
Message-ID: <YTyFZufZHu9BSFxk@unreal> (raw)
In-Reply-To: <87ilz8c7ff.ffs@tglx>
On Sat, Sep 11, 2021 at 01:55:16AM +0200, Thomas Gleixner wrote:
> On Fri, Sep 10 2021 at 16:45, Josh Triplett wrote:
>
> > On Sat, Sep 11, 2021 at 12:52:14AM +0200, Mauro Carvalho Chehab wrote:
> >> On media, enforcing userspace to always be open source would
> >> have been very bad, as it would prevent several videoconferencing
> >> software to exist on Linux.
> >
> > I don't think we should enforce that all userspace users of an interface
> > be Open Source. I do think we should enforce that *some* userspace user
> > of an interface be Open Source before we add the interface.
>
> The real question is whether the interface is documented in a way that
> an Open Source implementation is possible. It does not matter whether it
> exists at that point in time or not. Even if it exists there is no
> guarantee that it is feature complete.
>
> Freely accessible documentation is really the key.
I have more radical view than you and think that documentation is far
from being enough. I would like to see any userspace API used (or to be
used) in any package which exists in Debiam/Fedora/SuSE.
Only this will give us some sort of confidence that API and device are usable
to some level. As a side note, we will be able to estimate possible API
deprecation/fix/extension based on simple search in package databases.
IMHO, github projects to show API usage are the worst possible way to
allow acceptance for new userspace API.
Thanks
>
> Thanks,
>
> tglx
>
>
>
next prev parent reply other threads:[~2021-09-11 10:31 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-10 21:00 [MAINTAINER SUMMIT] User-space requirements for accelerator drivers Jonathan Corbet
2021-09-10 21:32 ` Josh Triplett
2021-09-13 13:50 ` Christian Brauner
2021-09-13 13:57 ` Daniel Vetter
2021-09-14 2:07 ` Laurent Pinchart
2021-09-14 14:40 ` Jani Nikula
2021-09-14 14:45 ` Geert Uytterhoeven
2021-09-14 14:59 ` Jani Nikula
2021-09-14 15:10 ` Geert Uytterhoeven
2021-09-10 21:51 ` James Bottomley
2021-09-10 21:59 ` Alexandre Belloni
2021-09-10 22:35 ` James Bottomley
2021-09-11 14:51 ` Jonathan Corbet
2021-09-11 15:24 ` James Bottomley
2021-09-11 21:52 ` Laurent Pinchart
2021-09-14 13:22 ` Johannes Berg
2021-09-11 0:08 ` Laurent Pinchart
2021-09-10 22:52 ` Mauro Carvalho Chehab
2021-09-10 23:45 ` Josh Triplett
2021-09-10 23:48 ` Dave Hansen
2021-09-11 0:13 ` Laurent Pinchart
2021-09-10 23:55 ` Thomas Gleixner
2021-09-11 0:20 ` Laurent Pinchart
2021-09-11 14:20 ` Steven Rostedt
2021-09-11 22:08 ` Laurent Pinchart
2021-09-11 22:42 ` Steven Rostedt
2021-09-11 23:10 ` Laurent Pinchart
2021-09-13 11:10 ` Mark Brown
2021-09-11 22:51 ` Mauro Carvalho Chehab
2021-09-11 23:22 ` Mauro Carvalho Chehab
2021-09-11 10:31 ` Leon Romanovsky [this message]
2021-09-11 11:41 ` Laurent Pinchart
2021-09-11 12:04 ` Leon Romanovsky
2021-09-11 22:04 ` Laurent Pinchart
2021-09-12 4:27 ` Leon Romanovsky
2021-09-12 7:26 ` Greg KH
2021-09-12 8:29 ` Leon Romanovsky
2021-09-12 13:25 ` Greg KH
2021-09-12 14:15 ` Leon Romanovsky
2021-09-12 14:34 ` Greg KH
2021-09-12 16:41 ` Laurent Pinchart
2021-09-12 20:35 ` Dave Airlie
2021-09-12 20:41 ` Dave Airlie
2021-09-12 20:49 ` Daniel Vetter
2021-09-12 21:12 ` Dave Airlie
2021-09-12 22:51 ` Linus Walleij
2021-09-12 23:15 ` Dave Airlie
2021-09-13 13:20 ` Arnd Bergmann
2021-09-13 13:54 ` Daniel Vetter
2021-09-13 22:04 ` Arnd Bergmann
2021-09-13 23:33 ` Dave Airlie
2021-09-14 9:08 ` Arnd Bergmann
2021-09-14 9:23 ` Daniel Vetter
2021-09-14 10:47 ` Laurent Pinchart
2021-09-14 12:58 ` Arnd Bergmann
2021-09-14 19:45 ` Daniel Vetter
2021-09-14 15:43 ` Luck, Tony
2021-09-13 14:52 ` James Bottomley
2021-09-14 13:07 ` Linus Walleij
2021-09-13 14:03 ` Mark Brown
2021-09-12 15:55 ` Laurent Pinchart
2021-09-12 16:43 ` James Bottomley
2021-09-12 16:58 ` Laurent Pinchart
2021-09-12 17:08 ` James Bottomley
2021-09-12 19:52 ` Dave Airlie
2021-09-12 7:46 ` Mauro Carvalho Chehab
2021-09-12 8:00 ` Leon Romanovsky
2021-09-12 14:53 ` Laurent Pinchart
2021-09-12 15:41 ` Mauro Carvalho Chehab
2021-09-10 23:46 ` Laurent Pinchart
2021-09-11 0:38 ` Mauro Carvalho Chehab
2021-09-11 9:27 ` Laurent Pinchart
2021-09-11 22:33 ` Mauro Carvalho Chehab
2021-09-13 12:04 ` Mark Brown
2021-09-12 19:13 ` Dave Airlie
2021-09-12 19:48 ` Laurent Pinchart
2021-09-13 2:26 ` Dave Airlie
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=YTyFZufZHu9BSFxk@unreal \
--to=leon@kernel.org \
--cc=corbet@lwn.net \
--cc=josh@joshtriplett.org \
--cc=ksummit@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=tglx@linutronix.de \
/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).