From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: tegra: restrict usable RAM size further
Date: Thu, 30 Jul 2015 13:47:44 -0600 [thread overview]
Message-ID: <55BA7F60.4070402@wwwdotorg.org> (raw)
In-Reply-To: <CAPnjgZ3RQFCpWdX3qSJ9+44yE82w_sGmk+mD4-+G58Un_dNbzw@mail.gmail.com>
On 07/30/2015 01:00 PM, Simon Glass wrote:
> Hi Stephen,
>
> On 30 July 2015 at 12:47, Stephen Warren <swarren@wwwdotorg.org> wrote:
...
>> At least initially, we're targeting booting the system with the same
>> bootloader that L4T and Android use for unification. U-Boot runs after the
>> base security/... environment is set up to provide a flexible user
>> experience for untrusted OS loading. Hopefully this won't make flashing a
>> system too much more complex, but there will inevitably be some differences.
>> Hopefully it'll get mostly hidden by tegra-uboot-flasher or some other tool.
>>
>> At some point I hope we'll be able to get U-Boot to act as the first stage
>> bootloader rather than just the non-secure bootloader. However, that
>> requires a lot more work so certainly isn't something that's in the first
>> round of Tegra210 support.
>
> Thanks for the explanation. Booting ARM devices might get as hard as
> x86 if we try really hard. Maybe we can add some run-time services as
> well...good luck!
Well, at least PSCI is required by the ARM64 kernel now I believe, and
there's plenty of push for ACPI in some environments too, so I expect
the complexity will indeed converge!
next prev parent reply other threads:[~2015-07-30 19:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-29 19:47 [U-Boot] [PATCH] ARM: tegra: restrict usable RAM size further Stephen Warren
2015-07-30 11:04 ` Thierry Reding
2015-07-30 15:43 ` Stephen Warren
2015-07-30 15:52 ` Simon Glass
2015-07-30 18:47 ` Stephen Warren
2015-07-30 19:00 ` Simon Glass
2015-07-30 19:47 ` Stephen Warren [this message]
2015-08-05 18:33 ` Stephen Warren
2015-08-05 19:22 ` Tom Warren
2015-08-05 19:27 ` Stephen Warren
2015-08-05 19:30 ` Tom 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=55BA7F60.4070402@wwwdotorg.org \
--to=swarren@wwwdotorg.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.