From: Tuomas Tynkkynen <tuomas@tuxera.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] rpi: Fix device tree path on ARM64
Date: Mon, 9 Jan 2017 15:34:28 +0200 [thread overview]
Message-ID: <20170109153428.44f6767e@duuni> (raw)
In-Reply-To: <42cac7aa-2e13-2ca8-6d1a-226e3f573883@wwwdotorg.org>
On Thu, 5 Jan 2017 16:44:43 -0700
Stephen Warren <swarren@wwwdotorg.org> wrote:
> On 01/03/2017 03:39 AM, Tuomas Tynkkynen wrote:
> > The directory structure of device tree files produced by the kernel's
> > 'make dtbs_install' is different on ARM64, the RPi3 device tree file is
> > in a 'broadcom' subdirectory there. Make the set_fdtfile function account
> > for this so that the distro boot scripts can locate the DTB file.
>
> I'm not 100% sure there's an expectation/guarantee that "make
> dtbs_install" will be used to create the DTB layout that the bootloader
> uses, although I suppose this is a reasonable thing to do.
>
It certainly would be nice from the distro's point of view to have the same
scripts work on both ARM and ARM64.
> > diff --git a/board/raspberrypi/rpi/rpi.c b/board/raspberrypi/rpi/rpi.c
>
> > static void set_fdtfile(void)
>
> > - fdtfile = model->fdtfile;
> > + if (IS_ENABLED(CONFIG_ARM64))
> > + strcat(fdtfile, "broadcom/");
> > + strcat(fdtfile, model->fdtfile);
>
> Instead of writing code for this, and in particular code that doesn't
> check for buffer size/overflow/..., wouldn't it be better to simply edit
> the RPi 3 entry in rpi_models_new_scheme[] to contain "broadcom/" in the
> DTB filename string?
>
I did it this way to keep the 32-bit builds looking in the old location,
as that's where it was planned to be added for 32-bit ARM:
https://patchwork.kernel.org/patch/9148261/
I did consider some preprocessor magic and compile-time string concatenation
but this seemed a cleaner way.
next prev parent reply other threads:[~2017-01-09 13:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-03 10:39 [U-Boot] [PATCH] rpi: Fix device tree path on ARM64 Tuomas Tynkkynen
2017-01-05 23:44 ` Stephen Warren
2017-01-09 13:34 ` Tuomas Tynkkynen [this message]
2017-01-10 2:48 ` Stephen Warren
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=20170109153428.44f6767e@duuni \
--to=tuomas@tuxera.com \
--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