public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] Remove static display data
Date: Fri, 26 Jul 2013 08:49:13 -0600	[thread overview]
Message-ID: <51F28C69.9050406@wwwdotorg.org> (raw)
In-Reply-To: <51F28AEC.3070909@denx.de>

On 07/26/2013 08:42 AM, Stefano Babic wrote:
> On 26/07/2013 16:04, Eric Nelson wrote:
>> The real question we have regarding DT is the timing. We're shipping
>> DT files on secondary storage (SATA/SD card), and want/need something
>> local (i.e. env in SPI-NOR) to present a U/I if either no storage
>> available or if something goes wrong.
> 
> ok, understood.

For Tegra (and I assume the similar Exynos support), the DTB that's used
by U-Boot is considered part of the U-Boot binary, so whatever loads
that into RAM also automatically picks up the DTB, so there's no need to
do any kind of storage access to retrieve it

Of course, the U-Boot code apparently supports other methods, such as
hard-coding a memory-mapped address etc.; take a lok at the DT-related
config options.

...
>> Is Tegra somehow using DT to configure U-Boot display?
>> I'm not finding the code.
> 
> ./board/compal/dts/tegra20-paz00.dts seems doing that, but I have no
> experience with it ;(

Yes, that's working fine.

  reply	other threads:[~2013-07-26 14:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-25 18:21 [U-Boot] [RFC] Remove static display data Robert Winkler
2013-07-26  7:50 ` Anatolij Gustschin
2013-07-26  8:43   ` Stefano Babic
2013-07-26 14:04     ` Eric Nelson
2013-07-26 14:42       ` Stefano Babic
2013-07-26 14:49         ` Stephen Warren [this message]
2013-07-26 19:41           ` Eric Nelson
2013-07-27  0:42         ` Eric Nelson
2013-07-27  1:34           ` Troy Kisky
2013-07-27 19:05           ` Simon Glass
2013-07-28 16:57             ` Eric Nelson
2013-07-28 18:09               ` Simon Glass
2013-07-28 19:22                 ` Eric Nelson
2013-07-29 16:50                   ` Simon Glass
2013-07-26 14:00   ` Eric Nelson

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=51F28C69.9050406@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox