From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1LwvBt-0004Hh-L1
	for qemu-devel@nongnu.org; Thu, 23 Apr 2009 05:25:57 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1LwvBo-0004EM-M8
	for Qemu-devel@nongnu.org; Thu, 23 Apr 2009 05:25:56 -0400
Received: from [199.232.76.173] (port=58462 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1LwvBo-0004E8-FT
	for Qemu-devel@nongnu.org; Thu, 23 Apr 2009 05:25:52 -0400
Received: from mail3-relais-sop.national.inria.fr ([192.134.164.104]:14931)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_ARCFOUR_SHA1:16)
	(Exim 4.60) (envelope-from <samuel.thibault@labri.fr>)
	id 1LwvBn-0007Sr-Sa
	for Qemu-devel@nongnu.org; Thu, 23 Apr 2009 05:25:52 -0400
Date: Thu, 23 Apr 2009 11:25:46 +0200
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
Subject: Re: [Qemu-devel] Re: Question about KVM and PC speaker
Message-ID: <20090423092546.GF5277@const.bordeaux.inria.fr>
References: <49EF69BC.90300@gmx.de> <49F01C8D.1010203@web.de>
	<20090423083252.GB5277@const.bordeaux.inria.fr>
	<49F031C2.5000204@siemens.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <49F031C2.5000204@siemens.com>
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: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Simon Bienlein <s.bienlein@gmx.de>, Qemu-devel@nongnu.org

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..

Samuel