From: "Sebastian Herbszt" <herbszt@gmx.de>
To: Jan Kiszka <jan.kiszka@siemens.com>, Volker Ruppert <info@vruppert.de>
Cc: Qemu-devel@nongnu.org, kvm@vger.kernel.org,
Simon Bienlein <simon@linux-fuer-blinde.de>
Subject: Re: [Qemu-devel] Re: Question about KVM and PC speaker
Date: Sun, 10 May 2009 00:21:27 +0200 [thread overview]
Message-ID: <B0393A87D91D41BCBB63799F330601DC@FSCPC> (raw)
In-Reply-To: <4A0297D2.4040009@siemens.com>
Jan Kiszka wrote:
> Sebastian Herbszt wrote:
>> Jan Kiszka wrote:
>>> Sebastian Herbszt wrote:
>>>> Simon Bienlein wrote:
>>>>> Is a support for BIOS worked on right now?
>>>>
>>>> The vgabios (vgabios.c) has a "FIXME should beep". Volker, do you plan
>>>> to fix this?
>>>>
>>>> Which frequency should be used for the beep? Which delay?
>>>
>>> I would try 1 KHz and some hundred milliseconds.
>>
>> I just looked at some vga bios and it uses about 896,45 Hz.
>>
>>>> Getting a delay using "inb(0x61) & 0x10" is still a no go on qemu,
>>>> right?
>>>
>>> Looks like (should be far too inaccurate for longer delays). What about
>>> 0x40:0x6c, the BIOS' daily timer counter?
>>
>> The bios i looked at used the refresh request port 0x61. This is
>> supported by bochs and
>> there is also a patch for qemu to replace the dummy [1]. The rombios
>> uses this to provide
>> INT 15h AH=86h functionality; this is likely broken with the dummy code
>> in qemu.
>
> I see no problem with improving qemu's emulation accuracy this way a
> bit. But I wouldn't built new delay implementations on top of it,
> specifically if the code is in fact aware of running over a hypervisor.
> Such micro-timings are far too inaccurate for longer delays in an
> environment where you cannot be sure of running all the time during that
> period.
Volker, mind to resubmit the patch once again?
>> Anyway, using "timer ticks since midnight" should be possible (INT 08h
>> handler is set up
>> before vga bios is called).
I have implemented the beep for vgabios-6b and it works on bochs but fails on qemu.
With "-soundhw pcspk" i should hear it thru the hosts pc speaker, right?
- Sebastian
next prev parent reply other threads:[~2009-05-09 22:23 UTC|newest]
Thread overview: 30+ 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
2009-04-23 9:50 ` Avi Kivity
2009-04-23 10:29 ` Jan Kiszka
2009-04-23 11:09 ` Avi Kivity
2009-04-23 17:42 ` Jan Kiszka
2009-05-04 16:34 ` Simon Bienlein
2009-05-04 20:29 ` Jan Kiszka
2009-05-04 20:56 ` 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-06 10:34 ` Jan Kiszka
2009-05-06 20:55 ` Sebastian Herbszt
2009-05-07 8:12 ` Jan Kiszka
2009-05-09 22:21 ` Sebastian Herbszt [this message]
2009-05-12 7:32 ` Jan Kiszka
2009-05-12 21:06 ` Sebastian Herbszt
2009-05-12 21:50 ` Jan Kiszka
2009-05-12 22:21 ` Sebastian Herbszt
2009-05-12 22:27 ` Samuel Thibault
2009-05-12 22:37 ` malc
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=B0393A87D91D41BCBB63799F330601DC@FSCPC \
--to=herbszt@gmx.de \
--cc=Qemu-devel@nongnu.org \
--cc=info@vruppert.de \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=simon@linux-fuer-blinde.de \
/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).