Nick Morrott wrote: > On 09/04/2008, Duncan Webb <[EMAIL PROTECTED]> wrote: > >> One solution is that the video drivers could be blacklisted and >> modprobed after udev has started. >> A second solution is that some udev rules could be written to link the >> devices to some other name. (but I'm rather found of /dev/videoX as the >> device name as it represents what it is.) >> >> I'm just wondering if anyone has a better solution for this problem and >> what it is? > > The ivtv driver still (as far as I can tell, looking at > http://www.linuxtv.org/hg/v4l-dvb/file/6e0ba8a3aa32/linux/drivers/media/video/ivtv/ivtv-driver.c) > supports the 'ivtv_first_minor' module parameter to control which > /dev/videoX device it creates when loaded.
Thanks this is good to know and is a nice solution. I've always found the numbering of the video devices a bit odd, difficult to remember and don't really say what they do. /dev/video0 -> video mpg encode (ro) /dev/video16 -> video mpg decode (wo) /dev/video32 -> video yuv encode (ro) /dev/video48 -> video yuv decode (wo) /dev/video24 -> audio pcm output (ro) I wonder if there is a way to use a udev rule to rename the other devices. I think that it would be nicer if a device that has more than one sub-device created a directory in /dev so you would end up with devices like: /dev/ivtv0/video /dev/ivtv0/vbi /dev/ivtv0/radio /dev/ivtv0/audio /dev/ivtv0/yuv-out or /dev/ivtv0/yuv-encode Then it would be easy to write udev rules that made symlinks and there would be some relationship between a module name and a device. Thanks again for the tip. Duncan _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
