From: DervishD <raul@pleyades.net>
To: Andrey Borzenkov <arvidjaar@mail.ru>
Cc: Shawn Willden <shawn-lkml@willden.org>, linux-kernel@vger.kernel.org
Subject: Re: /dev/input/mice doesn't work in test9?
Date: Sat, 1 Nov 2003 21:56:46 +0100 [thread overview]
Message-ID: <20031101205646.GB9129@DervishD> (raw)
In-Reply-To: <E1AFUFz-0008jt-00.arvidjaar-mail-ru@f20.mail.ru>
Hi Andrey and Shawn :)
* "Andrey Borzenkov" <arvidjaar@mail.ru> dixit:
> > I'm sure I'm just missing something stupid, but google doesn't
> > seem to turn up anything, so...
Exactly the same for me...
> > I'm trying to use 2.6.0-test9 on a machine with a USB mouse. With 2.4, I
> > have X configured to use /dev/input/mice (c 13 63) as my mouse pointer,
> > and it works great. With test9, XFree86 fails to start because it can't
> > open the mouse. The error is "xf86OpenSerial: Cannot open device /dev/
> > input/mice No such device.".
My problem is a bit different. I'm using 2.4.21, with an USB
mouse. I have 'input' built-in, and hid and mousedev as modules.
Well, if I do a cat /dev/mouse (c 13 32) or /dev/mice (c 13 63), I
always get ENODEV, unless I manually load hid and mousedev. The logs
doesn't say anything like 'cannot find driver for char-major-13' or
whatever. It just seems that 'mousedev' is never autoloaded :?
> The whole input subsystem has changed between 2.4 and 2.6.
> Unfortunately, input sysbsystem hotplugging is not currently
> implemented. Your best bet is to forcibly load mousedev during
> boot.
But hotplugging is for connecting and disconnecting devices, not
for autoloading modules. I mean, if I access any char-major-13, and
the corresponding modules is not loaded, it should autoload :?
The rest of devices in my system are properly autoloaded on
demand, but hid and mousedev are not :( Am I doing something wrong?
> Alternatively look into hotplug for usermap, it allows provide fake
> mapping for modules - you could add mapping from UDB IDs of oyur
> mouse to mousedev. Loading it statically is likely to be more
> simple.
Exactly... Anyway, if I build 'mousedev' into my kernel instead
of making it a module, should I do the same with 'hid' or
char-major-13 *is* autoloaded?
Thanks a lot in advance. I'm missing on this subject...
Raúl Núñez de Arenas Coronado
--
Linux Registered User 88736
http://www.pleyades.net & http://raul.pleyades.net/
next prev parent reply other threads:[~2003-11-01 20:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-31 8:03 /dev/input/mice doesn't work in test9? "Andrey Borzenkov"
2003-10-31 14:27 ` Shawn Willden
2003-11-01 20:56 ` DervishD [this message]
2003-11-02 10:12 ` Andrey Borzenkov
2003-11-02 12:08 ` DervishD
2003-11-02 17:45 ` Andrey Borzenkov
2003-11-02 20:37 ` DervishD
-- strict thread matches above, loose matches on Subject: below --
2003-10-30 18:32 Shawn Willden
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=20031101205646.GB9129@DervishD \
--to=raul@pleyades.net \
--cc=arvidjaar@mail.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=shawn-lkml@willden.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