From: Mark Hatle <mark.hatle@windriver.com>
To: yocto@yoctoproject.org
Subject: Re: RFC: "Demo Use Cases" documentation for the web page
Date: Fri, 22 Oct 2010 17:17:05 -0500 [thread overview]
Message-ID: <4CC20D61.8020301@windriver.com> (raw)
In-Reply-To: <4CC20A7C.10408@linux.intel.com>
On 10/22/10 5:04 PM, Darren Hart wrote:
> On 10/22/2010 02:04 PM, Alex deVries wrote:
>>
>> On 2010-10-22, at 4:22 PM, Darren Hart wrote:
>>
>>>> boards list used in this demo.
>>>
>>> Hrm... do we want to explicitly call them out? The point is that it was
>>> multi-architecture, but for some to recreate it, the point is that it
>>> doesn't really matter what hardware they have - poky can build for any
>>> of them.
>>>
>>> What do others think, should we mention the specific boards in use at
>>> the demo?
>>
>>
>> Yeah, I think we should. It proves that it really does run on other hardware, and the demo hw is the example. Showing product names helps shake the image that this is IA-only.
>
> OK, so can someone provide me with an appropriate list of the non-IA
> platforms? I know them as "The MIPS board" "The PPC board" etc.
>
arm - beagleboard (I don't know the revision)
ppc - fsl-mpc8315e-rdb
mips - Ubiquity Networks Router Station Pro a.k.a. MIPS Linux Starter Kit
next prev parent reply other threads:[~2010-10-22 22:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 23:00 RFC: "Demo Use Cases" documentation for the web page Darren Hart
2010-10-22 0:26 ` Tian, Kevin
2010-10-22 20:22 ` Darren Hart
2010-10-22 21:04 ` Alex deVries
2010-10-22 22:04 ` Darren Hart
2010-10-22 22:17 ` Mark Hatle [this message]
2010-10-22 22:21 ` Mark Hatle
2010-10-22 1:32 ` Tom Zanussi
2010-10-22 17:35 ` Stewart, David C
2010-10-22 17:44 ` Dirk Hohndel
2010-10-22 17:51 ` Mark Hatle
2010-10-22 22:02 ` RFC V2: " Darren Hart
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=4CC20D61.8020301@windriver.com \
--to=mark.hatle@windriver.com \
--cc=yocto@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.