From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/6] Upstream environment changes being used in Yocto/OE
Date: Mon, 1 Jul 2013 09:30:05 -0400 [thread overview]
Message-ID: <20130701133005.GB16630@bill-the-cat> (raw)
In-Reply-To: <CAP9ODKpxtSUHPHhN4drQVtWqiS1EyLnKJmCcAKSP5MdvgP0Y1g@mail.gmail.com>
On Mon, Jul 01, 2013 at 10:25:46AM -0300, Otavio Salvador wrote:
> On Mon, Jul 1, 2013 at 10:20 AM, Tom Rini <trini@ti.com> wrote:
> > On Fri, Jun 28, 2013 at 06:56:46PM -0300, Fabio Estevam wrote:
> >
> >> On Fri, Jun 28, 2013 at 6:52 PM, Otavio Salvador
> >> <otavio@ossystems.com.br> wrote:
> >> > This changes were being done in every version of U-Boot and it
> >> > makes sense to try to merge them upstream.
> >> >
> >> > Please review them and ack/nack them.
> >>
> >> I think the series look good:
> >>
> >> Reviewed-by: Fabio Estevam <fabio.estevam@freescale.com>
> >
> > We aren't breaking compat with other distros, are we? In TI-land where
> > (for better or worse) we often have a FAT partition we're dealing with
> > too, we use (and can have OE spit out) a uEnv.txt file that's
> > user-editable and imported to the environment that would update these
> > variables. I suspect there's not an easy analog here but I thought I'd
> > bring it up.
>
> We've not used uEnv.txt files for this in Freescale's Yocto support
> but patched the U-Boot source code to make it work out of box. I think
> these patches could go in now that Freescale is using Yocto more
> extensivelly for ARM platforms so we avoid same patches to be ported
> for every new U-Boot release.
Right well and good. But part of the reason we use it here is that
meta-various-ti-things may use a different layout from
meta-community-oriented-distro and this lets us handle both with just a
tweak in the various-ti-things layer to add a text file. Again, may not
apply here and that's fine. Heck, we're trying to move more towards
always just using the community layout.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20130701/50f7315c/attachment.pgp>
next prev parent reply other threads:[~2013-07-01 13:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 21:52 [U-Boot] [PATCH 0/6] Upstream environment changes being used in Yocto/OE Otavio Salvador
2013-06-28 21:52 ` [U-Boot] [PATCH 1/6] mx53loco: Change default environment to cope with OE changes Otavio Salvador
2013-06-28 21:52 ` [U-Boot] [PATCH 2/6] mx6qsabrelite: " Otavio Salvador
2013-06-28 21:52 ` [U-Boot] [PATCH 3/6] mx6slevk: " Otavio Salvador
2013-06-28 21:52 ` [U-Boot] [PATCH 4/6] wandboard: " Otavio Salvador
2013-06-28 21:52 ` [U-Boot] [PATCH 5/6] mx51evk: " Otavio Salvador
2013-07-12 7:38 ` Stefano Babic
2013-06-28 21:52 ` [U-Boot] [PATCH 6/6] mx53ard: " Otavio Salvador
2013-06-28 21:56 ` [U-Boot] [PATCH 0/6] Upstream environment changes being used in Yocto/OE Fabio Estevam
2013-07-01 13:20 ` Tom Rini
2013-07-01 13:25 ` Otavio Salvador
2013-07-01 13:30 ` Tom Rini [this message]
2013-07-01 13:32 ` Otavio Salvador
2013-07-04 11:46 ` Albert ARIBAUD
2013-07-12 7:43 ` Stefano Babic
2013-07-12 10:40 ` Fabio Estevam
2013-07-12 11:10 ` 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=20130701133005.GB16630@bill-the-cat \
--to=trini@ti.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