From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org, saul.wold@intel.com
Subject: [PATCH 0/1] linux-yocto/qemuppc: fix console and ethernet
Date: Mon, 23 Jan 2012 12:54:31 -0500 [thread overview]
Message-ID: <cover.1327341147.git.bruce.ashfield@windriver.com> (raw)
Richard/Saul,
As was discussed on the mailing list ethernet wasn't working out
of the box on the 3.0 kernel (but it was in 3.2, hence why my
boots missed it). I bundled this together with a console fix.
The commit says it all:
[
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.
]
Cheers,
Bruce
The following changes since commit 4ad01bdf3f9cea8b2f42b925fa2b644d96ba1a82:
Richard Purdie (1):
gcc-package-cross.inc: Mark do_package* tasks as noexec
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/qemuppc
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/qemuppc
Bruce Ashfield (1):
linux-yocto/qemuppc: fix console and ethernet
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(-)
next reply other threads:[~2012-01-23 18:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-23 17:54 Bruce Ashfield [this message]
2012-01-23 17:54 ` [PATCH 1/1] linux-yocto/qemuppc: fix console and ethernet Bruce Ashfield
2012-01-24 11:02 ` Richard Purdie
2012-01-24 14:12 ` Bruce Ashfield
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=cover.1327341147.git.bruce.ashfield@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