From: Alexander Graf <agraf@suse.de>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: isa-applesmc doesn't handle second instantiation gracefully
Date: Tue, 12 Oct 2010 14:57:24 +0200 [thread overview]
Message-ID: <CD75678C-1723-407B-96CF-93504C67721E@suse.de> (raw)
In-Reply-To: <m3ocazlglv.fsf@blackfin.pond.sub.org>
On 12.10.2010, at 14:50, Markus Armbruster wrote:
> When I try -device isa-applesmc -device isa-applesmc, I get
>
> WARNING: Using AppleSMC with invalid key
> qemu: hardware error: register_ioport_read: invalid opaque
> [...]
>
> and a core dump.
>
> I know nothing about this device. Instantiating twice may well make no
> sense. But hw_error() is not a nice way to reject a command line
> option.
I'd guess it fails because it defaults to the same port twice, so allocating it twice would put two ISA devices on the same PIO port which doesn't work.
I don't think there's any way around this, or is there?
Alex
next prev parent reply other threads:[~2010-10-12 12:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-12 12:50 [Qemu-devel] isa-applesmc doesn't handle second instantiation gracefully Markus Armbruster
2010-10-12 12:57 ` Alexander Graf [this message]
2010-10-12 13:00 ` [Qemu-devel] qdev: Some ISA devices don't handle second instantiation gracefully (was: isa-applesmc doesn't handle second instantiation gracefully) Markus Armbruster
2010-10-12 13:04 ` [Qemu-devel] " Alexander Graf
2010-10-12 14:52 ` [Qemu-devel] Re: qdev: Some ISA devices don't handle second instantiation gracefully Gerd Hoffmann
2010-10-12 13:27 ` [Qemu-devel] " Anthony Liguori
2010-10-12 13:54 ` Markus Armbruster
2010-10-12 14:24 ` Anthony Liguori
2010-10-13 12:47 ` [Qemu-devel] Re: qdev: Some ISA devices don't handle second instantiation gracefully (was: isa-applesmc doesn't handle second instantiation gracefully) Richard W.M. Jones
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=CD75678C-1723-407B-96CF-93504C67721E@suse.de \
--to=agraf@suse.de \
--cc=armbru@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).