linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: DervishD <raul@pleyades.net>
To: Andrey Borzenkov <arvidjaar@mail.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: /dev/input/mice doesn't work in test9?
Date: Sun, 2 Nov 2003 21:37:01 +0100	[thread overview]
Message-ID: <20031102203700.GA54@DervishD> (raw)
In-Reply-To: <200311022045.41928.arvidjaar@mail.ru>

    Hi Andrey :)

 * Andrey Borzenkov <arvidjaar@mail.ru> dixit:
> >     But not char-major-13-32, for example.
> for kernel device == major. It is assumed that complete major is
> handled by single driver.

    OK, now all makes sense :)

> But again, mousedev is using range of minors and 
> there is currently no established way to construct aliases for that. Short of 
> defining
> 
> alias char-major-13-32 mousedev
> alias char-major-13-33 mousedev
> ...
> alias char-major-13-63 mousedev
> 
> looks rather weird.

    But, is it possible? Just guessing...
 
> >     Yes, I'm going to build in hid, but, should I do the same with
> > mousedev (or event, joystick, etc...) or will it work with hid loaded
> > when doing 'cat /dev/mouse'?
> yes you should build it in. Or ensure it is loaded together with hid. 

    It's easier if I just build it in. No need to mess with
modules.conf for this one. The memory gain for having hid and
mousedev as modules is minimal.

    Thanks for all the explanations :)

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736
http://www.pleyades.net & http://raul.pleyades.net/

  reply	other threads:[~2003-11-02 20:37 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
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 [this message]
  -- 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=20031102203700.GA54@DervishD \
    --to=raul@pleyades.net \
    --cc=arvidjaar@mail.ru \
    --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;
as well as URLs for NNTP newsgroup(s).