qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: Tom Rini <trini@konsulko.com>
Cc: linus.walleij@linaro.org, fitzsim@fitzsim.org,
	qemu-devel@nongnu.org, seanga2@gmail.com, u-boot@lists.denx.de,
	Mark Kettenis <mark.kettenis@xs4all.nl>,
	francois.ozog@linaro.org, swarren@nvidia.com,
	Oleksandr_Andrushchenko@epam.com, xypron.glpk@gmx.de,
	michal.simek@xilinx.com, vanbaren@cideas.com,
	swarren@wwwdotorg.org, andre.przywara@arm.com, agraf@csgraf.de,
	Anastasiia_Lukianenko@epam.com, albert.u.boot@aribaud.net,
	mbrugger@suse.com, ilias.apalodimas@linaro.org,
	awilliams@marvell.com, tuomas.tynkkynen@iki.fi,
	bmeng.cn@gmail.com
Subject: Re: [PATCH v5 00/26] fdt: Make OF_BOARD a boolean option
Date: Wed, 3 Nov 2021 10:45:21 -0600	[thread overview]
Message-ID: <CAPnjgZ38AQvH+zKdEdxJWwM9kXVw3s2usoeOveLndTZVkwbZzA@mail.gmail.com> (raw)
In-Reply-To: <20211103155647.GD24579@bill-the-cat>

Hi Tom,

On Wed, 3 Nov 2021 at 09:56, Tom Rini <trini@konsulko.com> wrote:
>
> On Tue, Nov 02, 2021 at 07:20:51PM -0600, Simon Glass wrote:
> > Hi Mark,
> >
> > On Wed, 27 Oct 2021 at 16:30, Mark Kettenis <mark.kettenis@xs4all.nl> wrote:
> > >
> > > > From: Simon Glass <sjg@chromium.org>
> > > > Date: Wed, 27 Oct 2021 12:23:21 -0600
> > > >
> > > > Hi François,
> > > >
> > > > On Wed, 27 Oct 2021 at 09:14, François Ozog <francois.ozog@linaro.org> wrote:
> > > > >
> > > > >
> > > > >
> > > > > On Wed, 27 Oct 2021 at 16:08, Simon Glass <sjg@chromium.org> wrote:
> > > > >>
> > > > >> Hi François,
> > > > >>
> > > > >> On Tue, 26 Oct 2021 at 00:07, François Ozog <francois.ozog@linaro.org> wrote:
> > > > >> >
> > > > >> > Hi Simon
> > > > >> >
> > > > >> > Position unchanged on this series: adding fake dts for boards that generate their device tree in the dts directory is not good. If you have them in documentation the it is acceptable.
> > > > >>
> > > > >> I think we are going to have to disagree on this one. I actually used
> > > > >> the qemu one in testing/development recently. We have to have a way to
> > > > >> develop in-tree with U-Boot. It does not impinge on any of your use
> > > > >> cases, so far as I know.
> > > > >
> > > > > I am not the only one in disagreement... You just saw Alex Bénée from Qemu saying the same thing.
> > > > > I understand the advanced debug/development scenario you mention.
> > > > > But locating the DT files in the dts directory is mis-leading the contributors to think that they need to compile the DT for the targeted platforms.
> > > > > For your advanced scenario, you can still have the dts in the documentation area, or whatever directory (except dts). compile it and supply to U-Boot.
> > > >
> > > > We have this situation with rpi 1, 2 and 3 and I don't believe anyone
> > > > has noticed. U-Boot handles the build automatically. If you turn off
> > > > OF_BOARD, it will use the U-Boot devicetree always so you know what is
> > > > going on.
> > >
> > > Until.  The Raspberry Pi foundation releases a new firmware that
> > > configures the hardware differently such that the addresses in the
> > > U-Boot devicetree are wrong and nothing works anymore.  Can't speak
> > > for the rpi 1, but this has happened in the past for the rpi 2 and 3
> > > as well as more recently on the rpi 4.
> >
> > So I update my SD card with a new private-binary bootloader and things
> > stop working? I think I can narrow that one down :-)
>
> Well, wait, no, this is the point.  You can just not update your board.
> But that all of the users running a more recent release are now broken
> is the problem.  It's already an opt-in thing to use U-Boot on Pis and
> if we make it even more annoying to be recent, there'll be even less
> reason to use U-Boot over over the Pi+TianoCore if you want anything
> more fancy that direct-to-Linux booting.

This is all totally in the weeds at this point. What are you referring to?

I'm talking about turning off OF_BOARD in my private build of U-Boot
so that it picks up the devicetree built with U-Boot. I thought that
was what Mark was saying...?

Regards,
Simon


  reply	other threads:[~2021-11-03 16:47 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-26  0:23 [PATCH v5 00/26] fdt: Make OF_BOARD a boolean option Simon Glass
2021-10-26  0:23 ` [PATCH v5 03/26] arm: qemu: Mention -nographic in the docs Simon Glass
2021-10-26  0:23 ` [PATCH v5 04/26] arm: riscv: qemu: Explain how to extract the generated dt Simon Glass
2021-10-26  0:23 ` [PATCH v5 05/26] arm: qemu: Add a devicetree file for qemu_arm Simon Glass
2021-10-26  0:23 ` [PATCH v5 06/26] arm: qemu: Add a devicetree file for qemu_arm64 Simon Glass
2021-11-01 10:48   ` Peter Maydell
2021-11-01 16:58     ` Simon Glass
2021-11-01 17:33       ` François Ozog
2021-11-01 18:07         ` Tom Rini
2021-11-02 15:00           ` Simon Glass
2021-11-02 17:28             ` Tom Rini
2021-11-03  1:29               ` Simon Glass
2021-11-03  5:29                 ` François Ozog
2021-11-03 14:41                   ` Tom Rini
2021-11-04 11:09                     ` Peter Maydell
2021-11-04 11:22                       ` François Ozog
2021-11-04 11:41                         ` Peter Maydell
2021-11-04 11:48                           ` François Ozog
2021-11-03 14:44                   ` François Ozog
2021-11-03 14:39                 ` Tom Rini
2021-11-02 14:59         ` Simon Glass
2021-11-02 16:57           ` Tom Rini
2021-11-03  1:32             ` Simon Glass
2021-11-03 14:39               ` Tom Rini
2021-10-26  0:23 ` [PATCH v5 07/26] riscv: qemu: Add devicetree files for qemu_riscv32/64 Simon Glass
2021-10-26  6:07 ` [PATCH v5 00/26] fdt: Make OF_BOARD a boolean option François Ozog
2021-10-27 14:08   ` Simon Glass
2021-10-27 15:14     ` François Ozog
2021-10-27 18:23       ` Simon Glass
2021-10-27 19:25         ` Tom Rini
2021-11-03 16:45           ` Simon Glass
2021-11-03 17:21             ` Tom Rini
2021-10-27 20:07         ` François Ozog
2021-11-03  1:20           ` Simon Glass
2021-11-03  4:45             ` François Ozog
2021-10-27 22:30         ` Mark Kettenis
2021-11-03  1:20           ` Simon Glass
2021-11-03  8:22             ` Mark Kettenis
2021-11-03 16:02               ` Tom Rini
2021-11-03 16:45                 ` Simon Glass
2021-11-03 17:36                   ` Mark Kettenis
2021-11-03 15:56             ` Tom Rini
2021-11-03 16:45               ` Simon Glass [this message]
2021-10-27 15:36     ` Tuomas Tynkkynen
2021-10-27 19:13       ` Tom Rini
2021-10-27 18:16     ` Tom Rini
2021-10-27 18:24     ` Tom Rini
2021-11-03 17:13 ` François Ozog

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=CAPnjgZ38AQvH+zKdEdxJWwM9kXVw3s2usoeOveLndTZVkwbZzA@mail.gmail.com \
    --to=sjg@chromium.org \
    --cc=Anastasiia_Lukianenko@epam.com \
    --cc=Oleksandr_Andrushchenko@epam.com \
    --cc=agraf@csgraf.de \
    --cc=albert.u.boot@aribaud.net \
    --cc=andre.przywara@arm.com \
    --cc=awilliams@marvell.com \
    --cc=bmeng.cn@gmail.com \
    --cc=fitzsim@fitzsim.org \
    --cc=francois.ozog@linaro.org \
    --cc=ilias.apalodimas@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=mark.kettenis@xs4all.nl \
    --cc=mbrugger@suse.com \
    --cc=michal.simek@xilinx.com \
    --cc=qemu-devel@nongnu.org \
    --cc=seanga2@gmail.com \
    --cc=swarren@nvidia.com \
    --cc=swarren@wwwdotorg.org \
    --cc=trini@konsulko.com \
    --cc=tuomas.tynkkynen@iki.fi \
    --cc=u-boot@lists.denx.de \
    --cc=vanbaren@cideas.com \
    --cc=xypron.glpk@gmx.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;
as well as URLs for NNTP newsgroup(s).