From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot,2/2] board/db410c: fix fdt address
Date: Fri, 23 Jun 2017 10:32:47 -0400 [thread overview]
Message-ID: <20170623143247.GE27196@bill-the-cat> (raw)
In-Reply-To: <20170620215525.10430-2-robdclark@gmail.com>
On Tue, Jun 20, 2017 at 05:55:25PM -0400, Rob Clark wrote:
> Signed-off-by: Rob Clark <robdclark@gmail.com>
> ---
> Maybe there is a better way to not hardcode this? But at least with
> the build of lk that I have, the fdt table is at 0x81e00000. I guess
> there must be a more robust way to do this, since presumably lk when
> booting the linux kernel directly somehow passes the fdt address.
I would assume that lk does what Documentation/arm64/booting.txt
describes and places the physical address in x0, so you might be able to
implement a save_boot_params that saves this information for later use?
Perhaps even make this somewhat generic for armv8 as there's probably
other cases where U-Boot is being called in this manner? Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170623/6aee73c0/attachment.sig>
next prev parent reply other threads:[~2017-06-23 14:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 21:55 [U-Boot] [PATCH 1/2] board/db410c: add missing linker map entries for efi Rob Clark
2017-06-20 21:55 ` [U-Boot] [PATCH 2/2] board/db410c: fix fdt address Rob Clark
2017-06-23 14:32 ` Tom Rini [this message]
2017-06-23 20:24 ` [U-Boot] [U-Boot,2/2] " Rob Clark
2017-06-23 20:35 ` Rob Clark
2017-06-23 21:17 ` Tom Rini
2017-06-24 22:17 ` [U-Boot] [U-Boot, 1/2] board/db410c: add missing linker map entries for efi Tom Rini
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=20170623143247.GE27196@bill-the-cat \
--to=trini@konsulko.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