From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: work-around for video4linux sysfs
Date: Wed, 01 Aug 2007 21:58:35 +0000 [thread overview]
Message-ID: <20070801215835.GA25928@kroah.com> (raw)
In-Reply-To: <20070731195136.GW9881@outflux.net>
On Wed, Aug 01, 2007 at 02:31:30PM -0700, Kees Cook wrote:
> On Wed, Aug 01, 2007 at 01:52:45PM -0700, Greg KH wrote:
> > On Tue, Jul 31, 2007 at 12:51:37PM -0700, Kees Cook wrote:
> > > I proposed the change below while Kay and Scott were at GUADEC, and
> > > it seems the response was generally negative, but without any better
> > > suggestions. I'd like to bring this up again, as I think this solution,
> > > while being a bit of hack, should at least be forward-compatible if/when
> > > v4l sysfs stuff is sorted out better.
> >
> > Why can't we just fix the kernel code to do the right thing?
>
> Because I'm more familiar with writing udev rules than coding sysfs? :)
>
> Mostly I have no idea what the scope of the changes are for v4l sysfs
> fixes. It's not clear to me if each subdriver needs to be fixed, or if
> it's just a matter of getting the core of v4l fixed up.
>
> Is the idea of /dev/v4l/by-path/... sane? Once v4l sysfs was fixed,
> it seems that to support this symlink, the path_id tool would still need
> at least the second patch hunk. Is this correct?
Probably, and yes, the v4l by-path stuff is a good idea, I'm not trying
to keep that from happening. But are there ids on these devices you can
use too, to get a "by-id" path as well? Do the USB or PCI devices have
a serial number associated with them?
> By my estimation, the v4l sysfs is missing a "driver" linkage? I'm not
> entirely sure where to start looking.
What does the v4l device sysfs directory tree look like? Is the
"driver" link the only thing you are missing to do this in an easier
manner in your script?
thanks,
greg k-h
-------------------------------------------------------------------------
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-01 21:58 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 [this message]
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
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=20070801215835.GA25928@kroah.com \
--to=greg@kroah.com \
--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).