From: Brad Hards <bhards@bigpond.net.au>
To: Thunder from the hill <thunder@ngforever.de>,
Michael De Nil <linux@aerythmic.be>
Cc: Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: /dev/input/mice problem with 2.4.19-pre9 & 10
Date: Sun, 9 Jun 2002 09:51:49 +1000 [thread overview]
Message-ID: <200206090951.49761.bhards@bigpond.net.au> (raw)
In-Reply-To: <Pine.LNX.4.44.0206080522040.15675-100000@hawkeye.luckynet.adm>
On Sat, 8 Jun 2002 21:23, Thunder from the hill wrote:
> Hi,
>
> On Sat, 8 Jun 2002, Michael De Nil wrote:
> > When I move my mouse while catting /dev/input/mice, nothing appears ...
> >
> > Other USB-device work...
>
> Please try /dev/input/mouse0.
>
> [thunder@hawkeye.luckynet.adm /usr/src/thunder-2.5.20] (0) ls -l
> /dev/input/ total 0
> crw-r--r-- 1 root root 13, 63 Dec 31 1969 mice
> crw-r--r-- 1 root root 13, 32 Dec 31 1969 mouse0
That won't make any difference - it will say "no such device".
Both devices are created by the same input subsystem mouse driver. That driver
is loaded (because /dev/input/mice was able to be opened), but there is no
underlying USB support for the input subsystem. Input subsystem support was
made configurable in -pre9, and if you don't select that option, then the hid
parser directs the output to /dev/usb/hiddevX.
Brad
--
http://conf.linux.org.au. 22-25Jan2003. Perth, Australia. Birds in Black.
prev parent reply other threads:[~2002-06-08 23:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-08 9:41 Michael De Nil
2002-06-08 10:11 ` Brad Hards
2002-06-08 11:23 ` Thunder from the hill
2002-06-08 23:51 ` Brad Hards [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=200206090951.49761.bhards@bigpond.net.au \
--to=bhards@bigpond.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@aerythmic.be \
--cc=thunder@ngforever.de \
/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®