From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1LwvJj-0006j2-0z
	for qemu-devel@nongnu.org; Thu, 23 Apr 2009 05:34:03 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1LwvJe-0006hA-1o
	for Qemu-devel@nongnu.org; Thu, 23 Apr 2009 05:34:02 -0400
Received: from [199.232.76.173] (port=46155 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1LwvJd-0006gt-NV
	for Qemu-devel@nongnu.org; Thu, 23 Apr 2009 05:33:57 -0400
Received: from lizzard.sbs.de ([194.138.37.39]:16690)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <jan.kiszka@siemens.com>) id 1LwvJd-0000Bn-2o
	for Qemu-devel@nongnu.org; Thu, 23 Apr 2009 05:33:57 -0400
Message-ID: <49F035E7.5080906@siemens.com>
Date: Thu, 23 Apr 2009 11:33:27 +0200
From: Jan Kiszka <jan.kiszka@siemens.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Re: Question about KVM and PC speaker
References: <49EF69BC.90300@gmx.de> <49F01C8D.1010203@web.de>
	<20090423083252.GB5277@const.bordeaux.inria.fr>
	<49F031C2.5000204@siemens.com>
	<20090423092546.GF5277@const.bordeaux.inria.fr>
In-Reply-To: <20090423092546.GF5277@const.bordeaux.inria.fr>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>
Cc: Simon Bienlein <s.bienlein@gmx.de>, Qemu-devel@nongnu.org

Samuel Thibault wrote:
> Jan Kiszka, le Thu 23 Apr 2009 11:15:46 +0200, a =E9crit :
>> that's consistent with QEMU code: there is no handling of port 0x61 in
>> user space,
>=20
> ? I can see it in hw/pcspkr.c
>=20
>> 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?
>=20
> 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

--=20
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux