All of lore.kernel.org
 help / color / mirror / Atom feed
From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] ARM: qemu-arm: define fdt_addr_r
Date: Fri, 19 Oct 2018 17:17:34 +0900	[thread overview]
Message-ID: <20181019081732.GM32578@linaro.org> (raw)
In-Reply-To: <ec576547-488d-2d70-5639-45c80907664f@suse.de>

On Fri, Oct 19, 2018 at 09:46:51AM +0200, Alexander Graf wrote:
> 
> 
> On 19.10.18 08:33, AKASHI Takahiro wrote:
> > On Thu, Oct 18, 2018 at 09:25:04AM +0200, Alexander Graf wrote:
> >>
> >>
> >> On 18.10.18 00:25, Tuomas Tynkkynen wrote:
> >>> Hi Alexander,
> >>>
> >>> On Tue, 16 Oct 2018 15:04:26 +0200
> >>> Alexander Graf <agraf@suse.de> wrote:
> >>>
> >>> ...
> >>>>>   
> >>>>>> Glancing at cmd/pxe.c,
> >>>>>> there is a problem though, in that if ${fdt_addr_r} were defined,
> >>>>>> a PXE file using the FDTDIR directive would attempt loading a dtb
> >>>>>> file named "<NULL>-qemu-arm.dtb" instead of falling back to using
> >>>>>> ${fdt_addr}. That bug would need to be fixed first before applying
> >>>>>> this patch.  
> >>>>
> >>>> Well, and that load will fail and everyone's happy, no? 
> >>>
> >>> No, because currently if DTB loading from the filesystem/tftp is
> >>> attempted and it fails, it aborts the boot. It doesn't matter if it's
> >>> via a 'FDT' or 'FDTDIR' directive. In the case of typical hardware
> >>> that's probably the desired behaviour.
> >>>
> >>> I guess the qemu_arm + FDTDIR case can be fixed by not attempting
> >>> a .dtb load if the default fdtfile is not known due to $soc or $board
> >>> being unset. At least I doubt that some other board could be relying
> >>> on a filename containing literally "<NULL>" :)
> >>
> >> Well - IIRC $soc and $board should also always be defined ;). So yet
> >> another thing to fix in the QEMU port.
> > 
> > See my patch below. Are you happy with it?
> > (qemu-qemu-arm.dtb doesn't make sense to me, though :)
> > 
> >>>
> >>>> IMHO we should
> >>>> fall back to $fdtcontroladdr always
> >>>
> >>> FWIW, to me the idea of passing $fdtcontroladdr to the OS has always
> >>> filled me with dread. On top of the usual backwards- and
> >>> forwards-compatibility problems that happen when mixing and matching
> >>> kernels and DTBs from different releases, you now have to deal with
> >>
> >> That's something that we seriously as a community need to get sorted
> >> out. We're pushing hard for it in the EBBR context. The fact that people
> >> are afraid of putting *hardware desciption* into their firmware is just
> >> mind boggling.
> > 
> > I don't have a strong opinion, but it seems to me that 'fall-back' approach
> > is quite normal. If it doesn't work on a specific board, 'fdt_addr'
> > should be defined.
> > 
> > Thanks,
> > -Takahiro Akashi
> > 
> > 
> >>> issues like U-Boot specific .dts that are majorly diverged from Linux
> >>> ones, or where the .dts is otherwise from Linux but the U-Boot specific
> >>
> >> These case should really be the minority. And if you see those, please
> >> fix them.
> >>
> >>> additions break it for Linux, or where the .dts used is wrong for the
> >>
> >> I've never seen a case where a U-Boot addition broke the DT for Linux.
> >>
> >>> specific hardware revision but close enough for U-Boot's purposes,
> >>> and so on...
> >>
> >> Again, something that just needs fixing. Device trees belong to the
> >> entity that knows hardware, not to the OS. Otherwise you lose the
> >> abstraction layer that DT gives you and you lose the ability to run
> >> "generic" kernels. And of course you break the ecosystem, because now
> >> good luck running BSD, your own little toy OS, etc ;)
> >>
> >>
> >> Alex
> > 
> > ===8<===
> > From 47b26a86359a3b612e890f2ca2d5d20092f9f4e1 Mon Sep 17 00:00:00 2001
> > From: AKASHI Takahiro <takahiro.akashi@linaro.org>
> > Date: Fri, 19 Oct 2018 15:22:02 +0900
> > Subject: [PATCH] arm: qemu: rework Kconfig
> > 
> > Define SYS_SOC and move SYS_* to a canonical place (under board).
> > 
> > Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org>
> 
> Looks good enough to me, but it's up to Tuomas to double check and take
> as he's the qemu-arm maintainer :).
> 
> It also usually helps to post the patch as a new message, not buried
> inside a thread ;).

OK. Since I found a small bug, I will send out a new patch separately.

-Takahiro Akashi

> 
> Alex

  reply	other threads:[~2018-10-19  8:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-12  5:07 [U-Boot] [PATCH 1/2] efi_loader: rework fdt handling in distro boot script AKASHI Takahiro
2018-10-12  5:07 ` [U-Boot] [PATCH 2/2] ARM: qemu-arm: define fdt_addr_r AKASHI Takahiro
2018-10-15  1:01   ` Tuomas Tynkkynen
2018-10-15  5:14     ` AKASHI Takahiro
2018-10-16 13:04       ` Alexander Graf
2018-10-17 22:25         ` Tuomas Tynkkynen
2018-10-18  7:25           ` Alexander Graf
2018-10-19  6:33             ` AKASHI Takahiro
2018-10-19  7:46               ` Alexander Graf
2018-10-19  8:17                 ` AKASHI Takahiro [this message]
2018-10-24 10:36             ` Tuomas Tynkkynen
2018-10-16 13:15 ` [U-Boot] [PATCH 1/2] efi_loader: rework fdt handling in distro boot script Alexander Graf
2018-10-18  2:07   ` AKASHI Takahiro
2018-10-18  7:31     ` Alexander Graf
2018-10-19  7:20       ` AKASHI Takahiro
2018-10-19  7:31         ` Alexander Graf
2018-10-19  8:32           ` AKASHI Takahiro
2018-10-19  8:50             ` Alexander Graf

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=20181019081732.GM32578@linaro.org \
    --to=takahiro.akashi@linaro.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.