From: akuster808 <akuster808@gmail.com>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/3] Add qemuppc64 target
Date: Wed, 22 Jun 2016 09:54:31 -0700 [thread overview]
Message-ID: <576AC2C7.5080801@gmail.com> (raw)
In-Reply-To: <6b1040c9-6ca6-92e5-ac9d-c2a74d67db8f@linux.intel.com>
Alex,
On 06/22/2016 04:43 AM, Alexander Kanavin wrote:
> On 06/21/2016 07:03 PM, Burton, Ross wrote:
>> Can you also see if usermode qemu needs to be changed for ppc64 as
>> well
>>
>> It needs enabling entirely - qemu-ppc64 doesn't exist currently so every
>> build-time postinst fails.
>
When I enable qemu-ppc64 in the OE build, I can boot the kernel and get
to the login prompt. When I type in the passwd, nothing is echo'd back.
If I use the Ubuntu 14.04 qemu-2.0 version , it works.
> There were reports that qemu-ppc64 does not work even when enabled:
>
> https://lists.yoctoproject.org/pipermail/yocto/2016-April/029698.html
Haven't seen those errors.
- armin
>
> Alex
>
next prev parent reply other threads:[~2016-06-22 16:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 14:38 [PATCH 0/3] Add qemuppc64 target Armin Kuster
2016-06-21 14:39 ` [PATCH 1/3] machine: add qemuppc64 machine Armin Kuster
2016-06-21 14:39 ` [PATCH 2/3] linux-yocto: add qemuppc64 Armin Kuster
2016-06-21 15:01 ` Bruce Ashfield
[not found] ` <57695F73.80209@mvista.com>
2016-06-21 15:39 ` Bruce Ashfield
2016-06-21 14:39 ` [PATCH 3/3] runqemu: Add qemuppc64 Armin Kuster
2016-06-21 15:59 ` [PATCH 0/3] Add qemuppc64 target Khem Raj
2016-06-21 16:03 ` Burton, Ross
2016-06-22 11:43 ` Alexander Kanavin
2016-06-22 16:54 ` akuster808 [this message]
[not found] ` <57698C05.7020704@mvista.com>
2016-06-21 19:54 ` Khem Raj
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=576AC2C7.5080801@gmail.com \
--to=akuster808@gmail.com \
--cc=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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.