Re: [MAINTAINER SUMMIT] User-space requirements for accelerator drivers

Mark Brown
2021-09-13T14:04:04Z

[-- Attachment #1: Type: text/plain, Size: 1773 bytes --]

On Sun, Sep 12, 2021 at 04:34:48PM +0200, Greg KH wrote:
> On Sun, Sep 12, 2021 at 05:15:30PM +0300, Leon Romanovsky wrote:

> > https://lore.kernel.org/all/YT2zryAKHc%2F5R2IH@unreal/
> > "To be used" means some open PR to existing package or request for
> > inclusion for new packages.

> But again, distros will not take things that are not already in the
> kernel.

Or, mainly for the community distros which are open to people
volunteering to package things, can't be relied on to do validation
beyond checking that the package is distributable and that the installed
files integrate into the distro in roughly the right form. That's not
really a meaningful form of back pressure from our point of view.

> > > But how do you define Android's userspace? Just one vendor? 2 vendors?
> > > 10 vendors? There is major userspace fragmentation in Android userspace
> > > in many places, the user/kernel boundry being one of the big ones as
> > > many of us have found out over the past years. And many of us are
> > > working to resolve this, but it's not so simple at times, and I have
> > > many examples if you want specifics.

> > Lauerent suggested AOSP
> > https://lore.kernel.org/all/YTyWANV%2FmSkQbYhj@pendragon.ideasonboard.com/

> Vendors can not get code into AOSP for various reasons that only Google
> understands. There are many millions, if not billions of Android
> devices out there with user/kernel apis that are not upstream nor in
> AOSP because Google doesn't want to take them, or because the vendor can
> not go through those hoops (international law is tricky at times...)

Right, if you're not one of the main SoC vendors working on something
that's a main application of Android it can be very hard to get anyone
to give you the time of day.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]