From: Eric Nelson <eric.nelson@boundarydevices.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] MX6 solo support
Date: Sat, 24 Nov 2012 12:44:27 -0700 [thread overview]
Message-ID: <50B1239B.8080203@boundarydevices.com> (raw)
In-Reply-To: <CAOMZO5AddTaFNmrOa-Sdk=0Fuvx6tUxP11j5k0ahocK9ZdkLmA@mail.gmail.com>
On 11/24/2012 11:26 AM, Fabio Estevam wrote:
> Hi,
>
> Just wondering if someone has already started adding mx6solo support
> into mainline U-boot?
>
> Carolyn,
>
> You posted some questions about mx6solo in this list. Were you using
> mainline U-boot or the FSL version?
>
> In case you were using mainline U-boot, and would like to share some
> mx6solo related patches, I would be glad to to receive them and submit
> them.
>
> Regards,
>
> Fabio Estevam
>
Hi Fabio,
Troy's been working diligently to push Solo support, but it's taking
a while to work through the bits. The first attempt, which allowed a
single binary to be used on Solo->Quad required the use of i.MX
plugins and was more or less rejected with pushback to use SPL instead.
We have some Solo boards out in the field using plugins from this branch:
https://github.com/boundarydevices/u-boot-imx6/tree/solo-dl-staging
Based on the feedback, our plan was (is) to create separate board
file for the processor variants, but don't want to duplicate everything,
so we planned on these steps:
- Add preprocessor support to imximage.
This is stalled at the moment, waiting for Stefano
and Tom to resolve differences
- Push nitrogen6q board file for Quad/Dual
- Create a new board for nitrogen6s (Solo/Dual Lite)
We've been at the first stage for a while though.
Regards,
Eric
prev parent reply other threads:[~2012-11-24 19:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-24 18:26 [U-Boot] MX6 solo support Fabio Estevam
2012-11-24 19:44 ` 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=50B1239B.8080203@boundarydevices.com \
--to=eric.nelson@boundarydevices.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