public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Eric Nelson <eric.nelson@boundarydevices.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mx6sabresd: Fix the fdt file for the mx6dl version
Date: Fri, 20 Sep 2013 07:20:04 -0700	[thread overview]
Message-ID: <523C5994.4090409@boundarydevices.com> (raw)
In-Reply-To: <523C50F7.5080706@denx.de>

Thanks, Stefano,

On 09/20/2013 06:43 AM, Stefano Babic wrote:
> Hi Eric,
>
> On 18/09/2013 15:48, Eric Nelson wrote:
>>
>> This allows the boot script to produce the DTB name as shown
>> here:
>>      https://github.com/boundarydevices/u-boot-imx6/blob/staging/board/boundary/nitrogen6x/6x_bootscript.txt#L72
>>
>>
>> If/when you move to a single binary for DQ/DL, you won't have
>> a separate choice as shown above.
>>
>> Let me know your thoughts on this.
>
> It would be helpful if we agree on a set of common variables (across
> architectures) to be automatically set by u-boot at the startup.
>
> The proposed mechanism is already used in u-boot: see the "dieid#"
> variable for TI's OMAP.
>

This maps to the get_imx_type() routine pretty nicely, though
the hash in the environment variable seems weird.

We'll want a board identifier as well, and see other boards
using CONFIG_SYS_BOARD, which seems very reasonable, but the
Nitrogen6x/SABRE Lite will need some additional logic.

  reply	other threads:[~2013-09-20 14:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-18  1:55 [U-Boot] [PATCH] mx6sabresd: Fix the fdt file for the mx6dl version Fabio Estevam
2013-09-18  2:04 ` Otavio Salvador
2013-09-18 13:48 ` Eric Nelson
2013-09-19 11:57   ` Fabio Estevam
2013-09-19 14:01     ` Eric Nelson
2013-09-20 13:44     ` Stefano Babic
2013-09-20 13:43   ` Stefano Babic
2013-09-20 14:20     ` Eric Nelson [this message]
2013-09-20 16:11 ` Stefano Babic

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=523C5994.4090409@boundarydevices.com \
    --to=eric.nelson@boundarydevices.com \
    --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