From: Guenter Roeck <linux@roeck-us.net>
To: Mark Brown <broonie@kernel.org>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Hans de Goede <hdegoede@redhat.com>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
kernelci-results@groups.io, bot@kernelci.org,
gtucker@collabora.com, linux-pci@vger.kernel.org
Subject: Re: next/master bisection: baseline.login on asus-C523NA-A20057-coral
Date: Wed, 6 Apr 2022 13:56:02 -0700 [thread overview]
Message-ID: <20220406205602.GA3711131@roeck-us.net> (raw)
In-Reply-To: <Yk3r9uhIHmNumtxi@sirena.org.uk>
On Wed, Apr 06, 2022 at 08:37:26PM +0100, Mark Brown wrote:
> On Wed, Apr 06, 2022 at 01:59:31PM -0500, Bjorn Helgaas wrote:
> > On Tue, Apr 05, 2022 at 06:53:17PM -0500, Bjorn Helgaas wrote:
>
> > > Is there any way to get the contents of:
>
> > > /sys/firmware/acpi/tables/DSDT
> > > /sys/firmware/acpi/tables/SSDT*
>
> > > from these Chromebooks?
>
> > Is there hope for this, or should I look for another way to get this
> > information?
>
> I believe Guillaume is out of office this week. Copying in Guenter as
> well since he's on the ChromeOS team in case he can help or knows
> someone who can.
I _think_ the source should be in
https://chromium.googlesource.com/chromiumos/third_party/coreboot,
branch firmware-coral-10068.B,
in src/mainboard/google/reef/variants/coral/devicetree.cb.
Does this help, or do you need the actual binary devicetree file(s) ?
Guenter
prev parent reply other threads:[~2022-04-06 21:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <623c13ec.1c69fb81.8cbdb.5a7a@mx.google.com>
2022-03-24 17:52 ` next/master bisection: baseline.login on asus-C523NA-A20057-coral Mark Brown
2022-03-24 20:34 ` Hans de Goede
2022-03-24 22:19 ` Mark Brown
2022-03-28 12:54 ` Hans de Goede
2022-03-29 18:44 ` Guillaume Tucker
2022-04-04 19:44 ` Guillaume Tucker
2022-04-05 8:13 ` Hans de Goede
2022-04-05 17:57 ` Bjorn Helgaas
[not found] ` <16E2C910B4947F17.5433@groups.io>
2022-04-04 19:48 ` Guillaume Tucker
2022-03-30 11:35 ` Bjorn Helgaas
2022-04-04 8:45 ` Hans de Goede
2022-04-06 0:19 ` Bjorn Helgaas
2022-04-11 9:54 ` Hans de Goede
2022-04-11 9:57 ` Hans de Goede
2022-03-24 23:08 ` Bjorn Helgaas
2022-03-29 22:14 ` Bjorn Helgaas
2022-04-05 23:53 ` Bjorn Helgaas
2022-04-06 18:59 ` Bjorn Helgaas
2022-04-06 19:37 ` Mark Brown
2022-04-06 20:11 ` Guillaume Tucker
2022-04-07 15:17 ` Denys Fedoryshchenko
2022-04-06 20:56 ` Guenter Roeck [this message]
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=20220406205602.GA3711131@roeck-us.net \
--to=linux@roeck-us.net \
--cc=bhelgaas@google.com \
--cc=bot@kernelci.org \
--cc=broonie@kernel.org \
--cc=gtucker@collabora.com \
--cc=hdegoede@redhat.com \
--cc=helgaas@kernel.org \
--cc=kernelci-results@groups.io \
--cc=linux-pci@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rjw@rjwysocki.net \
/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;
as well as URLs for NNTP newsgroup(s).