All of lore.kernel.org
 help / color / mirror / Atom feed
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: i.MX6SL EVK
Date: Sat, 16 Mar 2013 09:00:51 -0700	[thread overview]
Message-ID: <51449733.2030607@boundarydevices.com> (raw)
In-Reply-To: <CAP9ODKo1OfCif3_S2uJ01z_M_qbPWdj5G4a=F5ZbXqE6a92TEA@mail.gmail.com>

Hi Otavio,

On 03/16/2013 07:08 AM, Otavio Salvador wrote:
> On Fri, Mar 15, 2013 at 9:30 PM, Eric Nelson
> <eric.nelson@boundarydevices.com> wrote:
>> On 03/14/2013 09:44 AM, Otavio Salvador wrote:
>>>
>>> On Thu, Mar 14, 2013 at 1:10 PM, Michael Urbaniak <MikeU@ebtron.com>
>>> wrote:
>>>>
>>>> I am very interested in moving from LTIB to Yocto for an i.MX6SL project
>>>> we
>>>> currently have.
>>>
>>>
>>> I am glad to learn it ;-)
>>>
>>>> Is there support at this time for the i.MX6SL-EVK?  If not I suppose I
>>>> need
>>>> to learn about modifying BSP’s.
>>>
>>>
>>> Not at this moment as said by Daiane; it shouldn't be hard but it does
>>> need to be done.
>>>
>>
>> FWIW, the Yocto build for Nitrogen6X boots right up with a Solo
>> processor.
>>
>> In order to get VPU acceleration, you'll need to copy in the
>> firmware file "vpu_fw_imx6d.bin" though.
>>
>> The GPU seems to come right up.
>
> We need to adapt to use the official kernel for the board.
>

Of course. The i.MX6SL-EVK will need both custom U-Boot and kernel.

My message was really for Nitrogen6X customers that might
be interested in evaluating the performance of Solo or Dual-Lite
CPUs.

> I think it did work for your board because Boundary's U-Boot already
> handles it however we currently use U-Boot 2013.01 by default here and
> this still doesn't cope with the other variants of i.MX6 SoC.
>

Yep. This is a benefit of booting to SPI-NOR.

> What is the Boundary's plans for the kernel? A single kernel tree or
> two (as done by FSL)?
>
Single kernel.

We did this by creating "pads-mx6_sabrelite.h" and including it
twice: once for Dual/Quad and again for Solo/Dual-Lite:
	https://github.com/boundarydevices/linux-imx6/blob/boundary-imx_3.0.35_1.1.1/arch/arm/mach-mx6/board-mx6q_sabrelite.c#L124

This allows us to boot all of our SD cards on all of our boards.

We even have a boot script for Adeneo's Windows CE7 to make it
easy to swap.

Regards,


Eric


      reply	other threads:[~2013-03-16 16:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-14 16:10 i.MX6SL EVK Michael Urbaniak
2013-03-14 16:18 ` Daiane Angolini
2013-03-14 16:44 ` Otavio Salvador
2013-03-16  0:30   ` Eric Nelson
2013-03-16 14:08     ` Otavio Salvador
2013-03-16 16:00       ` 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=51449733.2030607@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.