[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZqIuN2JR_mRgZiJ1@shikoro>
Date: Thu, 25 Jul 2024 12:51:35 +0200
From: Wolfram Sang <wsa+renesas@...g-engineering.com>
To: Ricardo Ribalda Delgado <ricardo.ribalda@...il.com>
Cc: Laurent Pinchart <laurent.pinchart@...asonboard.com>,
James Bottomley <James.Bottomley@...senpartnership.com>,
Jiri Kosina <jikos@...nel.org>,
Dan Williams <dan.j.williams@...el.com>, ksummit@...ts.linux.dev,
linux-cxl@...r.kernel.org, linux-rdma@...r.kernel.org,
netdev@...r.kernel.org, jgg@...dia.com
Subject: Re: [MAINTAINERS SUMMIT] Device Passthrough Considered Harmful?
Hi Ricardo,
> It would be great to define what are the free software communities
> here. Distros and final users are also "free software communities" and
> they do not care about niche use cases covered by proprietary
> software.
> They only care (and should care) about normal workflows.
Don't you think there are distros and final users who do care about
proprietary influences, in general. For sure, though, I think they
should not be told what they should care about?
> If we want vendors involved, we need to build an ecosystem where they
> feel invited.
Definitely. Invited as in "you are welcome to work with us on this",
though. Not as in "come here and do what you want". This is why we have
a coding-style etc...
> We should not take as hostages our users and impose rules on how they
> should build or even sell their product.
Right, it should be a plain buisness decision. I totally agree with your
"clear rules" request below. And yeah, face to face is probably best
suited.
> - Vendor passthrough mechanisms are allowed for niche use cases or
> development/experimentation.
Problem with "niche" is that it can grow really big. See Linux :)
All the best,
Wolfram
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists