[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CA+BfgNKCYT6EnOK1JTsy+AJCzZ+p6UbYD+SgBZ=ANHCV1pC7oA@mail.gmail.com>
Date: Thu, 27 Jan 2022 21:15:53 -0600
From: Dustin Howett <dustin@...ett.net>
To: Prashant Malani <pmalani@...omium.org>
Cc: linux-kernel@...r.kernel.org, Benson Leung <bleung@...omium.org>,
Guenter Roeck <groeck@...omium.org>,
Tzung-Bi Shih <tzungbi@...gle.com>,
Michael Niksa <michael.niksa@...e.com>, aaboagye@...omium.org
Subject: Re: [PATCH v2 2/2] platform/chrome: cros_ec_lpcs: reserve the MEC LPC
I/O ports first
On Thu, Jan 27, 2022 at 1:25 PM Prashant Malani <pmalani@...omium.org> wrote:
>
> What source do Framework laptop ECs (MECs?) compile their EC firmware
> from?
They just released their source here:
https://github.com/FrameworkComputer/EmbeddedController
FWIW, this series was written before they went open, and you're not
likely to see a similar construct
over there.
> Yeah, I wasn't thinking about userland i/o port access, but just having
> this behaviour/different I/O port mapping described in the EC code base
> too.
Happy to submit this over there as well. Are cros_ec_commands.h (here)
and ec_commands.h (there)
intended to be kept in 1:1 sync?
As well, is this a blocking concern?
Thanks!
d
Powered by blists - more mailing lists