From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev and USB ID
Date: Tue, 13 Jan 2004 00:56:58 +0000 [thread overview]
Message-ID: <20040113005658.GA5095@kroah.com> (raw)
In-Reply-To: <1073748412.5057.14.camel@t40>
On Sat, Jan 10, 2004 at 05:26:52PM +0200, Paul Ionescu wrote:
> How can I put in /etc/udev/udev.rules something like
> SYSFS_id="0c76:0005" ?
SYSFS_idVendor="0c76", SYSFS_idProduct="0005"
should work just fine. You can look for more than one sysfs attribute.
> I tried last night udev, and is really great, but it took me one hour to
> discover why it ignores the line SYSFS_vendor="OLYMPUS".
> Well the good news is that udev was fine and not ignoring this line, BUT
> the good guys at olympus made a joke and I had to put it
> SYSFS_vendor="OLYMPUS " <- Yes with a trailing space. They put an extra
> space at the end :(
> And it was a pain to find it, I had to use strace on udev, just because
> I didn't know any other choice.
Dump the sysfs file through a hex dump program (like xxd). That
trailing space is quite common for digital cameras for some reason (took
me forever to figure it out too...)
thanks,
greg k-h
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
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:[~2004-01-13 0:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-10 15:26 udev and USB ID Paul Ionescu
2004-01-13 0:56 ` Greg KH [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=20040113005658.GA5095@kroah.com \
--to=greg@kroah.com \
--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).