* meta-intel
@ 2011-05-13 12:08 Gary Thomas
2011-05-13 13:27 ` meta-intel Tom Zanussi
0 siblings, 1 reply; 3+ messages in thread
From: Gary Thomas @ 2011-05-13 12:08 UTC (permalink / raw)
To: Poky Project
[-- Attachment #1: Type: text/plain, Size: 1129 bytes --]
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?
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.
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
------------------------------------------------------------
[-- Attachment #2: emelnow.ps --]
[-- Type: application/postscript, Size: 3714 bytes --]
[-- Attachment #3: qemu.ps --]
[-- Type: application/postscript, Size: 6302 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: meta-intel
2011-05-13 12:08 meta-intel Gary Thomas
@ 2011-05-13 13:27 ` Tom Zanussi
2011-05-13 16:51 ` meta-intel Gary Thomas
0 siblings, 1 reply; 3+ messages in thread
From: Tom Zanussi @ 2011-05-13 13:27 UTC (permalink / raw)
To: Gary Thomas; +Cc: Poky Project
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).
Tom
> 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.
>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: meta-intel
2011-05-13 13:27 ` meta-intel Tom Zanussi
@ 2011-05-13 16:51 ` Gary Thomas
0 siblings, 0 replies; 3+ messages in thread
From: Gary Thomas @ 2011-05-13 16:51 UTC (permalink / raw)
To: Tom Zanussi; +Cc: Poky Project
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
------------------------------------------------------------
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2011-05-13 16:51 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-05-13 12:08 meta-intel Gary Thomas
2011-05-13 13:27 ` meta-intel Tom Zanussi
2011-05-13 16:51 ` meta-intel Gary Thomas
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.