From: Philipp Rumpf <prumpf@suse.de>
To: Alex deVries <adevries@thepuffingroup.com>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] keyboards and such.
Date: Tue, 26 Oct 1999 08:56:54 +0200 [thread overview]
Message-ID: <19991026085653.A17980@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.10.9910242258310.22118-100000@vodka.thepuffingroup.com>; from Alex deVries on Sun, Oct 24, 1999 at 11:01:57PM -0400
> Does anyone have docs on how to speak to a standard AT or PS/2 keyboard?
> The Black Puffin of Death will haunt you if you point me to 8042
> controller docs.
what about looking at the current keyboard driver ? It looks to me like it
shouldn't be too difficult to work from the assumption that kbd_read_input is
RCVDATA, kbd_read_status is STATUS, KBD_STAT_OBF is RBNE, KBD_STAT_IBF is TBNE,
KBD_STAT_MOUSE_OBF we don't need, KBD_STAT_GTO is TERR and KBD_STAT_PERR is
PERR.
looking at it again, the bit correlations are:
8042 Lasi
0-1 0-1
6-7 2-3
2-5 unimplemented
unimplemented 4-7
assuming there is a 8042-compatible chip inside lasi, it just seems to get the
line for bit 2 as both input line 2 and 3 (and there's some additional logic
around it).
Philipp Rumpf
prev parent reply other threads:[~1999-10-26 6:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-25 3:01 [parisc-linux] keyboards and such Alex deVries
1999-10-26 6:56 ` Philipp Rumpf [this message]
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=19991026085653.A17980@suse.de \
--to=prumpf@suse.de \
--cc=adevries@thepuffingroup.com \
--cc=parisc-linux@thepuffingroup.com \
/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