From: Kees Cook <kees@outflux.net>
To: video4linux-list@redhat.com
Cc: Kay Sievers <kay.sievers@vrfy.org>
Subject: [PATCH 0/2] V4L: add "function" sysfs attribute to v4l devices
Date: Wed, 16 Apr 2008 18:23:46 -0700 [thread overview]
Message-ID: <20080417012346.GG18929@outflux.net> (raw)
Hello!
Two patches follow, related to discussions[1][2] on the hotplug mailing
list, in an attempt to solve enumeration problems when multiple v4l
devices are present in a system and the resulting init order was not
guaranteed to be the same from boot-to-boot (video0 isn't always the
same device). The goal is to create things like this with udev:
pci-0000:01:06.0-video-mpeg-cap -> ../../video0
pci-0000:01:07.0-video-yuv-cap -> ../../video1
pci-0000:01:06.0-video-yuv-cap -> ../../video24
First patch is the sysfs infrastructure to support exporting a
"function" string. This value is related to the existing "type" field,
but is singular in use and not designed for internal driver use, as
"type" seems to be.
Second patch is a first stab at providing "function" entries for
hardware I have access to.
Thanks,
-Kees
[1] http://marc.info/?t=118591155400012&r=1&w=2
[2] some recent discussion on the new hotplug list, but I can't find an
archive link since it moved to vger...
--
Kees Cook @outflux.net
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next reply other threads:[~2008-04-17 2:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-17 1:23 Kees Cook [this message]
2008-04-17 22:08 ` [PATCH 0/2] V4L: add "function" sysfs attribute to v4l devices 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=20080417012346.GG18929@outflux.net \
--to=kees@outflux.net \
--cc=kay.sievers@vrfy.org \
--cc=video4linux-list@redhat.com \
/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