According to the developer website, driver has been tested to work with 2.6 kernels all the way back to 2.6.9. However, the ebuild tests for the VIDEO_V4L1_COMPAT kernel config option, which makes it abort the build on any pre-V4L2 kernel - probably unnecessarily so, since it's actually a V4L1 driver. Reproducible: Always Steps to Reproduce: 1. Have a pre-V4L2 2.6 kernel (2.6.14 in my case) 2. emerge qc-usb-messenger 3. Shit hits the fan Actual Results: * Messages for package media-video/qc-usb-messenger-1.7: * CONFIG_VIDEO_V4L1_COMPAT: is not set when it should be. * Please check to make sure these options are set correctly. * Failure to do so may cause unexpected problems. * Once you have satisfied these options, please try merging * this package again. * * ERROR: media-video/qc-usb-messenger-1.7 failed. * Call stack: * ebuild.sh, line 49: Called pkg_setup * qc-usb-messenger-1.7.ebuild, line 25: Called linux-mod_pkg_setup * linux-mod.eclass, line 469: Called linux-info_pkg_setup * linux-info.eclass, line 613: Called check_extra_config * linux-info.eclass, line 511: Called die * The specific snippet of code: * die "Incorrect kernel configuration options" * The die message: * Incorrect kernel configuration options * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/media-video/qc-usb-messenger-1.7/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/media-video/qc-usb-messenger-1.7/temp/die.env'. * Expected Results: A working webcam driver uname -a Linux syslab-12 2.6.14-gentoo-r2 #5 PREEMPT Tue Nov 14 15:03:49 CET 2006 i686 VIA Nehemiah CentaurHauls GNU/Linux I'm not providing make.conf, as this should be irrelevant in this case.
My 2 cents. Update to stable kernel. Close this bug as WORKSFORME.
Not sure what you mean by "stable" - this was the default kernel in Gentoo at the time it was compiled. The machine is part of an embedded measurement system. I've got twenty of those in the lab. They've been running 24/7 for the last two years, and I'm rather unwilling to upgrade kernels without an emergency, _particularly_ because the upstream qc-usb driver works absolutely fine if I build it myself from source. The *only* thing that's not working for me is that the ebuild is overly protective - it tells me that this driver won't work on 2.6.14 (and prevents me from installing) while even the upstream website says it does (and it does, if I bypass portage).
We are up to qc-usb-messenger-1.8-r1 now for compability with 2.6.27 which will be stabilized. There is no plans to support backwards compability with this package.
