From: Greg KH <greg@kroah.com>
To: Ivan Gyurdiev <ivg2@cornell.edu>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: USB Keyboard in 2.5 bitkeeper...
Date: Fri, 11 Apr 2003 17:03:57 -0700 [thread overview]
Message-ID: <20030412000357.GJ4539@kroah.com> (raw)
In-Reply-To: <200304111941.16563.ivg2@cornell.edu>
On Fri, Apr 11, 2003 at 07:41:08PM -0400, Ivan Gyurdiev wrote:
> input1: USB HID v1.00 Keyboard [NOVATEK Keyboard NT6881] on usb1:3.0
> input2: USB HID v1.00 Mouse [NOVATEK Keyboard NT6881] on usb1:3.1
>
> That's only a keyboard, but interestingly it shows up as a keyboard AND mouse.
> (This kernel is 2.4.21-pre5-ac3)
Well, it thinks it is both :)
> Anyway: In 2.5 bitkeeper (4/11/03), my keyboard is completely dead - even
> sysrq doesn't work. I've had similar problems with recent 2.4 bitkeeper
> kernels (but I can't be very specific - I can re-test if you'd like me to)
Does 2.5.67 work for you?
thanks,
greg k-h
next prev parent reply other threads:[~2003-04-11 23:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-11 23:41 USB Keyboard in 2.5 bitkeeper Ivan Gyurdiev
2003-04-12 0:03 ` Greg KH [this message]
2003-04-13 0:57 ` Ivan Gyurdiev
2003-04-12 1:49 ` Ruth Ivimey-Cook
2003-04-12 3:39 ` Ivan Gyurdiev
2003-04-12 7:58 ` Matthias Schniedermeyer
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=20030412000357.GJ4539@kroah.com \
--to=greg@kroah.com \
--cc=ivg2@cornell.edu \
--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