From: Gary Thomas <gary@mlbassoc.com>
To: Tom Zanussi <tom.zanussi@intel.com>
Cc: Poky Project <poky@yoctoproject.org>
Subject: Re: meta-intel
Date: Fri, 13 May 2011 10:51:02 -0600 [thread overview]
Message-ID: <4DCD6176.5020306@mlbassoc.com> (raw)
In-Reply-To: <1305293225.30469.151.camel@elmorro>
On 05/13/2011 07:27 AM, Tom Zanussi wrote:
> On Fri, 2011-05-13 at 05:08 -0700, Gary Thomas wrote:
>> I'm using meta-intel (git://git.pokylinux.org/meta-intel.git) to
>> test Poky on my Atom-PC (emenlow works fine).
>>
>> Where is the best place to ask for help with this? Perhaps there
>> should be a README in the layer to give such guidance?
>>
>
> Yeah, good point - it would make sense to add 'owner' contact info in
> the BSP READMEs. I'll do that for all the BSPs in meta-intel.
>
>> Now, to my actual question. I'm trying to understand the strange
>> network behaviour I see when running qemu (see yesterday's thread).
>> When I build for qemuXXX, I build& run core-image-sato. On the
>> real hardware (emenlow), I built core-image-sato-live, so I would
>> think the only difference would be the USB-live packaging. So
>> why do I see such a different set of tasks running, once I log
>> in via X? See attached files.
>>
>
> Actually, the set of tasks doesn't look all that different to me. But
> they're also different BSPs (qemu vs emenlow) so I wouldn't expect them
> to be exactly the same (different config options, additional packages,
> etc).
To me, that doesn't make much sense. I want to run core-image-sato,
just with different kernels. The userland experience (i.e. which
programs run by just starting up) should be pretty much the same.
Why does the qemu image start a bunch of NFS and DISTCC stuff that
emenlow does not?
I'm still trying to get a grip on why the network works correctly
on emenlow and fails on qemu...
Thanks
>> Interestingly, the network on the real system (emenlow) works
>> properly. The only problem I have is that /etc/resolv.conf is
>> still wrong, even though I get my network address via DHCP and
>> the DHCP server provides DNS info.
>>
>
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
prev parent reply other threads:[~2011-05-13 16:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 12:08 meta-intel Gary Thomas
2011-05-13 13:27 ` meta-intel Tom Zanussi
2011-05-13 16:51 ` Gary Thomas [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=4DCD6176.5020306@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=poky@yoctoproject.org \
--cc=tom.zanussi@intel.com \
/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.