linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: md@Linux.IT (Marco d'Itri)
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] The Mandriva Collection
Date: Tue, 13 Dec 2005 00:49:31 +0000	[thread overview]
Message-ID: <20051213004931.GA14814@wonderland.linux.it> (raw)
In-Reply-To: <m3k6eaqki0.fsf@dynamo.mandriva.com>

On Dec 12, Olivier Blin <oblin@mandriva.com> wrote:

> And it needs a VID/PID rules list, which may not be easy to write
> without duplication. What's the proper construction to replace this
> kind of usermaps?
In one of my packages (which maybe should just have used fxload for
stage1...) I use:

BUS!="usb", ACTION!="add", GOTO="eciadsl_usb_add_end"

# Aethra Starmodem
SYSFS{idVendor}="0659", SYSFS{idProduct}="0915", \
        RUN+="/lib/hotplug/eciadsl stage1"
SYSFS{idVendor}="0915", SYSFS{idProduct}="0916", \
        RUN+="/lib/hotplug/eciadsl stage2 4 GS7070"

...

LABEL="eciadsl_usb_add_end"

Obviously I did not manually write rules for each of the 26 modems
supported, a trivial perl program does it.
Similar programs have been implemented by the libgphoto2 and libsane
maintainers.


> It can probably be simplified using PRODUCT values:
Ugly, and probably slower.

-- 
ciao,
Marco


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id\x16865&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2005-12-13  0:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-12 17:43 [PATCH] The Mandriva Collection Olivier Blin
2005-12-12 18:21 ` Marco d'Itri
2005-12-12 18:25 ` Scott James Remnant
2005-12-12 18:37 ` Olivier Blin
2005-12-12 18:47 ` Marco d'Itri
2005-12-12 19:13 ` Olivier Blin
2005-12-12 19:17 ` Marco d'Itri
2005-12-12 19:44 ` Olivier Blin
2005-12-12 21:45 ` Olivier Blin
2005-12-13  0:49 ` Marco d'Itri [this message]
2005-12-13  5:08 ` Kay Sievers
2005-12-21 17:46 ` Olivier Blin
2005-12-21 17:47 ` Marco d'Itri
2005-12-21 17:51 ` Olivier Blin
2005-12-21 18:04 ` Marco d'Itri
2006-01-03 19:55 ` Olivier Blin
2006-01-04  1:20 ` Kay Sievers

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=20051213004931.GA14814@wonderland.linux.it \
    --to=md@linux.it \
    --cc=linux-hotplug@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).