From: Clemens Ladisch <clemens@ladisch.de>
To: linux-hotplug@vger.kernel.org
Subject: udev: getting attributes from subdevice?
Date: Sat, 30 Jun 2012 17:15:26 +0000 [thread overview]
Message-ID: <4FEF342E.2040803@ladisch.de> (raw)
Hi,
I thought it would be useful to have persistent names for FireWire
devices:
########################################################################
ACTION="remove", GOTO="persistent_firewire_end"
SUBSYSTEM!="firewire", GOTO="persistent_firewire_end"
TEST="guid", SYMLINK+="firewire/by-id/guid-$attr{guid}"
TEST="vendor_name", TEST="model_name", \
OPTIONS="string_escape=replace", \
SYMLINK+="firewire/by-name/$attr{vendor_name} $attr{model_name}"
LABEL="persistent_firewire_end"
########################################################################
And these rules appear to work:
$ cat /sys/bus/firewire/devices/fw0/{vendor_name,model_name}
Linux Firewire
Juju
$ ls -l /dev/firewire/by-name/
lrwxrwxrwx 1 root root 9 2012-06-30 18:13 Linux_Firewire_Juju -> ../../fw0
However, there are devices where, due to some strange rules in the
FireWire specifications, some attributes end up belonging to a subdevice:
$ cat /sys/bus/firewire/devices/fw2/{vendor_name,model_name}
LaCie
cat: /sys/bus/firewire/devices/fw2/model_name: No such file or directory
$ cat /sys/bus/firewire/devices/fw2/fw2.0/model_name
Hard Drive Quadra
Okay, let's add some rules to handle this:
TEST="vendor_name", TEST!="model_name", WAIT_FOR="$kernel.0/model_name"
TEST="vendor_name", TEST!="model_name", TEST="$kernel.0/model_name", \
OPTIONS="string_escape=replace", \
SYMLINK+="firewire/by-name/$attr{vendor_name} $attr{$kernel.0/model_name}"
But this doesn't work, probably because $kernel is not substituted
before $attr:
$ ls -l /dev/firewire/by-name/
lrwxrwxrwx 1 root root 9 2012-06-30 18:13 LaCie_ -> ../../fw2
(It works if I use $attr{fw2.0/model_name}, but that isn't generic enough.)
Do I have to write a separate tool for extracting the name?
Regards,
Clemens
next reply other threads:[~2012-06-30 17:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-30 17:15 Clemens Ladisch [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-07-02 17:03 udev: getting attributes from subdevice? 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=4FEF342E.2040803@ladisch.de \
--to=clemens@ladisch.de \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).