Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org, saul.wold@intel.com
Subject: Re: [PATCH 1/1] linux-yocto/qemuppc: fix console and ethernet
Date: Tue, 24 Jan 2012 09:12:07 -0500	[thread overview]
Message-ID: <4F1EBC37.7080603@windriver.com> (raw)
In-Reply-To: <1327402947.19643.86.camel@ted>

On 12-01-24 06:02 AM, Richard Purdie wrote:
> On Mon, 2012-01-23 at 12:54 -0500, Bruce Ashfield wrote:
>> Two issues are fixed with this commit, the ability to use the keyboard
>> on a graphical qemu boot and enabling ethernet by default on a 3.0
>> kernel.
>>
>> The keyboard is fixed via the same method as the other simulations with
>> the addition of console=tty on the qemu command line.
>>
>> Ethernet is fixed by adding a dependency of PCNET32 to the qemuppc
>> configuration, which allows us to build ethernet directly into the image.
>>
>> Signed-off-by: Bruce Ashfield<bruce.ashfield@windriver.com>
>> ---
>>   meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb |    2 +-
>>   meta/recipes-kernel/linux/linux-yocto_3.0.bb    |    2 +-
>>   scripts/runqemu-internal                        |    2 +-
>>   3 files changed, 3 insertions(+), 3 deletions(-)
>
> Merged to master, thanks.
>
> I can confirm qemuppc now has networking as well as graphics which is
> great progress :)

Indeed! It is nice to close out this longstanding issue.

Cheers,

Bruce

>
> Cheers,
>
> Richard
>




      reply	other threads:[~2012-01-24 14:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-23 17:54 [PATCH 0/1] linux-yocto/qemuppc: fix console and ethernet Bruce Ashfield
2012-01-23 17:54 ` [PATCH 1/1] " Bruce Ashfield
2012-01-24 11:02   ` Richard Purdie
2012-01-24 14:12     ` Bruce Ashfield [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=4F1EBC37.7080603@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=saul.wold@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox