From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2] imx: Define common routines to set cpu and board environment variables
Date: Fri, 15 Nov 2013 05:23:43 +0100 [thread overview]
Message-ID: <201311150523.43181.marex@denx.de> (raw)
In-Reply-To: <528579E2.6080906@boundarydevices.com>
Dear Eric Nelson,
> On 11/14/2013 04:30 PM, Marek Vasut wrote:
> > Hi Eric,
> >
> >> Thanks Marek,
> >>
> >> On 11/14/2013 02:22 PM, Marek Vasut wrote:
> >>> Dear Eric Nelson,
> >
> > <snip>
> >
> >> I'm just hoping to get a trivial amount of machinery so a boot
> >>
> >> script can figure out which of a set of DTBs to load:
> >> imx6q-nitrogen6x.dtb,
> >> imx6dl-nitrogen6x.dtb, or
> >> imx6s-nitrogen6x.dtb
> >>
> >> Fabio's recent patch for SABRE SD showed the same need.
> >
> > Full agreement here.
> >
> >> This could be even easier on i.MX6 if we had more formalized (and
> >> lower-case) strings returned by get_imx_type(), but I wanted this
> >> to be very small.
> >>
> >> I'm not sure how consistent the DTB naming is for other machines
> >> or if there's always the equivalent of get_imx_type().
> >
> > In the worst-case scenario, you might end up with some mapping function
> > full of strcmp()s ;-)
>
> This is much easier for us to do, since we defer much of the
> scripting into a boot script.
>
> It will be harder for Fabio to shoe-horn in until we get environment
> settings in an external file...
Yeah, patching the env unto u-boot is the way to go here I guess. What's the
progress on this anyway, Tom ?
Best regards,
Marek Vasut
next prev parent reply other threads:[~2013-11-15 4:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 1:16 [U-Boot] [PATCH V2] imx: Define common routines to set cpu and board environment variables Eric Nelson
2013-11-14 21:22 ` Marek Vasut
2013-11-14 21:38 ` Eric Nelson
2013-11-14 23:30 ` Marek Vasut
2013-11-15 1:33 ` Eric Nelson
2013-11-15 4:23 ` Marek Vasut [this message]
2013-11-15 19:15 ` Tom Rini
2013-11-16 16:14 ` Eric Nelson
2013-11-16 14:03 ` Fabio Estevam
2013-11-16 16:16 ` 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=201311150523.43181.marex@denx.de \
--to=marex@denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox