From: Bob Cochran <yocto@mindchasers.com>
To: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Looking for recommendations to help evaluate Freescale LS1021A...
Date: Thu, 17 Oct 2013 13:26:24 -0400 [thread overview]
Message-ID: <52601DC0.7080707@mindchasers.com> (raw)
Hello All,
Most of you are probably aware that Freescale has announced an ARM-based
QorIQ device built around an ARM (dual) Cortex-A7.
http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=LS1021A
We're interested in moving forward with this SoC, but we first want to
benchmark in hardware some relevant applications to see if the dual
Cortex-A7 @ 1GHz will have enough processing power to do what we need.
Can you please reply with what you think would be the best evaluation
board to bring in house that provides a fair representation of the
Cortex-A7's performance? BTW, each core has 32KB data & instruction L1
caches, and it shares a 512KB L2 cache.
I'm thinking it will probably be an i.MX solution (maybe i.MX53 QS or
i.MX6 Sabre Lite?). However, I would like to hear from the developers
working with these boards on a regular basis about the stability and
level of support for the particular board they're working with.
We'll also need to work out which HW debugger to bring in, so I would
love to hear any recommendations for this.
Also, I suppose we should be looking at non Freescale ARM eval boards,
too.
Thanks,
Bob
next reply other threads:[~2013-10-17 17:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-17 17:26 Bob Cochran [this message]
2013-10-18 15:16 ` Looking for recommendations to help evaluate Freescale LS1021A Otavio Salvador
2013-10-23 2:34 ` Bob Cochran
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=52601DC0.7080707@mindchasers.com \
--to=yocto@mindchasers.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.