From: Vojtech Pavlik <vojtech@suse.cz>
To: Osamu Tomita <tomita@cinet.co.jp>
Cc: "'Vojtech Pavlik '" <vojtech@suse.cz>,
"'LKML '" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][RFC] add support for PC-9800 architecture (11/26) inp ut
Date: Wed, 23 Oct 2002 11:17:46 +0200 [thread overview]
Message-ID: <20021023111746.D28139@ucw.cz> (raw)
In-Reply-To: <E6D19EE98F00AB4DB465A44FCF3FA46903A309@ns.cinet.co.jp>; from tomita@cinet.co.jp on Wed, Oct 23, 2002 at 10:42:19AM +0900
On Wed, Oct 23, 2002 at 10:42:19AM +0900, Osamu Tomita wrote:
> Thanks for many suggestion.
>
> -----Original Message-----
> From: Vojtech Pavlik
> To: Osamu Tomita
> Cc: LKML; Linus Torvalds
> Sent: 2002/10/22 19:29
> Subject: Re: [PATCH][RFC] add support for PC-9800 architecture (11/26) input
>
> > Before I'll think of merging this, it has to be seriously cleaned up.
> > Comments below.
> I see. I work away at cleanup.
>
> > (Summary: use your own SERIO_TYPE for the PC-98 keyboard, remove dead
> > code and definitions, fix naming, make as little #ifdefs as possible,
> > and maybe you can put the PC-98 keyboard code into xtkbd.c (in which
> > case you may get away with SERIO_XT).
> Since xtkbd has not write keyboard function, I modified atkbd.
> I'll rewrite driver, keycode translations and (un)initialize using xtkbd's
> way. Also rename identifier.
> I don't touch input.h in next patch.
Great, thanks!
Yes, it's true that the xtkbd.c code has no way to set the LEDs on the
keyboard nor any functions that'd support sending bytes to the keyboard.
Anyway, the PC-9800 seems to have diverged from IBM machines at about
the time of the XT, and thus the keyboard controller in it (i8251) and
the keyboard itself speak much like they'd do on an IBM XT, with some
extensions like adding commands to set the LEDs, of course.
--
Vojtech Pavlik
SuSE Labs
prev parent reply other threads:[~2002-10-23 9:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-23 1:42 Osamu Tomita
2002-10-23 9:17 ` Vojtech Pavlik [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=20021023111746.D28139@ucw.cz \
--to=vojtech@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=tomita@cinet.co.jp \
/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
all inboxes | Powered by JetHome®