From: Vojtech Pavlik <vojtech@suse.cz>
To: James Simmons <jsimmons@transvirtual.com>
Cc: Etienne Lorrain <etienne_lorrain@yahoo.fr>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: New Input PS/2 driver
Date: Sat, 6 Oct 2001 00:50:06 +0200 [thread overview]
Message-ID: <20011006005006.A17152@suse.cz> (raw)
In-Reply-To: <20011003133440.28925.qmail@web11804.mail.yahoo.com> <Pine.LNX.4.10.10110031217300.32026-100000@transvirtual.com>
In-Reply-To: <Pine.LNX.4.10.10110031217300.32026-100000@transvirtual.com>; from jsimmons@transvirtual.com on Wed, Oct 03, 2001 at 12:28:34PM -0700
On Wed, Oct 03, 2001 at 12:28:34PM -0700, James Simmons wrote:
>
> > Would be nice to change the comment describing the Keyboard core
> > support (CONFIG_INPUT_KEYBDEV) in this patch: people (as dumb me)
> > may read the help in menuconfig and say:
> > I have no USB HID or ADB keyboard...
> > Recompile, reboot => no keyboard, no control-alt-del => Reset (fsck...).
>
> Yeah. That does need to be added.
>
> > Else it is working here on a P133 with nothing special (std PS2 mouse).
>
> >From the several reports I have had with the driver it looks pretty
> stable. Alan what do you think about adding it to the ac tree?
>
> > BTW you just undefine I8042_OVERRIDE_KEYLOCK but this define is
> > never used.
>
> Not implemented yet.
Quite the opposite: #undef was forgotten in the .h file after the .c
file converted to a runtime option instead of a compiletime one. I
removed it in the CVS now.
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2001-10-05 22:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-03 13:34 New Input PS/2 driver Etienne Lorrain
2001-10-03 19:28 ` James Simmons
2001-10-05 22:50 ` Vojtech Pavlik [this message]
2001-10-05 23:02 ` James Simmons
2001-10-05 23:07 ` Vojtech Pavlik
-- strict thread matches above, loose matches on Subject: below --
2001-10-02 4:47 James Simmons
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=20011006005006.A17152@suse.cz \
--to=vojtech@suse.cz \
--cc=etienne_lorrain@yahoo.fr \
--cc=jsimmons@transvirtual.com \
--cc=linux-kernel@vger.kernel.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