Hi Samuel, On Friday 25 June 2010 12:01:42 Samuel Xu wrote: > One correction: After make and make install, uvcvideo module can't > auto loaded any more. I must manually "insmod uvcvideo.ko" to load it. > > Here is lsmod result, I never have chance to make uvcvideo module used > bit to 1 :( > [root@user-desktop uvc]# lsmod > Module Size Used by > uvcvideo 46182 0 > rt2860sta 406917 1 > battery 7968 0 > > After 2 questions, there is dmesg from uvcvideo after my manually > insmod, any idea? > Another question is: If newest v4l code tree has been advanced much > than src tree inside 2.6.33 kernel, which v4l src label is nearest > from src tree inside 2.6.33 kernel? > 3rdd question is: if I want to build v4l driver from src inside 2.6.33 > kernel directly. How should I do? (I tried to make menuconfig and make > modules from a clean kernel, while insmod the newly build uvcvideo.ko > reports: insmod: error inserting './uvcvideo.ko': -1 Invalid module > format You can checkout the latest v4l-dvb source from mercurial (or download a snapshot), and run make SRCDIR=/path/to/your/kernel/2.6.33/source/tree Make sure your kernel source tree has been configured (you might need to compile it as well, not sure about that). > [ 78.446109] uvcvideo: Found UVC 1.00 device CNF7129 (04f2:b071) > [ 78.462540] ------------[ cut here ]------------ > [ 78.462569] WARNING: at drivers/media/video/v4l2-dev.c:420 > __video_register_device+0x44/0x3d7() [snip] I'm pretty sure this is a mismatch between the uvcvideo and videodev kernel modules. Please reinstall the whole v4l-dvb subsystem, either from your distribution packages or from the v4l-dvb repository. Make sure both the uvcvideo driver and the v4l-dvb core come from the same source. -- Regards, Laurent Pinchart -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
