public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrey Borzenkov <arvidjaar@mail.ru>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: module-init-tools - input devices id support
Date: Sat, 2 Aug 2003 20:26:08 +0400	[thread overview]
Message-ID: <200308022026.08906.arvidjaar@mail.ru> (raw)
In-Reply-To: <20030801234824.A199E2C129@lists.samba.org>

On Saturday 02 August 2003 03:13, Rusty Russell wrote:
> In message <200308020129.51737.arvidjaar@mail.ru> you write:
> > this adds support for generating modules.inputmap with input handler
> > match table that is used by input hotplug agent posted separately. Using
> > hotplug allowed me to completely eliminate any manual (input handler)
> > module loading in 2.6, it is also compatible with 2.4 in that usb.agent
> > for 2.4 includes fake usb table that maps device class to input handlers
> > so this is mostly transparent to users.
>
> Hi Andrey,
>
> 	For 2.6 you should not be using the maps generated by depmod.
> You should be adding to scripts/file2alias.c, and using those aliases
> to insert modules.  This is much more flexible.
>

well ... file2alias assumes scalar fields with "is equal" or "do not care" 
values. Input handler matching requires bit (sub-)fields matching (with 
longest filed being 512 bits). I od not see how it can be implemented using 
standard alias syntax. This syntax fails even for some PCI entries already 
(while using pcimap allows for more elaborate matching)

Can you name some current users of module.alias?

thank you

-andrey

  reply	other threads:[~2003-08-02 16:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-01 21:29 module-init-tools - input devices id support Andrey Borzenkov
2003-08-01 23:13 ` Rusty Russell
2003-08-02 16:26   ` Andrey Borzenkov [this message]
2003-08-08 17:20     ` Rusty Russell
2003-08-08 21:07       ` Andrey Borzenkov
2003-08-15 12:08         ` Rusty Russell

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=200308022026.08906.arvidjaar@mail.ru \
    --to=arvidjaar@mail.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    /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