From: Martin Mohring <martin.mohring@5etech.eu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] ARMv6 el + vfp: User Mode signals uncaught target signal 4 (Illegal instruction)
Date: Fri, 05 Dec 2008 13:35:13 +0100 [thread overview]
Message-ID: <49392001.6000806@5etech.eu> (raw)
In-Reply-To: <761ea48b0812050355x6adaea49nd9434a41bcd8f765@mail.gmail.com>
Laurent Desnogues wrote:
> On Fri, Dec 5, 2008 at 11:17 AM, Martin Mohring
> <martin.mohring@opensuse.org> wrote:
>
>> I put together a qemu from recent svn trunk -r 5862.
>>
>> when running armv6 eabi + vfp binaries in user mode emulation, i get:
>>
>> qemu: uncaught target signal 4 (Illegal instruction) - exiting
>>
>> running the same compiled for armv5 eabi + vfp works. I use the binaries
>> from mojo (mojo.handhelds.org) project, they ported Ubuntu 8.04 to arm.
>> They also have a compiled version for ARMv6 + VFP, which I wanted to try
>> in the openSUSE Buildservice.
>>
>
> You should specify the CPU when launching qemu. Look at "qemu -cpu ?"
> output and select the right one. You probably want -cpu arm1136.
>
I use qemu user mode, and call qemu with host linux kernels binfmt
handler. How do I specify the cpu type there? Or must I compile in the
"default cpu type" somehow?
>
>> How do I find out whats wrong? From the source code, I would guess qemu
>> is implemented up to ARMv7, right?
>>
>
> Yes ARMv7 is in, including NEON.
>
>
I thought that, from looking into the code. I was sure I missed something...
Martin
next prev parent reply other threads:[~2008-12-05 12:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 10:17 [Qemu-devel] ARMv6 el + vfp: User Mode signals uncaught target signal 4 (Illegal instruction) Martin Mohring
2008-12-05 11:55 ` Laurent Desnogues
2008-12-05 12:34 ` Riku Voipio
2008-12-05 12:35 ` Martin Mohring [this message]
2008-12-05 12:35 ` Martin Mohring
2008-12-05 12:57 ` Laurent Desnogues
2008-12-05 13:28 ` Martin Mohring
2008-12-05 21:00 ` Martin Mohring
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=49392001.6000806@5etech.eu \
--to=martin.mohring@5etech.eu \
--cc=qemu-devel@nongnu.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.