From: Mark Brown <broonie@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Jason Gunthorpe <jgg@nvidia.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Greg KH <gregkh@linuxfoundation.org>,
Dan Williams <dan.j.williams@intel.com>,
ksummit@lists.linux.dev
Subject: Re: [MAINTAINERS SUMMIT] Between a rock and a hard place, managing expectations...
Date: Thu, 24 Aug 2023 18:12:23 +0100 [thread overview]
Message-ID: <ZOePd+0Ncywxa5kZ@finisterre.sirena.org.uk> (raw)
In-Reply-To: <CACRpkdbt-GxDgGbpETJTjBXz6qH2yLFgTR8BVVU9EU1uj7tJ+Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 953 bytes --]
On Thu, Aug 24, 2023 at 10:16:31AM +0200, Linus Walleij wrote:
> Since then they come a long way, after a few generations of lost
> hardware that the kernel never supported properly, Android is
> pushing the Generic Kernel Image and being more restrictive about
> proprietary extensions every day. It's going the right way.
> Todd Kjos at Google and Greg Kroah-Hartman from the community
> have been instrumental here.
I do have some concerns about the effects of GKI on framework
improvements, by making it difficult for vendors to update any of the
shared APIs it pushes them into implementing anything they can't get
from the frameworks in their drivers instead. This means if they're
going to upstream things and do the best job possible they'll end up
working on multiple versions which provides a bunch of stop energy.
Life will be much easier for vendors if they just worry about their
specific devices as much as possible.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-08-24 17:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 0:43 Dan Williams
2023-08-22 8:55 ` Greg KH
2023-08-22 13:37 ` Linus Walleij
2023-08-22 14:29 ` Laurent Pinchart
2023-08-24 0:46 ` Jason Gunthorpe
2023-08-24 8:16 ` Linus Walleij
2023-08-24 14:19 ` Jason Gunthorpe
2023-08-24 17:12 ` Mark Brown [this message]
2023-08-24 17:20 ` Bird, Tim
2023-08-24 19:29 ` Bart Van Assche
2023-08-24 19:58 ` Mark Brown
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=ZOePd+0Ncywxa5kZ@finisterre.sirena.org.uk \
--to=broonie@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jgg@nvidia.com \
--cc=ksummit@lists.linux.dev \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linus.walleij@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox