From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Simon Glass <sjg@chromium.org>
Cc: Tom Rini <trini@konsulko.com>, Bin Meng <bmeng.cn@gmail.com>,
U-Boot Mailing List <u-boot@lists.denx.de>,
u-boot-custodians@lists.denx.de,
u-boot-board-maintainers@lists.denx.de
Subject: Re: [ANN] U-Boot v2022.04-rc1 released
Date: Fri, 11 Feb 2022 21:54:38 +0200 [thread overview]
Message-ID: <Yga+/sByzbueZfxu@smile.fi.intel.com> (raw)
In-Reply-To: <Yga9Z7sBFAeV64FV@smile.fi.intel.com>
On Fri, Feb 11, 2022 at 09:47:52PM +0200, Andy Shevchenko wrote:
> On Fri, Feb 11, 2022 at 12:31:46PM -0700, Simon Glass wrote:
> > On Fri, 11 Feb 2022 at 12:29, Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
> > > On Fri, Feb 11, 2022 at 9:26 PM Simon Glass <sjg@chromium.org> wrote:
...
> > > To the topic, any suggestions on how to fix the current U-Boot regression?
> >
> > The easiest thing is to use 'acpi list' and 'acpi dump facp' etc. to
> > see what is different between the two commits. My testing was on coral
> > and minnowmax and I must have missed it. We don't actually have any
> > test coverage on the board-specific code.
>
> => acpi dump facp
> Table 'FACP' not found
>
> This explains I believe everything.
So, how is this ACPI_WRITER() supposed to work? Any documentation, please?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-02-11 19:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 22:59 [ANN] U-Boot v2022.04-rc1 released Tom Rini
2022-02-11 18:27 ` Andy Shevchenko
2022-02-11 18:46 ` Andy Shevchenko
2022-02-11 19:15 ` Andy Shevchenko
2022-02-12 15:02 ` Andy Shevchenko
2022-03-30 15:47 ` Andy Shevchenko
2022-02-11 19:25 ` Simon Glass
2022-02-11 19:27 ` Andy Shevchenko
2022-02-11 19:31 ` Simon Glass
2022-02-11 19:47 ` Andy Shevchenko
2022-02-11 19:50 ` Andy Shevchenko
2022-02-11 19:54 ` Andy Shevchenko [this message]
2022-03-30 9:20 ` Andy Shevchenko
2022-02-12 16:58 ` Michal Simek
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=Yga+/sByzbueZfxu@smile.fi.intel.com \
--to=andy.shevchenko@gmail.com \
--cc=bmeng.cn@gmail.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot-board-maintainers@lists.denx.de \
--cc=u-boot-custodians@lists.denx.de \
--cc=u-boot@lists.denx.de \
/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