From: Kevin O'Connor <kevin@koconnor.net>
To: Roy Tam <roytam@gmail.com>
Cc: seabios@seabios.org, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Regression: more 0.12 regression (SeaBIOS related?)
Date: Wed, 10 Mar 2010 22:07:42 -0500 [thread overview]
Message-ID: <20100311030742.GA26752@morn.localdomain> (raw)
In-Reply-To: <473191351003092124o382bddc8m80df4676c048ec0a@mail.gmail.com>
On Wed, Mar 10, 2010 at 01:24:27PM +0800, Roy Tam wrote:
> 2010/3/10 Kevin O'Connor <kevin@koconnor.net>:
> > I don't see an "Illegal Instruction" message. Instead, I see the
> > keyboard just not working. What qemu version and what command line
> > did you use?
>
> latest git today. when you type fast.
Bleh. That image defines an int15 wrapper which corrupts %edi.
SeaBIOS calls int154f from the keyboard irq, and it is not prepared to
handle a corrupted edi. In contrast, Bochs BIOS doesn't care if the
registers change.
> > What the fdos0138.img image is doing is broken - once it reads the key
> > from the ps2 port, nothing stops a new key from being read the next
> > time something reads from the port. Indeed, although the keyboard
> > works in qemu-0.11 for fdos0138.img, if one types fast they'll see
> > duplicate and lost keys.
> >
>
> But it is how programs(Chinese/Japanese/Korean Display Systems,
> GW-BASIC, etc.) in the past get input from keyboard.
Can you point me to documentation on this usage?
> "Consider" legacy as "broken" is wrong IMHO.
It's broken because it causes key presses to be lost and corrupted.
The ps2 port hardware just doesn't work the way that software is
trying to use it.
-Kevin
next prev parent reply other threads:[~2010-03-11 3:14 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 2:04 [Qemu-devel] Regression: more 0.12 regression (SeaBIOS related?) Roy Tam
2010-03-08 10:05 ` Jamie Lokier
2010-03-08 11:08 ` Roy Tam
2010-03-08 13:48 ` Roy Tam
2010-03-10 4:48 ` Roy Tam
2010-03-09 15:41 ` Natalia Portillo
2010-03-09 16:09 ` Natalia Portillo
2010-03-10 2:12 ` Kevin O'Connor
2010-03-10 3:49 ` Roy Tam
2010-03-10 4:59 ` Kevin O'Connor
2010-03-10 5:05 ` Roy Tam
2010-03-10 5:55 ` Kevin O'Connor
2010-03-10 5:24 ` Roy Tam
2010-03-11 3:07 ` Kevin O'Connor [this message]
2010-03-11 7:42 ` Roy Tam
2010-03-11 8:10 ` Natalia Portillo
2010-03-12 0:57 ` Kevin O'Connor
2010-03-12 1:17 ` Roy Tam
2010-03-12 16:13 ` Roy Tam
2010-03-13 15:35 ` Kevin O'Connor
2010-03-13 16:00 ` Roy Tam
2010-03-12 23:24 ` [Qemu-devel] PC keyboard emulation (was: Regression: more 0.12 regression (SeaBIOS related?)) Jamie Lokier
2010-03-14 0:44 ` [Qemu-devel] " Kevin O'Connor
2010-03-15 2:47 ` Jamie Lokier
2010-03-15 3:08 ` Kevin O'Connor
[not found] <998502.27470.qm@web15103.mail.cnb.yahoo.com>
[not found] ` <473191351003071956g48c3944fyd3adc3ae6012493c@mail.gmail.com>
2010-03-08 3:57 ` [Qemu-devel] Regression: more 0.12 regression (SeaBIOS related?) Roy Tam
-- strict thread matches above, loose matches on Subject: below --
2012-03-06 17:00 Alain Ribière
2012-03-07 13:38 ` Kevin O'Connor
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=20100311030742.GA26752@morn.localdomain \
--to=kevin@koconnor.net \
--cc=qemu-devel@nongnu.org \
--cc=roytam@gmail.com \
--cc=seabios@seabios.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).