From: Jan Kiszka <jan.kiszka@siemens.com>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>
Cc: Simon Bienlein <s.bienlein@gmx.de>, Qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: Question about KVM and PC speaker
Date: Thu, 23 Apr 2009 11:33:27 +0200 [thread overview]
Message-ID: <49F035E7.5080906@siemens.com> (raw)
In-Reply-To: <20090423092546.GF5277@const.bordeaux.inria.fr>
Samuel Thibault wrote:
> Jan Kiszka, le Thu 23 Apr 2009 11:15:46 +0200, a écrit :
>> that's consistent with QEMU code: there is no handling of port 0x61 in
>> user space,
>
> ? I can see it in hw/pcspkr.c
>
>> Doing beep via the BIOS is surely another to-do, and a useful hint in
>> this context. But unless you add a paravirt firmware beep channel or
>> BIOS support for sound cards or, and that' probably the best approach,
>> PC speaker emulation, how should the beep be emitted?
>
> I thought the PC speaker emulation was already implemented in
> hw/pcspkr.c..
Huh, it is! Then the problem is a KVM-only thing: The kernel part hooks
onto those resources but doesn't communicate changes to this user space
backend.
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2009-04-23 9:34 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 19:02 [Qemu-devel] Question about KVM and PC speaker Simon Bienlein
2009-04-23 7:45 ` [Qemu-devel] " Jan Kiszka
2009-04-23 8:32 ` Samuel Thibault
2009-04-23 9:06 ` Kevin Wolf
2009-04-23 9:23 ` Samuel Thibault
2009-04-23 9:15 ` Jan Kiszka
2009-04-23 9:25 ` Samuel Thibault
2009-04-23 9:33 ` Jan Kiszka [this message]
2009-04-23 9:50 ` Avi Kivity
2009-04-23 10:29 ` Jan Kiszka
2009-04-23 10:29 ` Jan Kiszka
2009-04-23 11:09 ` Avi Kivity
2009-04-23 11:09 ` Avi Kivity
2009-04-23 17:42 ` Jan Kiszka
2009-04-23 17:42 ` Jan Kiszka
2009-05-04 16:34 ` Simon Bienlein
2009-05-04 16:34 ` Simon Bienlein
2009-05-04 20:29 ` Jan Kiszka
2009-05-04 20:56 ` Samuel Thibault
2009-05-04 20:56 ` [Qemu-devel] " Samuel Thibault
2009-05-04 21:00 ` Jan Kiszka
2009-05-05 15:59 ` Simon Bienlein
2009-05-05 22:34 ` Sebastian Herbszt
2009-05-05 22:34 ` Sebastian Herbszt
2009-05-06 10:34 ` Jan Kiszka
2009-05-06 10:34 ` Jan Kiszka
2009-05-06 20:55 ` Sebastian Herbszt
2009-05-06 20:55 ` Sebastian Herbszt
2009-05-07 8:12 ` Jan Kiszka
2009-05-07 8:12 ` Jan Kiszka
2009-05-09 22:21 ` Sebastian Herbszt
2009-05-09 22:21 ` Sebastian Herbszt
2009-05-12 7:32 ` Jan Kiszka
2009-05-12 7:32 ` Jan Kiszka
2009-05-12 21:06 ` Sebastian Herbszt
2009-05-12 21:06 ` Sebastian Herbszt
2009-05-12 21:50 ` Jan Kiszka
2009-05-12 21:50 ` Jan Kiszka
2009-05-12 22:21 ` Sebastian Herbszt
2009-05-12 22:21 ` Sebastian Herbszt
2009-05-12 22:27 ` Samuel Thibault
2009-05-12 22:37 ` malc
2009-05-12 22:37 ` [Qemu-devel] " malc
2009-05-14 19:48 ` Sebastian Herbszt
2009-05-14 19:48 ` Sebastian Herbszt
2009-05-14 22:01 ` malc
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=49F035E7.5080906@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=Qemu-devel@nongnu.org \
--cc=s.bienlein@gmx.de \
--cc=samuel.thibault@ens-lyon.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.