From: Eric Nelson <eric.nelson@boundarydevices.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: imx6qsabrelite and nitrogen6x
Date: Wed, 12 Jun 2013 13:19:12 -0700 [thread overview]
Message-ID: <51B8D7C0.30507@boundarydevices.com> (raw)
In-Reply-To: <CAP9ODKpbtL6Ys4b-xJX0JgjfCLb=GRYjAT3AeSr5DS9OUr8k1g@mail.gmail.com>
Hi all,
On 06/12/2013 12:32 PM, Otavio Salvador wrote:
> Hello Daiane,
>
> On Wed, Jun 12, 2013 at 4:18 PM, Daiane Angolini
> <daiane.angolini@freescale.com <mailto:daiane.angolini@freescale.com>>
> wrote:
>
> I've been seen that several people try to get imx6qsabrelite up and
> running and end up getting an error.
>
> I think we can drop imx6qsabrelite.conf and point a comment on
> nitrogen6x.conf file in order to avoid this kind of situation.
>
> Anyone has a better idea?
>
>
> I understand your motivation for it and I agree it does makes hard for
> some users. I am just unsure if we ought to drop it.
>
> Eric, please advice.
>
I'm okay with dropping the imx6qsabrelite.conf file.
There is another vendor producing boards "to the SABRE Lite design",
but I think even they are best served by using our kernel and
configuration.
The Freescale kernel team is still making updates to SABRE Lite in
the kernel tree, but we're pulling them into the nitrogen6x/sabre lite
board file and configuration fairly quickly.
Fabio and the Freescale U-Boot team are also maintaining updates
to the mx6qsabrelite board files, but I don't know whether anybody
is actually using it. The README file has a big hack to over-ride
boot to SPI NOR to keep Linaro's build process happy:
http://git.denx.de/u-boot.git/?p=u-boot.git;a=blob;f=board/freescale/mx6qsabrelite/README;h=12a9c856cffe1f4cdd73c9d67b31bd41b1a7303b;hb=HEAD
But I don't think Linaro is active with i.MX6 at the moment.
prev parent reply other threads:[~2013-06-12 20:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 19:18 imx6qsabrelite and nitrogen6x Daiane Angolini
2013-06-12 19:32 ` Otavio Salvador
2013-06-12 20:19 ` Eric Nelson [this message]
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=51B8D7C0.30507@boundarydevices.com \
--to=eric.nelson@boundarydevices.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
/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.