From: Dennis Gilmore <dennis@ausil.us>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] try to merge different i.MX environment
Date: Fri, 14 Feb 2014 10:14:50 -0600 [thread overview]
Message-ID: <20140214101450.015ee7cf@adria.ausil.us> (raw)
In-Reply-To: <1392390415-25620-1-git-send-email-sbabic@denx.de>
On Fri, 14 Feb 2014 16:06:55 +0100
Stefano Babic <sbabic@denx.de> wrote:
> Signed-off-by: Stefano Babic <sbabic@denx.de>
> CC: Fabio Estevam <fabio.estevam@freescale.com>
> CC: Otavio Salvador <otavio@ossystems.com.br>
> CC: Marek Vasut <marex@denx.de>
> CC: Leo Sartre <lsartre@adeneo-embedded.com>
> CC: Jon Nettleton <jon.nettleton@gmail.com>
> CC: Eric Nelson <eric.nelson@boundarydevices.com>
> CC: b18965 at freescale.com
>
> Hi everybody,
>
> the current built-in environment in most i.MX boards is very similar.
> Even if I always thought that the default environemt is something
> that the user want always customize, I see from all you submitters
> the not hidden desire to have such a common default environment for
> all boards. At least, for i.MX boards.
> Checking in the board configuration files, I see at least the
> following boards that hase "quite" the same built-in environment:
>
I'm working on building a common set environment based on the work by
Stephen Warren for tegra, that would provide for a very usable
experience.
Its the next step forward from the distro config options. Id rather us
get a solution that works across the board than something different per
soc family. looking at how tegra is being done should provide a solid
guide.
Dennis
next prev parent reply other threads:[~2014-02-14 16:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 15:06 [U-Boot] [RFC] try to merge different i.MX environment Stefano Babic
2014-02-14 15:24 ` Otavio Salvador
2014-02-16 16:40 ` Stefano Babic
2014-02-14 16:14 ` Dennis Gilmore [this message]
2014-02-15 11:57 ` Stefano Babic
2014-02-18 17:11 ` Tom Rini
2014-02-14 16:35 ` Wolfgang Denk
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=20140214101450.015ee7cf@adria.ausil.us \
--to=dennis@ausil.us \
--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