From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Elvis Dowson <elvis.dowson@gmail.com>
Cc: OpenEmbedded Core Mailing List
<openembedded-core@lists.openembedded.org>
Subject: Re: QEMU with ARM Cortex A9 with hard float configuration - Kernel panic
Date: Sun, 25 Aug 2013 21:03:22 -0400 [thread overview]
Message-ID: <521AA95A.8000803@windriver.com> (raw)
In-Reply-To: <4AC41A5E-073D-4973-82BD-F94A8B168F34@gmail.com>
On 13-08-25 3:09 PM, Elvis Dowson wrote:
> Hi Bruce,
> I noticed that you've committed the changes for qemuarma9 KMACHINE configuration to the linux-yocto kernel.
>
> http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.8/tree/meta/cfg/kernel-cache/bsp?h=meta
>
> I adapted the qemuarm.conf configuration and booted it up, but nothing shows up in the QEMU window, I just get a black screen.
>
> Has qemu with the qemuarma9 configuration been successfully built and tested before?
It has been, but not with a machine definition that is part of oe-core
or Yocto.
It was contributed as the output from some cortexA9 testing, and I've
been carrying the kernel parts ever since.
>
> This is how my qemuarm.conf looks like, locally at the moment:
>
> #@TYPE: Machine
> #@NAME: qemuarmhf
> #@DESCRIPTION: Machine configuration for QEMU ARM Cortex A9 hard float.
>
> # Specify the default tune.
> DEFAULTTUNE = "armv7a-neon"
>
> require conf/machine/include/qemu.inc
> require conf/machine/include/tune-cortexa9.inc
>
> # Specify the machine name used by the kernel.
> KMACHINE_qemuarm = "qemuarma9"
This is a default, so you don't need to set it.
>
> # Specify the kernel image type.
> KERNEL_IMAGETYPE = "zImage"
I recall booting it with a uImage, but maybe my memory is failing.
>
> # Specify the serial console parameters.
> SERIAL_CONSOLE = "115200 ttyAMA0"
All of the above looks reasonably sane, but it's more about how you
launch qemu than the kernel build that is probably resulting in your
issues. What machine subtype did you use ?
Bruce
>
>
> Elvis Dowson
>
next prev parent reply other threads:[~2013-08-26 1:03 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-25 17:43 QEMU with ARM Cortex A9 with hard float configuration - Kernel panic rewitt
2013-08-25 18:02 ` Elvis Dowson
2013-08-25 18:31 ` Elvis Dowson
2013-08-25 19:09 ` Elvis Dowson
2013-08-26 1:03 ` Bruce Ashfield [this message]
2013-08-26 3:58 ` Elvis Dowson
2013-08-26 4:24 ` Bruce Ashfield
2013-08-26 15:49 ` Elvis Dowson
2013-08-26 19:08 ` Bruce Ashfield
2013-08-26 19:35 ` Elvis Dowson
2013-08-27 20:03 ` Bruce Ashfield
2013-08-28 15:16 ` Elvis Dowson
2013-08-28 22:43 ` Bruce Ashfield
2013-08-29 4:36 ` Elvis Dowson
2013-08-29 5:48 ` Khem Raj
2013-08-29 8:50 ` Elvis Dowson
2013-08-29 16:17 ` Khem Raj
2013-08-29 16:18 ` Bruce Ashfield
2013-08-29 16:22 ` Elvis Dowson
2013-08-29 12:35 ` Bruce Ashfield
2013-08-29 14:02 ` Elvis Dowson
2013-08-29 16:23 ` Bruce Ashfield
2013-08-29 16:28 ` Elvis Dowson
2013-08-26 1:11 ` Bruce Ashfield
-- strict thread matches above, loose matches on Subject: below --
2013-08-29 19:32 rewitt
2013-08-29 19:40 ` Bruce Ashfield
2013-08-30 10:17 ` Elvis Dowson
2013-08-29 18:53 rewitt
2013-08-29 18:58 ` Bruce Ashfield
2013-08-29 19:01 ` Elvis Dowson
2013-08-29 19:16 ` Bruce Ashfield
2013-08-29 19:25 ` Elvis Dowson
2013-08-29 19:30 ` Bruce Ashfield
2013-08-25 14:37 Elvis Dowson
2013-08-25 14:44 ` Martin Jansa
2013-08-25 15:09 ` Elvis Dowson
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=521AA95A.8000803@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=elvis.dowson@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox