From: Paolo Bonzini <pbonzini@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Gerd Hoffmann <kraxel@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 3/4] wakeup: make serial configurable
Date: Sat, 08 Sep 2012 12:34:28 +0200 [thread overview]
Message-ID: <504B1F34.7000101@redhat.com> (raw)
In-Reply-To: <CAAu8pHtZwd9UhMWGqHJRkeP=OhOwWbL4EhBpdxVzMG0L0LreZg@mail.gmail.com>
Il 08/09/2012 09:15, Blue Swirl ha scritto:
>> Preferably some which don't
>> > break on 'qemu -nodefault -device isa-serial,chardev=foo'.
> Add a qdev property? The base address check can't be correct, the
> serial device could be the only one in the board and wired to wakeup
> but still use a different iobase.
Could work, but the default value for the property would still be
"depending on the iobase".
> One way could be to check if chr == serial_hds[0] or rather, pass the
> wakeup reason code from board level based on this check.
That doesn't work for -device.
Paolo
next prev parent reply other threads:[~2012-09-08 10:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 7:42 [Qemu-devel] [PULL 0/4] wakeup: make wakeup events guest-configurable Gerd Hoffmann
2012-09-06 7:42 ` [Qemu-devel] [PATCH 1/4] wakeup: add acpi gpe wakeup reasons Gerd Hoffmann
2012-09-06 7:42 ` [Qemu-devel] [PATCH 2/4] wakeup: make ps/2 configurable Gerd Hoffmann
2012-09-06 7:42 ` [Qemu-devel] [PATCH 3/4] wakeup: make serial configurable Gerd Hoffmann
2012-09-06 7:48 ` Peter Maydell
2012-09-06 10:47 ` Gerd Hoffmann
2012-09-08 7:15 ` Blue Swirl
2012-09-08 10:34 ` Paolo Bonzini [this message]
2012-09-10 16:02 ` Anthony Liguori
2012-09-10 16:07 ` Paolo Bonzini
2012-09-10 16:16 ` Peter Maydell
2012-09-10 17:19 ` Anthony Liguori
2012-09-10 5:47 ` Gerd Hoffmann
2012-09-06 7:42 ` [Qemu-devel] [PATCH 4/4] wakeup: uhci support Gerd Hoffmann
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=504B1F34.7000101@redhat.com \
--to=pbonzini@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=kraxel@redhat.com \
--cc=peter.maydell@linaro.org \
--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).