All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] efi_loader: Use system fdt as fallback
Date: Wed, 13 Apr 2016 15:15:08 +0200	[thread overview]
Message-ID: <570E465C.9060205@suse.de> (raw)
In-Reply-To: <570E4268.9080808@suse.de>

On 04/13/2016 02:58 PM, Andreas F?rber wrote:
> Am 11.04.2016 um 16:55 schrieb Alexander Graf:
>> When the user did not pass any device tree or the boot script
>> didn't find any, let's use the system device tree as last resort
>> to get something the payload (Linux) may understand.
>>
>> This means that on systems that use the same device tree for U-Boot
>> and Linux we can just share it and there's no need to manually provide
>> a device tree in the target image.
>>
>> While at it, also copy and pad the device tree by 64kb to give us
>> space for modifications.
>>
>> 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).

We could give the user a warning in the fallback case as well, but 
ideally I'd like to move to a model where all device trees really are 
interchangable and work with every component. So then we would warn the 
user about the preferred default case. I'm not sure that's a great idea.


Alex

  reply	other threads:[~2016-04-13 13:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-11 14:55 [U-Boot] [PATCH] efi_loader: Use system fdt as fallback Alexander Graf
2016-04-13 12:58 ` Andreas Färber
2016-04-13 13:15   ` Alexander Graf [this message]
2016-04-13 13:17     ` Andreas Färber
2016-04-21 11:22 ` [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=570E465C.9060205@suse.de \
    --to=agraf@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.