From: Matthias Schniedermeyer <ms@citd.de>
To: Ivan Gyurdiev <ivg2@cornell.edu>
Cc: Ruth Ivimey-Cook <Ruth.Ivimey-Cook@ivimey.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: USB Keyboard in 2.5 bitkeeper...
Date: Sat, 12 Apr 2003 09:58:59 +0200 [thread overview]
Message-ID: <20030412075859.GA19294@citd.de> (raw)
In-Reply-To: <200304112339.19484.ivg2@cornell.edu>
On Fri, Apr 11, 2003 at 11:39:19PM -0400, Ivan Gyurdiev wrote:
> On Friday 11 April 2003 21:49, Ruth Ivimey-Cook wrote:
> > On Sat, 2003-04-12 at 00:41, 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)
> >
> > I have a USB keyboard (a BTC model 9000) that has a PS/2 mouse port on
> > the back. When USB enumerates it I get a keyboard controller and a mouse
> > controller connection... I guess that's the sort of thing you have.
> >
> > Ruth
>
> my keyboard has no mouse port on the back.
Exists a version of the keyboard with a mouse-port, or a version with a
"mouse"-thing. (Track-Point, Track-Ball, Glide-Point, or whatever you
call it today.)
Then there is a chance that they only use a single version of the
chipset, which includes a mouse-port.
Bis denn
--
Real Programmers consider "what you see is what you get" to be just as
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated,
cryptic, powerful, unforgiving, dangerous.
prev parent reply other threads:[~2003-04-12 7:47 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
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 [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=20030412075859.GA19294@citd.de \
--to=ms@citd.de \
--cc=Ruth.Ivimey-Cook@ivimey.org \
--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