Em Tue, 29 Jan 2013 16:40:18 +0100 Gianluca Gennari <gennarone@xxxxxxxxx> escreveu: > Il 29/01/2013 15:59, Hans Verkuil ha scritto: > > On Tue January 29 2013 15:18:12 Olivier Subilia wrote: > >> Hi, > >> > >> First of all, I've no experience with this mailing list. I'm not sure > >> I'm sending my report to the right place. If not, please don't hesitate > >> to tell it to me (possibly with the right place address). > >> > >> I'm desperately trying to compile v4l drivers for a PCTV quatrostick > >> nano. Following this page > >> > >> http://www.linuxtv.org/wiki/index.php/PCTVSystems_QuatroStick-nano_520e > >> > >> it uses the em28xx driver. > >> > >> my configuration: `uname -r` = 3.2.0-35-generic-pae > >> > >> So I tried to compile it with > >> > >> $ git clone git://linuxtv.org/media_build.git > >> $ cd media_built > >> $ ./build >log.log (file attached) > >> > >> STDERR: > >> > >> Cloning into 'media_build'... > >> remote: Counting objects: 1813, done. > >> remote: Compressing objects: 100% (591/591), done. > >> remote: Total 1813 (delta 1223), reused 1751 (delta 1183) > >> Receiving objects: 100% (1813/1813), 423.66 KiB, done. > >> Resolving deltas: 100% (1223/1223), done. > >> multimedia@serveur:~$ cd media_build/ > >> multimedia@serveur:~/media_build$ ./build >log.log > >> From git://linuxtv.org/media_build > >> * branch master -> FETCH_HEAD > >> --2013-01-29 14:52:49-- > >> http://linuxtv.org/downloads/drivers/linux-media-LATEST.tar.bz2.md5 > >> Resolving linuxtv.org (linuxtv.org)... 130.149.80.248 > >> Connecting to linuxtv.org (linuxtv.org)|130.149.80.248|:80... connected. > >> HTTP request sent, awaiting response... 200 OK > >> Length: 93 [application/x-bzip2] > >> Saving to: `linux-media.tar.bz2.md5.tmp' > >> > >> 100%[=========================================================================================================================================>] > >> 93 --.-K/s in 0s > >> > >> 2013-01-29 14:52:49 (7.72 MB/s) - `linux-media.tar.bz2.md5.tmp' saved > >> [93/93] > >> > >> cat: linux-media.tar.bz2.md5: No such file or directory > >> --2013-01-29 14:52:49-- > >> http://linuxtv.org/downloads/drivers/linux-media-LATEST.tar.bz2 > >> Resolving linuxtv.org (linuxtv.org)... 130.149.80.248 > >> Connecting to linuxtv.org (linuxtv.org)|130.149.80.248|:80... connected. > >> HTTP request sent, awaiting response... 200 OK > >> Length: 4502249 (4.3M) [application/x-bzip2] > >> Saving to: `linux-media.tar.bz2' > >> > >> 100%[=========================================================================================================================================>] > >> 4'502'249 5.47M/s in 0.8s > >> > >> 2013-01-29 14:52:50 (5.47 MB/s) - `linux-media.tar.bz2' saved > >> [4502249/4502249] > >> > >> --2013-01-29 14:52:51-- > >> http://www.linuxtv.org/downloads/firmware//dvb-firmwares.tar.bz2 > >> Resolving www.linuxtv.org (www.linuxtv.org)... 130.149.80.248 > >> Connecting to www.linuxtv.org (www.linuxtv.org)|130.149.80.248|:80... > >> connected. > >> HTTP request sent, awaiting response... 200 OK > >> Length: 649441 (634K) [application/x-bzip2] > >> Saving to: `dvb-firmwares.tar.bz2' > >> > >> 100%[=========================================================================================================================================>] > >> 649'441 1.41M/s in 0.4s > >> > >> 2013-01-29 14:52:51 (1.41 MB/s) - `dvb-firmwares.tar.bz2' saved > >> [649441/649441] > >> > >> > >> ln: accessing `../../linux/firmware/dabusb//*': No such file or directory > >> /home/multimedia/media_build/v4l/anysee.c: In function > >> 'anysee_frontend_attach': > >> /home/multimedia/media_build/v4l/anysee.c:893:2: warning: 'ret' may be > >> used uninitialized in this function [-Wuninitialized] > >> /home/multimedia/media_build/v4l/m920x.c: In function 'm920x_probe': > >> /home/multimedia/media_build/v4l/m920x.c:91:6: warning: 'ret' may be > >> used uninitialized in this function [-Wuninitialized] > >> /home/multimedia/media_build/v4l/m920x.c:70:6: note: 'ret' was declared here > >> /home/multimedia/media_build/v4l/mxl111sf.c:58:0: warning: "err" > >> redefined [enabled by default] > >> include/linux/usb.h:1655:0: note: this is the location of the previous > >> definition > >> /home/multimedia/media_build/v4l/ngene-cards.c:813:2: warning: > >> initialization discards 'const' qualifier from pointer target type > >> [enabled by default] > >> /home/multimedia/media_build/v4l/mxl111sf-tuner.c:34:0: warning: "err" > >> redefined [enabled by default] > >> include/linux/usb.h:1655:0: note: this is the location of the previous > >> definition > >> /home/multimedia/media_build/v4l/mxl111sf-tuner.c:34:0: warning: "err" > >> redefined [enabled by default] > >> include/linux/usb.h:1655:0: note: this is the location of the previous > >> definition > >> WARNING: "snd_tea575x_set_freq" > >> [/home/multimedia/media_build/v4l/radio-shark.ko] undefined! > >> WARNING: modpost: Found 1 section mismatch(es). > >> To see full details build your kernel with: > >> 'make CONFIG_DEBUG_SECTION_MISMATCH=y' > >> > >> > >> No other compilation error. 524 modules founds. But if I check em28xx > >> family modules: > >> > >> $ ls v4l/em28xx*.ko > >> ls: cannot access v4l/em28xx*.ko: No such file or directory > >> > >> In other words: no module is compiled with this. > >> All (most ?) other modules are compiled in v4l/*.ko > >> > >> What am I doing wrong ? > > > > Nothing :-) > > > > I can reproduce this myself. It works fine for all kernels except 3.2 and 3.3. > > One workaround is to run 'make menuconfig' in the media_build directory, turn > > on the em28xx modules, and run 'make' to build everything. > > > > Why it isn't automatically selected when compiling for those kernels is a > > mystery to me. > > > > Regards, > > > > Hans > > > > Another similar bug that I noticed recently on kernel > 2.6.32-45-generic-pae (Ubuntu 10.04): > > - the default .config file is OK; > - .config files produced by 'make allmodconfig', 'make stagingconfig' > are OK; > - .config produced by 'make menuconfig' or 'make xconfig' are NOT OK and > the build fails! > > The error is this: > > media_build/v4l/au8522_dig.c:748: error: redefinition of 'au8522_attach' > media_build/v4l/au8522.h:69: note: previous definition of > 'au8522_attach' was here > make[3]: *** [media_build/v4l/au8522_dig.o] Error 1 > make[3]: *** Waiting for unfinished jobs.... > make[2]: *** [_module_media_build/v4l] Error 2 > make[2]: Leaving directory `/usr/src/linux-headers-2.6.32-45-generic-pae' > > In the bad .config file the modules: > > CONFIG_DVB_AU8522_DTV=m > CONFIG_DVB_AU8522_V4L=m > > are enabled, but the main option: > > CONFIG_DVB_AU8522=m > > is missing! Adding it manually fixes the problem. I really have no idea > about the origin of the problem, but I'm sure that a few months ago > everything was working properly. There are some new Kconfig syntax used by the media Kconfig files that aren't available on legacy kernels. A make menuconfig will not honor those rules with unknown syntax. This is one of those changes that I remember: commit df835c2e7fa875618cc14ced0110ea96f79536fb Author: Michal Marek <mmarek@xxxxxxx> Date: Fri Nov 26 17:15:11 2010 +0100 kconfig: Document the new "visible if" syntax Signed-off-by: Michal Marek <mmarek@xxxxxxx> It was needed because some previous Kbuild patch broke the handling of some media symbols, and affects 3 menus: drivers/media/dvb-frontends/Kconfig: visible if !MEDIA_SUBDRV_AUTOSELECT drivers/media/i2c/Kconfig: visible if !MEDIA_SUBDRV_AUTOSELECT drivers/media/tuners/Kconfig: visible if !MEDIA_SUBDRV_AUTOSELECT Not handling it would work as if MEDIA_SUBDRV_AUTOSELECT is not selected, so users need to manually select the needed frontends, I2C chips and tuners for kernels before this patch: $ git describe df835c2e7fa875618cc14ced0110ea96f79536fb v2.6.39-rc1-13-gdf835c2 E. g. kernels up to 2.6.38. A patch fixing it likely simple. I suspect that adding: s,visible if,depends on,g at v4l/scripts/make_kconfig.pl if the Kernel is bellow to 2.6.39 will solve it (needs testing though). It should be noticed, however, that the Makefile rules may require some changes, as it may be needed to re-generate it if the user requests to compile against a different Kernel version. I think that there are other similar changes, but I can't remember on what Kernel versions we needed to change Kconfig rules due to some syntax or semantics change at Kbuild language anymore. So, a more complete fix would require one to double-check when those changes happened at the kernel and write the proper backport logic. Another alternative would be to ship the scripts that parse the Kconfig with the current syntax inside the media-build. That's probably the best long-term solution. Anyway, we never found enough time for that, as there are already lots of pending work at the drivers themselves. So, patches are welcome. Cheers, Mauro -- 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
