All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Cochran <yocto@mindchasers.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: Looking for recommendations to help evaluate Freescale LS1021A...
Date: Tue, 22 Oct 2013 22:34:33 -0400	[thread overview]
Message-ID: <526735B9.1020402@mindchasers.com> (raw)
In-Reply-To: <CAP9ODKrQY64t7QvFZeGbGLQvz3iaBr+Ejbim-3pL82xEhWXz=Q@mail.gmail.com>

>
> For i.MX we have many supported boards; you can see the full list at
> our Release Notes[1].
>
> 1. http://freescale.github.io/doc/release-notes/1.5/

Thanks Otavio.  I'm leaning towards the sabre-lite design.  Could 
someone please clarify whether there are any notable differences / 
advantages when comparing the Boundary and Element14 boards?

I see from the jpegs of the two boards that they are very similar and 
are both built from a Freescale sabre lite reference.  Are the only 
differences the connectors and silkscreen?

Bob


>
> The right SoC is very project specific so it is hard to give a good
> advise; regarding possible evaluation boards you have many available
> and I'd say for you to try to choose one with support on this BSP so
> it easy your initial development.
>
> I hope this gives you some pointers where to start.
>
> Regards,
>



  reply	other threads:[~2013-10-23  2:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-17 17:26 Looking for recommendations to help evaluate Freescale LS1021A Bob Cochran
2013-10-18 15:16 ` Otavio Salvador
2013-10-23  2:34   ` Bob Cochran [this message]
2013-10-23  2:51     ` Otavio Salvador
2013-10-23  3:34       ` Eric Nelson
2013-10-23 17:46         ` Bob Cochran
2013-10-23 17:53           ` Eric Nelson
  -- strict thread matches above, loose matches on Subject: below --
2013-10-23 15:24 ad me

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=526735B9.1020402@mindchasers.com \
    --to=yocto@mindchasers.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.