g output after trying to run
> > Ekiga ?
> >
> Yes, the same version of Ekiga works with the trunk driver. My webcam is
> part of the laptop and can't be plugged out. Is their another way of
> debuging?
Yes, you can set the trace parameter when loading the module
modprobe u
gt; ...
Did you say ProScope ? So you're not using a Logitech webcam ? Do you know
which USB controller is used by the ProScope ? If it uses the spca525, you
might be suffering from the same hardware bug as Logitech users. If not, I
don't think I could really help without getting my hands on
og about the crash?Thanks!
Does Linux crash, or just the application ? The kernel should definitely not
crash. Do you get a kernel oops ? Does your system recover if you kill the
application ?
Best regards,
Laurent Pinchart
___
Linux-uvc-devel mailin
ere might of course be some that
I'm not aware of.
I've been told that the second revision webcams can have their firmware
upgraded, but Logitech is not known to make firmware upgrades available to
end-users. They could of course change their policy :-)
Cheers,
Laurent Pinchart
ou give more information about the
interference you noticed ?
> Laurent and Martin, what do you think about using mutexes for this?
Isochronous URBs are submitted in interrupt context, so we can't use mutexes
there.
Cheers,
Laurent Pinchart
___
. Why
was schedule not suitable ? Is the function called from interrupt context ?
Cheers,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
ting the camera as a video device, so
> I reloaded the module by doing an rmmod uvcvideo followed by
> modprobe uvcvideo, and that modprobe has hung. :( No output in dmesg about
> it.
modprobe hung with no message in dmesg ? That's weird. Try modprobe trace=15
to make the driver more verbose.
Cheers,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
ink it worked with
> split too (iirc) and works with trunk again. Don't worry here.
The split branch should work at least as good as the trunk. The only
user-visible difference is the control IDs. I will merge the split branch
into the trunk soon.
Cheers,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
bably is. The messages in the kernel log seems to indicate that
the module has been linked against a different kernel tree that the one your
are running.
Cheers,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
x27;
when the module is loaded) before plugging the webcam ? Then please send me
all the messages output by the driver to the kernel log, as well as the
device USB descriptors ('lsusb -d 046d: -v' with usbutils >= 0.72 or usbutils
CVS).
Cheers,
Laurent Pinchart
__
llation? I have
> tried both trunk and split branches of the driver with not much difference
> in behaviour.
>
> Any ideas how to debug this further?
Could you have a look at the kernel log (dmesg) after a failure with Ekiga ?
Cheers,
Laurent Pinchart
e buggy, and should be fixed.
The main issue is that many V4L2 drivers are buggy as well, so application
developers don't notice bugs in their software.
Try to contact the MPlayer development team. They will eventually fix MPlayer
if enough people ask them (nicel
nyway I can help for QC Fusion (debugging or anything) just
> tell me
We are looking for someone with a very good understanding of the EHCI driver.
As the problem isn't triggered by Windows, we suspect that splitting control
requests across USB frames might help. Unfortunately, that&#
ioctl fails ?
>
> I would be very interested in any workaround possible..., if I can help in
> any way...
Search the mailing list archive for a thread called "Experimental patch for
USB problem with Logitech webcams". Evgeny posted a few patches which might
help you.
Cheers,
...
> >> ...
> >
> > Did you say ProScope ? So you're not using a Logitech webcam ? Do you
> > know which USB controller is used by the ProScope ? If it uses the
> > spca525, you might be suffering from the same hardware bug as Logitech
> > users. If not, I
> Device Status: 0x0000
> (Bus Powered)
>
> info from /var/log/messages
> Dec 11 17:29:54 fa-hp kernel: Linux video capture interface: v2.00
> Dec 11 17:29:54 fa-hp kernel: usbcore: registered new driver uvcvideo
> Dec 11 17:29:54 fa-hp kernel: USB Video Class driver (v0.1.0)
>
> Linux: SuSE Linux 10.2 x64
> Kernel: 2.6.18.2-34
>
> any ideas ?
You could have a look at gphoto2, I think it supports USB imaging devices. You
won't be able to use it as a webcam.
Cheers,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
of a firmware update program, to turn the device into
a UVC webcam, supported by the Linux UVC driver.
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
Hi everybody,
the split branch has been merged to the trunk. There were no known bug in the
split branch code that were not present in the trunk, and reports so far
didn't show any blocking problem.
Please report any problem you run into with the split driver.
Cheers,
Laurent Pin
. Please report any new problem you notice.
Cheers,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
being said, Ivan N. Zlatev submitted a patch against the split branch to
add iSight support. We are discussing a few issues left with his code, which
should hopefully be resolved in the next few days. You should then see iSight
support committed to SVN.
Cheers,
Laurent Pinchart
___
nd 8 are the only values supported by the
> Logitech cameras.
Actually, the bit you are interested in are D0 and D3. 1 and 8 are the control
values.
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
bcams have a hardware bug which makes
the camera difficult to use. Some people experience the bug (the webcam stops
responding) and some don't. There is currently no way to work around it, and
no way if your computer will be affected.
Merry Christmas,
Laurent Pinchart
sed as a
starting point if anyone with some image processing background is interested
(it might be part of the official OpenCV package, I don't know about that).
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
h
27;t work (when I open it again
> with Ekiga or luvcview).
Do you mean it never works ? Or does it just fail from times to times ? I
tried what you described (with another Logitech webcam, but that shouldn't
matter) and didn't experience any problem.
Laurent Pinchart
___
Any idea someone?
> Any better idea for getting my webcam working with kopete?
If you have some C/C++ programming knowledge, Kopete wouldn't be difficult to
fix. I'm sure many people would thank you for your work :-)
Cheers,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
was still non-functional. Appended is what I did. (Quite a
> few fixes were just to quiet down gcc.)
luvcview uses the old pan/tilt API. Pan and tilt are not separate controls.
You should contact Michel Xhaard about that, he's the luvcview author.
Best regards,
Laurent Pinchart
___
;re the
first to report this problem. Does your platform support USB 2.0 ? Is it EHCI
(or OHCI/UHCI if it only supports USB 1.1) compliant ? You might want to
enable verbose debugging (and even add a few print statements to the driver)
to see if the buffers are allocated properly (are they b
1234:1: warning: this is the location of the
> previous definition
> make: *** [frmfmtenum.o] Error 1
>
> There was one other post about this but it seemed to have gotten hijacked.
> Any ideas on that error?
Are you using the latest driver version (revision 75 from the trunk) ? Which
kernel version are you running ? Do the kernel headers
(in /usr/include/linux) match the running kernel version ? Is your kernel
patched by your distribution ?
> Also, the xawtv error:
[snip]
> I have no other audio programs running that would be using OSS...I tried
> with aoss wrapper too...no diff.
xawtv is known to have issues with V4L2.
> Thanks for your time!
You're welcome :-)
Cheers,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
ve found that if you load the
> module with trace set to 15, then Ekiga is able to show the picture.
There are known timing-related hardware issues with Logitech webcams. The
problem doesn't affect all users. Nobody has been able to find a workaround
ll have something to test) but bad news
for you (because you will have to wait until I'm done :-)).
I'd like to have a look at the USB descriptors. Could you provide me with the
output of lsusb -v (usbutils 0.72 or CVS) ?
Cheers,
Laurent Pinchart
_
patch in the next few days. It might not work
though :-)
Cheers,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
artin, by the way, is it necessary to put the webcam in bayer mode to disable
the auto-exposure ? Or would the auto-exposure mode control do the job
alone ?
Cheers,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
happens and why Windows doesn't trigger the bug. In the meantime,
you can consider your webcam broken when connected to your specific computer.
It might work fine with another USB controller or another computer (even
changing the CPU clock could influence the webcam behaviour).
Laurent
Hi Adrian,
> Thanks a million for this. I'm looking forward to testing the patch for
> you!
Could you test the following patch ? Please use the latest driver revision
from SVN (75).
Cheers,
Laurent Pinchart
Index: u
Having an Optia webcam would help. I
wonder what those 2 bytes contain.
> Thanks for all your help. Any luck with creative giving some help?
They still haven't answered. I'll try to phone them tomorrow.
Cheers,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
of lsusb -v on the webcam
> device
I'm afraid your device is not UVC-compatible. The sn9c20x chipsets use a
vendor-specific protocol. The sn9c21x chipsets are UVC-compatible.
Cheers,
Laurent Pinchart
___
Linux-uvc-devel mailing l
him.
Cheers,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
Hi Adrian,
here's a patch that might fix the problem. It includes the previous patch. Let
me know if it helps.
Cheers,
Laurent Pinchart
Index: uvc_video.c
===
--- uvc_video.c (revision 75)
+++ uvc_video.c (working copy)
@@ -1
the code. This will be usefull for all the users who are interested
in raw image processing. There seem to be quite a lot of them lately :-)
Best regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berli
Michel Xhaard might be working on it, you could try to contact
> > him.
>
> I Will start to write a driver for the 20x series as well.
Is there any technical reason to duplicate the effort ?
Laurent Pinchart
___
Linux-uvc-devel mailing list
nice, but having them working
on two separate projects is clearly a waste of resources.
> I you guys need webspace or sth. like that for your development, I own a
> rootserver which I could give you some resources on.
> Or just what you need - also donat
ivers (where possible and where it makes sense) would
allow for a lot of code sharing. That would be great for developers and
end-users.
Cheers,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/m
ly stable.
> This would let you focus on particular features or add support for more
> hardware.
I can't answer for Michel here, but when I started developing the Linux UVC
driver, I decided to start from scratch instead of reusing current code from
kernel drivers. The code was just not clean enough.
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
codecs are not to be implemented
in kernel space. Basic decoding (such as stripping headers) is of course
allowed, but any operation on video data must be performed in userspace. I
think we all agree here.
By the way, the lack of a standard user-space framework f
you ! I'm always happy to hear that the hours I spent coding the driver
haven't been waisted :-)
> Many thanks to everyone who helped developing this driver,
You're welcome. Thank you for the report.
Laurent Pinchart
___
L
e able to do the work in a
> matter of hours.
And if you have any trouble, feel free to ask for support :-)
> > 3. Does anyone know of alternatives to Camorama that support
> > linux-uvcthat have functionality similar to
> > Camorama?
>
> Depending on what fea
n expect a patch soon.
Best regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
Hi Adrian,
> Just got to try your patch now. Still no joy though. I've attached the
> relevant pieces from the syslog.
Checkout the latest SVN version and tell me if it works better.
Cheers,
Laurent Pinchart
___
Linux-uvc-devel mailing lis
should not crash.
Could you please set the trace parameter to 127 ?
echo 127 > /sys/modules/uvcvideo/parameters/trace
Then try to plug your camera and let the kernel crash :-) I'll need the dmesg
output (you can leave out the syslog output) with all the uvcvideo
Hi Ioannis.
Thanks for the trace. Could you please apply the following patch and send me
the kernel log ? Please send me your compiled uvcvideo.ko module as well.
Thanks.
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel
Patch attached :-)
Laurent
Index: uvc_v4l2.c
===
--- uvc_v4l2.c (revision 76)
+++ uvc_v4l2.c (working copy)
@@ -205,6 +205,8 @@
struct uvc_format *format = video->streaming->cur_format;
struct uvc_frame *frame = video->streaming->
Hi Ioannis,
could you please send me the output of 'lsusb -v' as well ? You will need
usbutils 0.72 or newer (the CVS version should do as well).
Thanks
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlio
nis Nousias for letting me crash his kernel many times
until the remaining bugs were sorted out.
Cheers,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
Hi Paul
> It's a great news to have more devices supported! BTW, does Creative Live!
> Optia exhibit similar USB control request problems as Logitech cameras?
So far, no. But I haven't conducted any stress-test.
Regards,
Laurent Pinchart
_
ss-test program ? :-)
> Any chance for raw Bayer support on Optia?
I don't know yet. I contacted Creative to have more information about the
extension units. I don't know if the camera supports Bayer mode.
Cheers,
Laurent Pinchart
_
;m not looking for any sort or precise commitment at this point, I
> only would like to know if this is an option should I, or actually the
> company I work for, need a particular UVC Camera Model to function in the
> near future.
Yes, that's definitely an option. I'd be
ork as well with my Orbit as it does on
> x86_64.
>
> I say 'as well' because there are a few errors (attached) - it takes a
> couple of goes to capture an image. Is it possible this is the firmware
> bug that affects certain system
neric, less confusing
name, but that's life :-)
I still plan to submit the Linux UVC driver for inclusion in the kernel, as I
believe it is now ready. I need to get a few controls standardised at the
V4L2 level first, and that hasn't been easy so far. I keep trying tho
any sort or precise commitment at this point, I
> > > only would like to know if this is an option should I, or actually the
> > > company I work for, need a particular UVC Camera Model to function in
> > > the near future.
> >
> > Yes, that's definitely an
simply fail without a specific error code. Mind
> you, I don't know if these controls are suppose to change the settings
> of the camera or if they only have local effects.
Cheers,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
s mailing list is about the Linux UVC driver,
which supports the Logitech Fusion webcam, and as the qc-usb driver doesn't
support the Logitech Fusion webcam, what are you trying to do ? :-)
Cheers,
Laurent Pinchart
___
Linux-uvc-devel mailing list
make[1]: Entering directory `/usr/src/linux-2.6.19.1'
> INSTALL /home/antonio/trunk/uvcvideo.ko
> DEPMOD 2.6.19.1
> make[1]: Leaving directory `/usr/src/linux-2.6.19.1'
> depmod -ae
> [EMAIL PROTECTED]:/home/antonio/trunk#
Best Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
ries isn't related to the frame format, so it isn't a problem
in itself. However, the camera supports MJPEG only. It can't stream YUV
images.
Best regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
way, the button on the camera is found and I get messages in
> dmesg when it's pressed. The mic works well too.
So the only working features are either unusable (the button currently logs a
message but doesn't do anything else) or out of the Linux UVC driver scope
(audio is handled by the USB audio driver). Nice :-)
Cheers,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
Hi Olivier,
> > Nice to know. The Apple iSight was high on the list of broken cams, but
> > it seems the Microsoft ones might beat it :-)
>
> any progress on the iSight support ? I will be happy to help by testing
> it. ;)
I haven't made any progress myself (as I don't own any Mac), and haven't h
to the
image buffer, stripping the headers. Something is probably wrong there.
Cheers,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
to the printk's would be enough).
Cheers,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
to delegate firmware loading to the user-space
fxload software, but Ronald would like to integrate it in the driver instead.
Nothing has been decided yet.
I would welcome a tool to extract the firmware from the driver and output it
in a file readable by fxload.
Cheers,
Laurent Pinchart
--- /dev
>
> [17182258.156000] uvcvideo: Found UVC 1.00 device Built-in iSight
> (05ac:8501)
>
> So, I suspect that the loading of the firmware is OK.
Could you send me the iSight USB descriptors (lsusb -v with usbutils 0.72 or
newer) ? Make sure you load the firmware first.
ull
proprietary webcam with each firmware release. The Linux UVC driver will have
to stop supporting this at some point. A nice alternative would be to write
an open-source firmware. Anyone interested ? :-)
Cheers,
Laurent Pinchart
___
Li
am and doesn't report any error, I'd have a look
at your udev configuration.
Best regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
stated, we need people
with technical knowledge on the subject to voice their opinion on the V4L
mailing list. This is the last step before submitting the driver for
inclusion in the mainline kernel.
Best regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
ueries in your syslog are a bug in the camera's
> USB chip. It was discussed at length in previous threads. Please have a
> look at:
> https://lists.berlios.de/pipermail/linux-uvc-devel/
>
> There are a few workarounds to be found in the list archive, but none of
&g
7;m looking for a way to emulate an V4L1
> device. Is there any way to do this with linux-uvc?
V4L2 provides a V4L1 compatibility layer. I haven't heard about anyone getting
it working with the UVC driver, so it will probably not be easy.
Best regards,
Laurent Pinchart
___
only reason why read() hasn't been implemented (yet) is that mmap() has
been implemented first, and there hasn't been any demand for read(). It's on
my todo list though.
poll() without read() makes sense, using VIDIOC_DQBUF.
Best regards,
Laurent Pinchart
method described by the V4L2 protocol.
> (VIDIOC_QUERYBUF fo istance).
I'm not sure what you mean there. poll() must not start video streaming when
using a streaming I/O method.
Best regards,
Laurent Pinchart
___
Linux-uvc-devel mailing li
roduct ID to the
driver was enough.
The USB descriptor below clearly advertises a USB Imaging device, not a USB
Video device. Unless there is a hidden, magical way to switch the device to
UVC mode, there's not much the Linux UVC driver can do.
Best regards,
Laurent Pinchart
> On 2/1/07
ing "right" but sheer luck. As the hardware has been
tested with Windows only, the problem has never been detected before devices
hit the market.
> Thanks for a very usable driver.
You're welcome. Future Logitech products should hopefully include a firm
> were accidentally marked as write-only, which explains the error. It's
> part of the patch that I mentioned, it should be fixed soon in the
> repository.
>
> > Yes luvcview used the step value.
>
> We'll post a message to the list
eport any error ?
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
nplug the camera. You might also try to use a
> virtual machine with Windows to initialize it.
Or better, try to find if the Windows driver stores the firmware in some kind
of readable form. The fxload utility can be used to load EZ-USB firmwares in
Linux.
Cheers,
Laurent Pinchart
__
n is available on
http://linux-uvc.berlios.de.
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
erived works, which would require
> far more work to be fixed.
I don't plan to make anonymous unions widespread in the driver. The two
anonymous unions have been made anonymous to make the code easier to read,
and not to mimic videodev2.h. I don't think they are an issue for inte
;s another problem.
Best regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
vcvideo: Trying format 0x59455247 (GREY): 176x144.
> uvcvideo: Unsupported format 0x59455247.
> uvcvideo: Trying format 0x59565955 (UYVY): 176x144.
> uvcvideo: Unsupported format 0x59565955.
> uvcvideo: Trying format 0x31384142 (BA81): 176x144.
> uvcvideo: Unsupported format 0x31384142.
Best regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
mappings ? Without PROT_WRITE,
user space applications can't write to the buffer. I haven't been able to
find any other implication.
Best regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lis
VIDIOC_STREAMON) should return -EINVAL
if "no buffers have been allocated (memory mapping) or enqueued (output)
yet.". The specification clearly states that the lack of queued *output*
buffers leads to -EINVAL. Having no queued input buffers shouldn't trigger
any error condition.
B
there are no enqueued
> output buffers, while VIDIOC_STREAMON has to succed in the same case for
> input buffers?
No, not really. It's a bit inconsistent. I don't see any technical reason to
force the user to enqueue buffers before calling STREAMON. Might be worth
asking on
und UVC 1.00 device (046d:08c2)
>
> This is the output of dmesg:
>
> Linux video capture interface: v2.00
> usbcore: registered new interface driver uvcvideo
> USB Video Class driver (v0.1.0)
>
> Does it means it does not get detected?
It seems so. Try to set the trace pa
gt;
> I am able to build the module, and modprobe it with no problems. But it
> fails to find the device. I know the webcam works, as I have used it fine
> under a windows dual-boot.
Could you set the trace parameter to 15 (modprobe uvcvideo trace=15) and post
the dmesg outp
lear the kernel log with dmesg -c
- Insert the module with modprobe uvcvideo trace=15
- Check the kernel log with dmesg to see if anything is wrong
- Plug in the webcam
- Check the kernel log again
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
he kernel log with dmesg -c
2. Insert the module with modprobe uvcvideo trace=15
3. Check the kernel log with dmesg to see if anything is wrong
4. Plug in the webcam
5. Check the kernel log again
Paste the whole dmesg output after 3. and 5.
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
ta'
[more errors]
I suspect your kernel to be heavily patched. There's something wrong with the
V4L2 support. How can I have a look at the sources ?
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
kernel is heavily patched, so you might need a Linux
PPC/PS3 developer to look into the issue.
Cheers,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
is wrong
> > 4- Plug in the webcam
> > 5- Check the kernel log again
> >
> > Laurent Pinchart
>
> Doing 3 after 1 and 2, i get the same that i got before with
> /var/log/dmesg. How do I plug in an integrated camera?
Hmmm... that might be a bit difficult, right :-)
>
allocate buffers, set the video format, ...), and
start streaming when you need an image. You can stop streaming right after
getting the data, and start again later when required by your application.
> Perhaps I should join the v4l dev mailing list and see what their
> thoughts are. Your
interface: v2.00
> [ 771.192000] usbcore: registered new interface driver uvcvideo
> [ 771.192000] USB Video Class driver (v0.1.0-c)
modprobe doesn't report any error if the driver is already loaded. Try to
unload the driver (rmmod uvcvideo), cle
with dmesg to see if anything is wrong
> > > 4- Plug in the webcam
> > > 5- Check the kernel log again
> > >
> > > Laurent Pinchart
> >
> > Doing 3 after 1 and 2, i get the same that i got before with
> > /var/log/dmesg. How do I plug in an inte
l build process, which calls the Makefile back from kbuild. This seems
to work fine, why does it fail with openSuse ?
> The 10.2 repository is here, go up for other versions:
> http://software.opensuse.org/download/drivers:/webcam/openSUSE_10.2/
Best regards,
Laurent Pinchart
___
race=15
> > > > > 3- Check the kernel log with dmesg to see if anything is wrong
> > > > > 4- Plug in the webcam
> > > > > 5- Check the kernel log again
> > > > >
> > > > > Laurent Pinchart
> > > >
> > >
501 - 600 of 1880 matches
Mail list logo
