From: Carlos Rafael Giani <dv@pseudoterminal.org>
To: Daiane Angolini <daiane.angolini@freescale.com>,
"meta-freescale@yoctoproject.org"
<meta-freescale@yoctoproject.org>
Subject: Re: About customizing the image_types_fsl class
Date: Mon, 20 Jan 2014 18:40:12 +0100 [thread overview]
Message-ID: <52DD5F7C.2020109@pseudoterminal.org> (raw)
In-Reply-To: <52DD39FD.9090406@freescale.com>
On 2014-01-20 16:00, Daiane Angolini wrote:
>
> As I know it's supposed to be released today/tomorrow
>
Just had a discussion with developers working on Cubox-I support. They
tried to push MXC SPL support for the CuBox-i upstream, didn't work out
so far. Otavio suggested to use mainline without SPL for now, but I am
skeptical about it. SPL is a very nice feature, it allows me to use the
exact same installation for several Cubox-i machines.
The way I see it, there are two options for me:
1) Use the u-boot fork with MXC SPL support for now, until mainline
supports MXC SPL. Then immediately switch to mainline by applying a
patch to meta-fsl-arm-extra.
2) Use mainline without SPL, and live with the fact that I need a build
for every single CuBox-i machine.
I personally favor (1), especially since it is already fully working for
me. I could send the patches to the mailing list after a little cleanup.
You seem to favor (2), since mainline is usually a better choice than
some odd fork (I agree on this in principle, but in this case, I favor
the fork).
next prev parent reply other threads:[~2014-01-20 17:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 10:12 About customizing the image_types_fsl class Carlos Rafael Giani
2014-01-20 14:12 ` Daiane Angolini
2014-01-20 14:41 ` Carlos Rafael Giani
2014-01-20 15:00 ` Daiane Angolini
2014-01-20 17:40 ` Carlos Rafael Giani [this message]
2014-01-20 19:48 ` Fabio Estevam
2014-01-21 13:04 ` Carlos Rafael Giani
2014-01-21 13:22 ` Fabio Estevam
2014-01-21 13:28 ` Daiane.Angolini
2014-01-20 19:54 ` John Weber
2014-01-20 20:20 ` Otavio Salvador
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=52DD5F7C.2020109@pseudoterminal.org \
--to=dv@pseudoterminal.org \
--cc=daiane.angolini@freescale.com \
--cc=meta-freescale@yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.