From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Hotplugging USB Compact flash reader
Date: Sat, 10 Aug 2002 19:49:13 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-102900871927239@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-102886829118655@msgid-missing>
> 1. Is it correct to modify usb.agent itself? Should I
> rather include the VID-PID and other details in
> the handbook/userbook?
Don't modify usb.agent, no ... /etc/hotplug/usb/$DRIVERNAME
is where you put per-driver setup/config tweaks.
From what you said, you're assuming only one reader (or
SCSI-ish device) will ever be connected ... you're choosing
a single device name and mount point. That's error prone;
the reason is that you're using the wrong level of hotplug
event. As I said earlier, to solve this safely you need
higher level hotplug events: "here's a disk" (/dev/sdc or
whatever).
> 2. What is the "match-flag"?? AFAI can see it seems to
> be a "mask flag" - something to be 'anded' with
> something else. What is the principle behind it?
See <linux/usb.h> for "struct usb_device_id" support.
> 3. This is premature, but could someone give me a hint
> as to which desktop agent I should be talking to?
To my knowledge, there is no such desktop agent yet.
That's why I suggested you be prepared to write one.
- Dave
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
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
prev parent reply other threads:[~2002-08-10 19:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-09 4:40 Hotplugging USB Compact flash reader Ajay
2002-08-10 4:58 ` Ajay
2002-08-10 19:49 ` David Brownell [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=marc-linux-hotplug-102900871927239@msgid-missing \
--to=david-b@pacbell.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.