please test and keyword media-video/spca5xx-20050903
x86 & ppc: please also stable 20050701
bump, it's been over a month now......
Just curious, but why are you bumping a bug? This isn't a web forum, bugs don't just disappear.
Note to self: attempt support for the following device: Bus 003 Device 005: ID 046d:0870 Logitech, Inc. QuickCam Express add check for CONFIG_VIDEO_DEV to ebuild in reply to comment #3: Because I think that a bug with over 30 days of no activity is unacceptable. If there truely wasn't any hardware, then it should have been stated as such, instead of keeping me hanging.
Perhaps you missed the reply to bug #104940 where it was stated that we do not have the hardware to test this ebuild. The truth is that without more information, I have no clue whether I have the hardware to test this or not. What devices does this driver support? What methods should we use for testing? Please provide us with a proper list of supported hardware and a test case for us to use to determine if this package can be keyworded for x86. We can do a compile test, but that doesn't determine whether or not the package actually works. In any case, I don't appreciate the attitude towards the x86 team, as we are still forming and you're asking for testing on a hardware-specific ebuild, which, as far as I know, none of us own. You also failed to mention anywhere in this bug report that testing for this ebuild qould require a specific piece of hardware, leaving all of the research work on the part of the architecture teams. As the package maintainer, it is your responsibility to inform the arch teams on specifics that might be deemed necessary knowledge if you're going to request our help in stabilizing packages. You should not be pushing work onto the arch teams unnecessarily. With the information provided, I would be unable to determine what this package even does, let alone know that I would need a piece of hardware to properly KEYWORD it.
(In reply to comment #5) > Perhaps you missed the reply to bug #104940 where it was stated that we do not > have the hardware to test this ebuild. I surely did. I don't look at all my bugs before making a response. > The truth is that without more > information, I have no clue whether I have the hardware to test this or not. > > What devices does this driver support? http://mxhaard.free.fr/spca5xx.html > What methods should we use for testing? use any v4l viewer(including spcaview) and see if the camera is being displayed on the screen. > Please provide us with a proper list of supported hardware and a test case for > us to use to determine if this package can be keyworded for x86. We can do a > compile test, but that doesn't determine whether or not the package actually > works. > In any case, I don't appreciate the attitude towards the x86 team, as we > are still forming and you're asking for testing on a hardware-specific ebuild, > which, as far as I know, none of us own. You also failed to mention anywhere in > this bug report that testing for this ebuild qould require a specific piece of > hardware, leaving all of the research work on the part of the architecture teams. Get used to it, this is frequently how the bugs come in. > As the package maintainer, it is your responsibility to inform the arch teams on > specifics that might be deemed necessary knowledge if you're going to request > our help in stabilizing packages. You should not be pushing work onto the arch > teams unnecessarily. With the information provided, I would be unable to > determine what this package even does, let alone know that I would need a piece > of hardware to properly KEYWORD it. Look at the DESCRIPTION field of the ebuild. "spca5xx driver for webcams." As for jumping down my throat, don't do it. If you have a problem with the way I do something, then contact me privatly or follow the other inter-developer relations protocols. You can even refuse to keyword it(this hurts your users, not mine) Being nasty on bugs is uncalled for. As for the info that you requested, I've provided it. I would have provided it a month ago had someone asked. It's all freely available with about 2 minutes of going through the links/info in the ebuild.
I have the hardware and have been working with kingtaco to get this working but unfortunately spca5xx does not know the id of my camera yet. But we hope to get that fixed some time soon.
Just to let you know the latest ebuild does not compile with gentoo-sources-2.6.14.
Just to let you know that with the latest source ( 20051105 ), the compilation pb has gone for kernel > 2.6.14 (here i used x86-64 kernel 2.6.14-mm1 ) which seems confirmed by the changelog where it is mentionned a correction for build problem against kernel > 2.6.14 . Tested with a PCCAM 750 : works OK.
I have a Creative WebCam Live! I just installed the latest version of spca5xx-20051105 by modifying the ebuild it compiles perfect except for a single warning and works really well.
Which arch are you testing on?
I am using the 20051105 code release of the spca5xx driver 0.57.05
(In reply to comment #10) > I have a Creative WebCam Live! I just installed the latest version of > spca5xx-20051105 by modifying the ebuild it compiles perfect except for a single > warning and works really well. (In reply to comment #11) > Which arch are you testing on? I'm using the latest spca5xx-20051105 with a Creative Webcam Instant in my ibook (ppc) and it works well, my kernel version is gentoo-sources-2.6.14-r3.
Just letting everyone know that 20051001 is not new enough to compile on 2.6.14.
(In reply to comment #14) > Just letting everyone know that 20051001 is not new enough to compile on 2.6.14. I'll work with upstream on this. Could you post a build log or the errors? (I'm not yet on .14)
(In reply to comment #15) > > I'll work with upstream on this. Could you post a build log or the errors? (I'm > not yet on .14) Look at comment #9. But here is the error for reference: make[1]: Entering directory `/usr/src/linux-2.6.14-gentoo-r4' CC [M] /var/tmp/portage/spca5xx-20051001/work/spca5xx-20051001/drivers/usb/spca5xx.o CC [M] /var/tmp/portage/spca5xx-20051001/work/spca5xx-20051001/drivers/usb/spcadecoder.o In file included from /var/tmp/portage/spca5xx-20051001/work/spca5xx-20051001/drivers/usb/spcadecoder.h:5, from /var/tmp/portage/spca5xx-20051001/work/spca5xx-20051001/drivers/usb/spcadecoder.c:35: /var/tmp/portage/spca5xx-20051001/work/spca5xx-20051001/drivers/usb/spca5xx.h:23:5: warning: "LINUX_VERSION_CODE" is not defined /var/tmp/portage/spca5xx-20051001/work/spca5xx-20051001/drivers/usb/spca5xx.h:23:26: warning: "KERNEL_VERSION" is not defined /var/tmp/portage/spca5xx-20051001/work/spca5xx-20051001/drivers/usb/spca5xx.h:23:40: missing binary operator before token "(" /var/tmp/portage/spca5xx-20051001/work/spca5xx-20051001/drivers/usb/spca5xx.h:44:5: warning: "LINUX_VERSION_CODE" is not defined /var/tmp/portage/spca5xx-20051001/work/spca5xx-20051001/drivers/usb/spca5xx.h:44:26: warning: "KERNEL_VERSION" is not defined /var/tmp/portage/spca5xx-20051001/work/spca5xx-20051001/drivers/usb/spca5xx.h:44:40: missing binary operator before token "(" /var/tmp/portage/spca5xx-20051001/work/spca5xx-20051001/drivers/usb/spca5xx.h:51:27: linux/tqueue.h: No such file or directory /var/tmp/portage/spca5xx-20051001/work/spca5xx-20051001/drivers/usb/spca5xx.h:54:5: warning: "LINUX_VERSION_CODE" is not defined /var/tmp/portage/spca5xx-20051001/work/spca5xx-20051001/drivers/usb/spca5xx.h:54:27: warning: "KERNEL_VERSION" is not defined /var/tmp/portage/spca5xx-20051001/work/spca5xx-20051001/drivers/usb/spca5xx.h:54:41: missing binary operator before token "(" In file included from /var/tmp/portage/spca5xx-20051001/work/spca5xx-20051001/drivers/usb/spcadecoder.h:5, from /var/tmp/portage/spca5xx-20051001/work/spca5xx-20051001/drivers/usb/spcadecoder.c:35: /var/tmp/portage/spca5xx-20051001/work/spca5xx-20051001/drivers/usb/spca5xx.h:459: error: field `task' has incomplete type make[2]: *** [/var/tmp/portage/spca5xx-20051001/work/spca5xx-20051001/drivers/usb/spcadecoder.o] Error 1
When there is a version that is ready to go stable, please readd us to CC.
doesn't seem to be anything else to do here
the ebuild 20060202 works fine here on my x86 with a 2.6.15 kernel and with my Creative NX Zc301+.
