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] [PATCH V2] add README.distro file
Date: Mon, 12 Jan 2015 10:36:27 -0700	[thread overview]
Message-ID: <54B4061B.8020305@wwwdotorg.org> (raw)
In-Reply-To: <20150110124459.4e0d1378@ra.ausil.us>

On 01/10/2015 11:44 AM, Dennis Gilmore wrote:
> On Mon, 05 Jan 2015 12:55:46 -0700
> Stephen Warren <swarren@wwwdotorg.org> wrote:
>
>> On 12/28/2014 03:09 AM, Ian Campbell wrote:
>>> On Mon, 2014-12-22 at 13:46 -0700, Stephen Warren wrote:
>>>> [...]
>>>> +
>>>> +The U-Boot "syslinux" and "pxe boot" commands require a number of
>>>> environment +variables be set. Default values for these variables
>>>> are often hard-coded into +CONFIG_EXTRA_ENV_SETTINGS in the
>>>> board's U-Boot configuration file, so that +the user doesn't have
>>>> to configure them. +
>>>> +fdt_addr:
>>>> +
>>>> +  Optional. If specified a dtb to boot the system must be
>>>> available at the
>>>> +  given address.
>>>> +
>>>> +fdt_addr_r:
>>>> +
>>>> +  Mandatory.
>>>
>>> Isn't this one only mandatory if ${fdt_addr} is not given?
>>
>> Yes. I guess it's mandatory for at least one of fdt_addr or
>> fdt_addr_r to be set, according to common/cmd_pxe.c:
 >
> fdt_addr_r is actually mandatory unless you do not support device
> tree at all, which is not expected at all anymore. The reason being
> that the user/distro can override the vendor supplied dtb for whatever
> reason, by supplying a fdt/dtb fdtdir/dtbdir entry in extlinux.conf  in
> the past at times on calxeda hardware we had to override the dtb to work
> with newer kernels until we could update the systems firmware.

That's a good point. I'll revise the README again and repost a V4.

      reply	other threads:[~2015-01-12 17:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-22 20:46 [U-Boot] [PATCH V2] add README.distro file Stephen Warren
2014-12-28  9:26 ` Ian Campbell
2015-01-05 19:50   ` Stephen Warren
2015-01-11  9:45   ` Ian Campbell
2015-01-11 17:54     ` Stephen Warren
2015-01-11 18:15       ` Tom Rini
2015-01-12 17:34         ` Stephen Warren
2015-01-12 17:57           ` Ian Campbell
2015-01-12 18:47             ` Stephen Warren
2015-01-12 19:57             ` Sjoerd Simons
2015-01-12 22:41               ` Dennis Gilmore
2015-01-23 17:48             ` Rob Herring
2014-12-28 10:09 ` Ian Campbell
2015-01-05 19:55   ` Stephen Warren
2015-01-10 18:44     ` Dennis Gilmore
2015-01-12 17:36       ` Stephen Warren [this message]

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=54B4061B.8020305@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