From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Date: Wed, 01 Aug 2007 21:58:35 +0000 Subject: Re: work-around for video4linux sysfs Message-Id: <20070801215835.GA25928@kroah.com> List-Id: References: <20070731195136.GW9881@outflux.net> In-Reply-To: <20070731195136.GW9881@outflux.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org 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