From: Janne Grunau <j@jannau.net>
To: David Brownell <david-b@pacbell.net>
Cc: Hans de Goede <hdegoede@redhat.com>,
Hans Verkuil <hverkuil@xs4all.nl>,
Laurent Pinchart <laurent.pinchart@skynet.be>,
linux-media@vger.kernel.org,
Ricardo Jorge da Fonseca Marques Ferreira <storm@sys49152.net>,
linux-usb@vger.kernel.org
Subject: Re: v4l parent for usb device interface or device?
Date: Fri, 27 Mar 2009 21:59:23 +0100 [thread overview]
Message-ID: <20090327205923.GA6064@aniel> (raw)
In-Reply-To: <200903261831.55746.david-b@pacbell.net>
On Thu, Mar 26, 2009 at 06:31:55PM -0700, David Brownell wrote:
> On Thursday 26 March 2009, Janne Grunau wrote:
>
> > I noticed a problem after
> > changing the hdpvr driver accordingly.
> >
> > With parent set to the usb interface there is no longer easy access to
> > the usb device properties like the serial number through sysfs. I know
> > that a couple of user with more than one device use the serial number
> > to set static device nodes through udev.
>
> The serial number is still available, but it's coupled to the USB
> device not its interface. Make your udev script hop up a level or
> two in the driver model tree, as appropriate.
yes, ATTRS{} still matches. There are udev howtos around which suggest
ATTRS{} just matches one level up and not the entire path. I tried it but
had unfortunately a typo in the udev rule. Sorry for the noise.
Janne
next prev parent reply other threads:[~2009-03-27 20:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 14:58 v4l parent for usb device interface or device? Hans Verkuil
2009-03-26 12:29 ` Hans de Goede
2009-03-26 18:14 ` Theodore Kilgore
2009-03-27 0:51 ` Janne Grunau
2009-03-27 1:31 ` David Brownell
2009-03-27 20:59 ` Janne Grunau [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-03-25 10:18 Hans de Goede
2009-03-25 14:51 ` Laurent Pinchart
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=20090327205923.GA6064@aniel \
--to=j@jannau.net \
--cc=david-b@pacbell.net \
--cc=hdegoede@redhat.com \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart@skynet.be \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=storm@sys49152.net \
/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.