public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
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:50:38 +0200	[thread overview]
Message-ID: <Yga+DvmFVHrmll8G@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:
> > > > On Fri, 11 Feb 2022 at 11:28, Andy Shevchenko
> > > > <andriy.shevchenko@intel.com> wrote:
> > > > > On Mon, Jan 31, 2022 at 05:59:30PM -0500, Tom Rini wrote:
> > >
> > > ...
> > >
> > > > FWIW here is my tboot flash script for Edison:
> > >
> > > This is rather unbriking script, DFU (luckily) works
> > 
> > Not if it is bricked: :-) I need something that always works.
> > 
> > >
> > > >     def flash_edison(self, repo):
> > > >         vid = 0x8086
> > > >         pid = 0xe005
> > > >         expect = "%04x:%04x" % (vid, pid)
> > > >         self.wait_for_dfu(expect)
> > > >         u_boot = os.path.join(repo._local_str(), "u-boot-edison.img")
> > > >         bindir = self.usbboot_xfstk_dir
> > > >         self.host.exec0(
> > > >             "xfstk-dldr-solo", "--gpflags", "0x80000007",
> > > >             "--osimage", u_boot,
> > > >             "--fwdnx", os.path.join(bindir, "edison_dnx_fwr.bin"),
> > > >             "--fwimage", os.path.join(bindir, "edison_ifwi-dbg-00.bin"),
> > > >             "--osdnx", os.path.join(bindir, "edison_dnx_osr.bin"))
> > >
> > > 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.

Side question(s):

- Why out of a sudden different name here:

    ACPI_WRITER(5fadt, "FACS", apl_write_fadt, 0);

  FACS vs FACP

- Why do you need double assignment of the same revision in acpi_fadt_common()

    header->revision = 4;
    ...
    /* Use ACPI 3.0 revision */
    fadt->header.revision = 4;



-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2022-02-11 19:51 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 [this message]
2022-02-11 19:54           ` Andy Shevchenko
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+DvmFVHrmll8G@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