From: Kay Sievers <kay.sievers@vrfy.org>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: linux1394-devel@lists.sourceforge.net,
linux-hotplug@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] firewire: core: add sysfs attribute for easier udev rules
Date: Sat, 23 May 2009 02:35:36 +0200 [thread overview]
Message-ID: <ac3eb2510905221735lc5de01j334618ddeb72a813@mail.gmail.com> (raw)
In-Reply-To: <tkrat.acafb37c21e20784@s5r6.in-berlin.de>
On Fri, May 22, 2009 at 23:17, Stefan Richter <stefanr@s5r6.in-berlin.de> wrote:
> This adds the attribute /sys/bus/firewire/devices/fw[0-9]+/units. It
> can be used in udev rules like the following ones:
>
> # IIDC devices: industrial cameras and some webcams
> SUBSYSTEM=="firewire", ATTR{units}=="*0x00a02d:0x00010?*", GROUP="video"
>
> # AV/C devices: camcorders, set-top boxes, TV sets, audio devices, ...
> SUBSYSTEM=="firewire", ATTR{units}=="*0x00a02d:0x010001*", GROUP="video"
> Here is an example of a node which implements an IPv4 unit and an IPv6
> unit: $ cat /sys/bus/firewire/devices/fw2/units
> 0x00005e:0x000001 0x00005e:0x000002
Looks great. Let me know when you are merging this, so we can put the
rules in the udev tree.
Thanks,
Kay
next prev parent reply other threads:[~2009-05-23 0:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tkrat.d86e749d664670a9@s5r6.in-berlin.de>
[not found] ` <ac3eb2510905211001m77eda9e4gb73001d504fd5376@mail.gmail.com>
[not found] ` <4A159899.20506@s5r6.in-berlin.de>
[not found] ` <4A165CED.8030601@s5r6.in-berlin.de>
[not found] ` <ac3eb2510905220423h23e7aca1u3bc7c204db551eb0@mail.gmail.com>
2009-05-22 21:16 ` [PATCH 1/2] firewire: core: check for missing struct update at build time, not run time Stefan Richter
2009-05-22 21:17 ` [PATCH 2/2] firewire: core: add sysfs attribute for easier udev rules Stefan Richter
2009-05-22 22:03 ` Stefan Richter
2009-05-23 0:35 ` Kay Sievers [this message]
2009-05-24 12:09 ` Stefan Richter
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=ac3eb2510905221735lc5de01j334618ddeb72a813@mail.gmail.com \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=stefanr@s5r6.in-berlin.de \
/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