From: Darren Hart <darren.hart@intel.com>
To: "Zanussi, Tom" <tom.zanussi@intel.com>
Cc: "Li, Susie" <susie.li@intel.com>,
"Lock, Joshua" <joshua.lock@intel.com>,
"'McCombe, Kevin'" <kevin.mccombe@windriver.com>,
"'Ta, Lieu'" <Lieu.Ta@windriver.com>,
"'Anderson, Paul'" <paul.anderson@windriver.com>,
"'yocto@yoctoproject.org'" <yocto@yoctoproject.org>,
'Bruce Ashfield' <bruce.ashfield@windriver.com>,
"Purdie, Richard" <richard.purdie@intel.com>
Subject: Re: Yocto Linux Project Sync notes
Date: Tue, 19 Oct 2010 14:44:48 -0700 [thread overview]
Message-ID: <4CBE1150.6090807@intel.com> (raw)
In-Reply-To: <1287504271.26874.205.camel@elmorro>
On 10/19/2010 09:04 AM, Zanussi, Tom wrote:
> On Tue, 2010-10-19 at 08:40 -0700, Stewart, David C wrote:
>
>>
>> * demo
>>
>> ** Alex will put the hardware bits together, Darren to write down the description of what needs to come together and wiki-fy it. RP suggests that maybe getting all the pieces running on one hardware might be a good way to try it out just in case.
>>
>
> I can try getting everything running on one machine too - would it make
> sense to try that all on e.g. emenlow, or all on a laptop using qemu, or
> both?
Everything on One machine doesn't make a lot of sense to me, for two
reasons:
1) This is heavily network dependent, making sure the machines can find
eachother is a critical aspect of testing this.
2) Qemu does some magic with tun/tap devices, you have to configure
things to get multicast working between guests. I've tested the
mediatomb image in qemu, it works. We need to test on real hardware.
3) We don't an image that will install everything on the same machine,
and making one doesn't make a lot of sense to me.
4) Running a NAS to serve up media to itself doesn't test the networking
side of things as well.
I'd rather use 3 real devices (even if they are all emenlow or
blacksand) rather than qemu or all on one.
--
Darren
>
> Tom
>
--
Darren Hart
Embedded Linux Kernel
next prev parent reply other threads:[~2010-10-19 21:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4807CBBFD12C484EBEAB6D8DFBDCE47C267E303C06@orsmsx501.amr.corp.intel.com>
2010-10-19 15:40 ` Yocto Linux Project Sync notes Stewart, David C
2010-10-19 16:04 ` Tom Zanussi
2010-10-19 21:42 ` Richard Purdie
2010-10-19 21:44 ` Darren Hart [this message]
2010-10-19 21:48 ` Anderson, Paul
2010-10-19 21:50 ` Darren Hart
2010-10-19 21:51 ` Darren Hart
2010-10-19 22:09 ` Richard Purdie
2010-10-19 22:12 ` Anderson, Paul
2010-10-19 22:11 ` Anderson, Paul
2010-10-19 22:07 ` Tom Zanussi
2010-10-19 16:21 ` Bruce Ashfield
2010-10-19 21:01 ` Alex deVries
2010-10-19 21:12 ` Mark Hatle
2010-10-19 21:48 ` Darren Hart
2010-10-19 21:51 ` Darren Hart
2010-10-19 22:13 ` Yocto Readiness Review Meeting Saul Wold
2010-10-19 22:17 ` Mark Hatle
2010-10-19 22:22 ` Mark Hatle
2010-10-19 22:19 ` Anderson, Paul
2010-10-19 22:31 ` Richard Purdie
2010-10-21 14:11 ` Alex deVries
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=4CBE1150.6090807@intel.com \
--to=darren.hart@intel.com \
--cc=Lieu.Ta@windriver.com \
--cc=bruce.ashfield@windriver.com \
--cc=joshua.lock@intel.com \
--cc=kevin.mccombe@windriver.com \
--cc=paul.anderson@windriver.com \
--cc=richard.purdie@intel.com \
--cc=susie.li@intel.com \
--cc=tom.zanussi@intel.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.