Greg KH wrote: > > Looks like a bug in the driver or v4l2 layer. > > Can you send this to the video 4 linux developers instead? They are the > ones that need to know about this. > > thanks, > > greg k-h > Apologies for not doing the right thing from the start but in the end I did in fact fetch the latest v4l-dvb tree from the video4linux mercurial repository, compiled it against 2.6.30.4, installed the modules, whereupon the problem was fixed. Mea culpa. Only question that remains is how does that fix make it into the kernel, since it is clearly broken in 2.6.30, when might it be merged/fixed ? -- Tony Cook Lewiston 5501 Ph. +61 (0)8 8524 3418 Mob. +61 (0)4 2885 2512 -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
