From: Kees Cook <kees@outflux.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: work-around for video4linux sysfs
Date: Tue, 07 Aug 2007 23:18:13 +0000 [thread overview]
Message-ID: <20070807231813.GX9617@outflux.net> (raw)
In-Reply-To: <20070731195136.GW9881@outflux.net>
Hi Kay,
On Wed, Aug 08, 2007 at 12:58:43AM +0200, Kay Sievers wrote:
> Look at drivers/media/video/videodev.c how the "name" attribute is
> created. There should probably be common "function" names added to
> the v4l core which are just referenced by the drivers, like the
> defines for the device type in include/media/v4l2-dev.h which are
> replaced by strings in drivers/media/video/videodev.c.
Okay, thanks. I'll try to find some time to investigate this.
> Yeah, I see the problem, and it's time to solve it. Maybe you can try to
> add the stuff to the drivers you have access to the hardware, and we can
> come up with a working prototype, propose that to the v4l maintainer(s)
> and convert the other drivers step by step. Persistent names would just
> rely on that feature to be added to the driver for devices with multiple
> nodes of the same type.
Sure, that sounds right.
> Btw, what does:
> grep . /sys/class/video4linux/*/*
> print on your box? If you have access to the device with the multiple
> nodes.
$ grep . /sys/class/video4linux/*/* 2>/dev/null
/sys/class/video4linux/radio0/dev:81:64
/sys/class/video4linux/radio0/name:cx88[0] radio (pcHDTV HD3000 HD
/sys/class/video4linux/vbi0/dev:81:224
/sys/class/video4linux/vbi0/name:cx88[0] vbi (pcHDTV HD3000 HDTV
/sys/class/video4linux/vbi1/dev:81:225
/sys/class/video4linux/vbi1/name:ivtv0 encoder VBI
/sys/class/video4linux/video0/dev:81:0
/sys/class/video4linux/video0/name:cx88[0] video (pcHDTV HD3000 HD
/sys/class/video4linux/video1/dev:81:1
/sys/class/video4linux/video1/name:ivtv0 encoder MPEG
/sys/class/video4linux/video24/dev:81:24
/sys/class/video4linux/video24/name:ivtv0 encoder PCM audio
/sys/class/video4linux/video32/dev:81:32
/sys/class/video4linux/video32/name:ivtv0 encoder YUV
How's that for a mess? ;)
Thanks again,
-Kees
--
Kees Cook @outflux.net
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
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
next prev parent reply other threads:[~2007-08-07 23:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 19:51 work-around for video4linux sysfs Kees Cook
2007-08-01 20:52 ` Greg KH
2007-08-01 21:31 ` Kees Cook
2007-08-01 21:58 ` Greg KH
2007-08-01 22:22 ` Kees Cook
2007-08-01 22:39 ` Greg KH
2007-08-01 23:14 ` Kees Cook
2007-08-01 23:28 ` Greg KH
2007-08-01 23:48 ` Kees Cook
2007-08-02 9:24 ` Kay Sievers
2007-08-02 14:05 ` Kees Cook
2007-08-02 22:30 ` Kay Sievers
2007-08-02 22:39 ` Linas Vepstas
2007-08-02 23:02 ` Kay Sievers
2007-08-07 0:39 ` Kees Cook
2007-08-07 9:24 ` Kay Sievers
2007-08-07 19:36 ` Kees Cook
2007-08-07 22:58 ` Kay Sievers
2007-08-07 23:18 ` Kees Cook [this message]
2007-08-08 10:48 ` Kay Sievers
2007-08-09 19:38 ` Kees Cook
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=20070807231813.GX9617@outflux.net \
--to=kees@outflux.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 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).