From: "Andreas Färber" <afaerber@suse.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] efi_loader: Put fdt into convenient location
Date: Wed, 13 Apr 2016 14:57:16 +0200 [thread overview]
Message-ID: <570E422C.6040708@suse.de> (raw)
In-Reply-To: <570E40CE.2010303@suse.de>
Am 13.04.2016 um 14:51 schrieb Andreas F?rber:
> Am 11.04.2016 um 23:51 schrieb Alexander Graf:
>> The uEFI spec doesn't dictate where the device tree should live at, but
>> legacy 32bit ARM grub2 has some assumptions that it may stay at its place
>> when it's already loaded by the firmware.
>>
>> So let's put it somewhere where Linux that comes after would happily find
>> it - around the recommended 128MB line.
>>
>> Signed-off-by: Alexander Graf <agraf@suse.de>
>
> Tested-by: Andreas F?rber <afaerber@suse.de>
>
> It definitely avoids a warning message. However, it does not always
> allow Linux to actually boot, e.g. on jetson-tk1 (patch sent).
Err, wrong patch for comment but still tested. :)
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
GF: Felix Imend?rffer, Jane Smithard, Graham Norton
HRB 21284 (AG N?rnberg)
next prev parent reply other threads:[~2016-04-13 12:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 21:51 [U-Boot] [PATCH 1/2] efi_loader: Put fdt into convenient location Alexander Graf
2016-04-11 21:51 ` [U-Boot] [PATCH 2/2] efi_loader: Expose ascending efi memory map Alexander Graf
2016-04-13 12:52 ` Andreas Färber
2016-04-21 11:22 ` [U-Boot] [U-Boot, " Tom Rini
2016-04-13 12:51 ` [U-Boot] [PATCH 1/2] efi_loader: Put fdt into convenient location Andreas Färber
2016-04-13 12:57 ` Andreas Färber [this message]
2016-04-21 11:22 ` [U-Boot] [U-Boot, " 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=570E422C.6040708@suse.de \
--to=afaerber@suse.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 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.