[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+ASDXOuJVG7bpXdKMf9nobjJ=qcTiBWVj+TQ3Kpwqct27HSag@mail.gmail.com>
Date: Fri, 21 Jul 2023 10:28:59 -0700
From: Brian Norris <briannorris@...omium.org>
To: Alicja Michalska <ahplka19@...il.com>
Cc: Tzung-Bi Shih <tzungbi@...nel.org>, linux-kernel@...r.kernel.org,
robbarnes@...gle.com, lalithkraj@...gle.com, rrangel@...omium.org,
bleung@...omium.org, groeck@...omium.org,
chrome-platform@...ts.linux.dev
Subject: Re: [PATCH] platform/chrome: cros_ec_lpc: Add DMI definition for
post-Skylake machines running custom Coreboot builds
On Fri, Jul 21, 2023 at 10:16 AM Alicja Michalska <ahplka19@...il.com> wrote:
> I've explained the reason behind adding this patch, but we'll go with
> different approach next time around.
FWIW, I'm also confused about your first sentence the same way
Tzung-Bi is. If two people are confused by parts of your description,
then maybe it needs improvement :)
> Since we're discussing this, I would like to suggest removal of DMI
> matches for EOL machines from lines 503...535 (Link, Samus, Peppy, Glimmer).
>
> Those machines aren't supported by Google anymore. Patch I suggested
> will match DMI while running custom firmware.
>
> If maintainers are okay with it, I will submit a patch removing DMI
> matches for stock firmware running on those machines since it's not
> needed anymore.
That seems actively harmful. These devices continue to work just fine
with their stock BIOS, even if Google no longer supports updating the
Google-built OS. That doesn't mean people can't boot other OS'es
(e.g., their own ChromiumOS builds; or other Linux distros) on them.
Brian
Powered by blists - more mailing lists