From: forsyth@plan9.cs.york.ac.uk forsyth@plan9.cs.york.ac.uk
Subject: locked keyboard
Date: Tue, 21 Nov 1995 08:46:31 -0500 [thread overview]
Message-ID: <19951121134631.Lc_iajLke0-2ZvxfEcTfQ7VN8Kr1VD00COXD77Nyl5U@z> (raw)
i ran into this problem on a 386sx16 (a fairly old motherboard).
i've not seen it on any 486 here.
for the moment, i have changed kbd.c
as follows.
i changed the following assignment in kbdinit in the new kbd.c
ccc |= Csf | Ckbdint | Cscs1 | Cmousedis;
to read
ccc |= Csf | Ckbdint | Cscs1;
if(x86() != 3)
ccc |= Cmousedis;
this is sufficient to fix the problem here.
it's not ideal (because i don't yet know why this causes it to hang,
and i also don't know whether it really is
confined to [some] 386 motherboards or whether it
affects a particular keyboard chipset that
is also used on a 486.
next reply other threads:[~1995-11-21 13:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-11-21 13:46 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-11-21 14:09 forsyth
1995-11-21 8:08 Dave
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=19951121134631.Lc_iajLke0-2ZvxfEcTfQ7VN8Kr1VD00COXD77Nyl5U@z \
--to=forsyth@plan9.cs.york.ac.uk \
/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).