patch that
checks the idVendor and idProduct values directly (after converting them from
little-endian to cpu-endian, which was forgotten in your first patch).
For the record, here's the patch.
# HG changeset patch
# User Laurent Pinchart
# Date 1260408681
On Friday 04 December 2009 02:02:53 Melchior FRANZ wrote:
> * Laurent Pinchart -- Thursday 03 December 2009:
> > On Wednesday 02 December 2009 18:10:56 Melchior FRANZ wrote:
> > > I didn't find a reserved keysym for webcam snapshot buttons.
> >
> > What about XF
stalled the uvcvideo driver from
source, but that the v4l core modules (such as videodev.ko) are still the one
bundled with your default kernel. You need to install all the modules from the
source tree.
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
er around here.
>
> All the UVC cameras actually being sold in stores in my area were not in
> the list and most of them were Genius.
Thanks for the report. I've updated the supported devices list on the website.
--
Regards,
Laurent Pinchart
__
eived any test report for it
though, but I've successfully tested the C600 and Portable C200.
Could you please send me the output of
lsusb -v -d 046d:0804
with your camera plugged in ? Thanks.
--
Regards,
Laurent Pinchart
___
Linux-uvc-d
worth trying so that users with only hub terminated USB ports can use
> uvcvideo.
Thanks a lot for the information. You forgot the "lsusb -v -d 046d:0804"
output though ;-)
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
st UVC webcam
should be supported out of the box by the uvcvideo driver even if they're not
listed on the driver's website.
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/
Hi Alessandro,
On Monday 07 December 2009 17:12:18 Alessandro Bonometti wrote:
> On Thursday 03 December 2009 20:29:24 Laurent Pinchart wrote:
> > > I bought a Microsoft LifeCam NX-6000 which should be supported by UVC
> > > (http://linux-uvc.berlios.de/#devices). The came
sn't even have a chance to bring up the UVC driver.
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
enumeration seemed successful, however
> I did get only one device on the host (/dev/vide0). I hope for two streaming
> interfaces you should get two devices on the host
> isn't it?
I suspect that you're trying to use two different streaming interfaces with
the same USB output t
6b57031, *pte=0000,*ppte=0000
> internal error:Oops:17[#1]
> Modules linked in : uvcvideo
> .so many lines and last line is
> Sementation fault
>
> If any one knows the solution for this problem Please guide me
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
device descriptor read/8, error 2
>
> I think the USB controller couldn't find the right dirver, so it
> display these error message.
No, those messages indicate that the host can't read the device descriptor.
That's a very low-level error completely unrelate
ideo driver matches against the device using
interface class and subclass, not the device vendor and product IDs.
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
Hi Alessandro,
On Saturday 19 December 2009 15:04:32 Alessandro Bonometti wrote:
> On Sunday 13 December 2009 13:23:49 Laurent Pinchart wrote:
> > It might be possible to work around the problem. Could you try to load the
> > driver with quirks=0x102 and timeout=3000 ? If that h
vcvideo: Failed to initialize the device (-5).
> usbcore: registered new interface driver uvcvideo
Ouch. That seems to be a very buggy webcam. Could you please try to load the
uvcvideo driver with quirks=0x100 and see if it helps ?
--
Regars,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
rease
> > UVC_CTRL_CONTROL_TIMEOUT or if it would be enough something between 3000
> > and 5000 for UVC_CTRL_STREAMING_TIMEOUT as I did not have more time to
> > test it.
> >
> > So maybe 5000 would be a good default for UVC_CTRL_STREAMING_TIMEOUT?
Could be, but I'
ith the smallest bandwidth big enough
to accommodate the device needs, not just the first one.
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
eliminating clock
drift between the camera and system clocks. That's what the PTS/SCR fields are
for.
> I can't tell when a device will use it's own counter or when it'll echo the
> USB SOF frame number.
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
missing something here,
> suggestions?
UVC doesn't provide any support for that. You can't provide both isochronous
and bulk transfers for the main video stream in a single configuration.
However, you could have two configurations, one with isochronous transfers a
nd me the output of
lsusb -v -d 0c45:62f1
with your webcam plugged in ?
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
quested recently in the mailing list.
Thanks for the report and the lsusb output. No need to be sorry, that's
exactly what I wanted :-)
I've updated the supported devices list on the website.
--
Regards,
Laurent Pinchart
___
Linux-uv
LifeCam VX-800
> (/dev/video0) and test it to see myself in the video.
Thanks for the report.
Could you please confirm that the device didn't work without the patch ? The
uvcvideo driver should have printed an error message in the kernel log
(dmesg).
> Thanks to all the developers fo
you please send me the output of
lsusb -v -d 064e:d101
using usbutils 0.72 or newer (0.73+ preferred) ? I'll then update the
supported devices list on the uvcvideo driver's website.
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mai
s 0.72 or newer (0.73+ preferred) ? I'll then update the
supported devices list on the uvcvideo driver's website.
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
allocation when
> using mencoder with --v4l2-chroma=mjpeg ; but unfortunately the machine is
> remote and just died...
>
> At any rate, if anyone can verify that this is the (in)correct behavior of
> uvcvideo i would appreciate it (but I am under the impression it is not
> supposed
6428)
>
> So it should be listed under this name as well in your list.
Thanks for the report. Website updated.
> Thanks a lot for your support.
You're welcome.
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-
TREAMING_TIMEOUT to 5000, I left UVC_CTRL_CONTROL_TIMEOUT at
> 300. And everything seems to work.
Thanks. I'll increase the streaming timeout value to 5000.
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.ber
n when uvc_disconnect is
called.
The best solution might be a mix between those two: ignore -EPROTO/-EILSEQ/-
ETIME errors up to a maximum number (the threshold could be the total number
or errors, or the number of consecutive errors), and cancel the queues anyway
when the device is disconnected. What's your opinion ?
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
Hi Antonio,
On Friday 08 January 2010 20:47:21 Antonio C. Costantino wrote:
> In data martedì 27 ottobre 2009 11:16:47, Laurent Pinchart ha scritto:
> > On Monday 26 October 2009 13:05:58 Antonio C. Costantino wrote:
> > > Hi all,
> > >
> > > I'm pre
th usage. In that case it will still ask for
a high bandwidth, and streaming from two devices simultaneously will fail.
The other option is to use MJPEG instead of YUV. That will reduce the
bandwidth requirements drastically, but you will have to decompress the MJPEG
stream
f lsusb -v for your webcam.
>
> I'm sending it as attachment (does it look "good"?)
That's exactly what I needed, thanks. I'll update the list as soon as Berlios
becomes responsive again.
--
Regards,
Laurent Pinchart
___
to the kernel log when running mencoder in MJPEG mode ?
> Once again, I'd like to thank you for your time.
You're really welcome.
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.b
:49:00 localhost kernel:
> [12132.844729] input: USB2.0 Camera as
> /devices/pci:00/:00:1d.1/usb3/3-1/3-1.1/3-1.1:1.0/input/input13
As stated by the log, you should connect the camera to a high speed hub :-)
Your hub is probably running at full speed only (12 Mb/s), and the camera
s
t means the camera doesn't advertise any standard focus control. It could
still implement a standard focus control but not advertise it, or implement a
vendor-specific focus control through an extension unit.
--
Regards,
Laurent Pinchart
___
ath: /dev/video1
> Stream settings:
> Frame format: YUYV (MJPG is not supported by device)
> Frame size: 640x480
> Frame rate: 30 fps
> Unable to start capture: No space left on device
> Error grabbing
> Cleanup done. Exiting ..
t;back-engeneering" si besoin . (il semble
> que ce soit le même chip/ID sur la webcam de pas mal de portables)
Thanks for your offer, but I'm not involved with USB camera drivers beside
uvcvideo. You could try contacting the linux-media mailing
ransferSize;
in uvc_video.c by all of the above bandwidths in turn to see which one work in
1280x720 (MJPEG) ?
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
l log when you plug the camera to
your system.
If the camera isn't UVC compatible I'm afraid I won't be able to help you.
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
0460] usbcore: registered new interface driv
That looks fine, what's your issue ?
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
1b3b:2951 MSI StarCam 370i" is
> compatible with the uvc driver.
>
> # lsusb -v -d 1b3b:2937 | grep "14 Video"
> Doesn't print anything.
That means the camera isn't UVC compatible, so it won't be supported by the
uvcvideo driver.
Your webcam can still be
..60f40d9 100644
--- a/drivers/media/video/uvc/uvc_ctrl.c
+++ b/drivers/media/video/uvc/uvc_ctrl.c
@@ -1453,6 +1453,7 @@ uvc_ctrl_prune_entity(struct uvc_device *dev, struct
uvc_entity *entity)
struct usb_device_id id;
u8 index;
} blacklist[] = {
+ { { USB_DEVICE(0x
Hi Celejar,
On Sunday 31 January 2010 01:59:53 Celejar wrote:
> On Fri, 15 Jan 2010 01:32:03 +0100
> Laurent Pinchart wrote:
> > On Wednesday 13 January 2010 00:12:27 Celejar wrote:
> > > Hi,
>
> ...
>
> > > Thanks for your work on this project!
> &
crophone (ALSA). Not working only camera buttons, but who
> care of this :)
> Thanks to all of you who worked on GNU/Linux UVC support!
Thanks for the report.
Could you please send me the output of
lsusb -v -d 0458:705d
I will then update the supported devices list.
--
me would be appreciated.
Have you tried using the driver without adding the USB VID:PID to uvc_driver.c
? What happens then ?
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
vc_streaming_control
structure.
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
Hi Bram,
On Friday 05 February 2010 14:30:32 Bram Senders wrote:
> Hi Laurent,
>
> Thanks for your help so far!
>
> On Wed, Feb 3, 2010 at 1:23 AM, Laurent Pinchart
>
> wrote:
> > Hi Bram,
> >
> > On Tuesday 26 January 2010 16:12:02 Bram Senders wrote:
35xx processor
(in that case you could try capturing in MJPEG instead of YUYV) or a board
routing issue.
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
ge
> table" through the kernel log. Maybe it helps to get a clue.
Could you send me a copy of the kernel log ?
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
ts.html" for
> getting this errors (it needs 0.01 second to study all uvc driver :D).
Thank you for testing the uvcvideo driver and helping improving its quality.
I've checked the report you've attached to your e-mail, and it turned out that
the problems were false posit
drivers for this device.
If the camera isn't a video class device it won't work with the uvcvideo
driver. The gspca driver supports many webcams, you might have more luck with
it.
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing l
eo
driver selecting an alternate setting with a too high bandwidth (which is
allowed, but not very optimum). Your device has a single alternate setting for
the streaming interface, so it doesn't seem to be the same issue.
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
Hi Bram,
On Tuesday 16 February 2010 11:19:28 Bram Senders wrote:
> Hey Laurent,
>
> On Wed, Feb 10, 2010 at 1:24 AM, Laurent Pinchart
>
> wrote:
> > I think I made a small mistake, could you replace the index 4 by 9 in the
> > patch I've sent you ?
>
>
2d Z-Star Microelectronics Corp. Vega USB 2.0
> Camera And works!
>
> The product link:
> http://www.techsolo.net/site/product.php?lang=en&do=show&product_id=224&&cl
> ass_id=53
Thanks for the report. The device was already listed, albeit not under that
n
Hi Bram,
On Thursday 18 February 2010 23:43:59 Bram Senders wrote:
> Hey Laurent,
>
> On Thu, Feb 18, 2010 at 11:06 PM, Laurent Pinchart
>
> wrote:
> >> wrote:
> >> > I think I made a small mistake, could you replace the index 4 by 9 in
> >> >
C_DQBUF)
>
> Cameras are Microsoft NX-3000 and Genius eFace 1325R
>
> Does anyone have an idea, or need more info?
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
blem on the linux-media mailing
list, someone might be able to help you. You should post the lsusb -v output
for your camera in the report.
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists
ideo and is more
recent.
> When I do 'make install' instead of insmod I get the same old error again
> # modprobe vloopback
> FATAL: Error inserting vloopback
> (/lib/modules/2.6.26-2-686/kernel/drivers/misc/vloopback.ko): Unknown
> symbol in module, or unknown paramet
the cam is
> working fine!!!
Thanks a lot for the information. I will fix the driver to set the quirk
automatically and update the supported devices list. Could you please tell me
in which notebook model that webcam can be found ?
--
Regards,
Laurent Pinchart
_
D 046d:08ca Logitech, Inc. Mic (Fusion)
>
> [I--] [ ~] media-libs/gstreamer-0.10.25 (0.10) (tried 0.10.24 as well)
>
> # zcat /proc/config.gz | grep V4L
> CONFIG_VIDEO_V4L2_COMMON=y
> # CONFIG_VIDEO_ALLOW_V4L1 is not set
> # CONFIG_VIDEO_V4L1_COMP
ks parameter to 0x100 when loading the
uvcvideo driver ?
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
#x27;s a safe first guess though.
The next step is to configure the uvcvideo driver with the extension unit
controls information using uvcdynctrl and the XML file you've created. You
will then be able to access the controls through the V4L2 API.
--
Regards,
Laurent Pinchart
_
e? It seems that the software that
> follows the webcam supports this (you click on the part of the image that
> you want in focus).
It should be possible yes. Your camera has two focus controls (auto-focus and
absolute focus) that are accessible through the V4L2_C
if
they do, that's done through a standard UVC control, mapped to the
V4L2_CID_EXPOSURE_AUTO control.
> How could I do it?
There's a few command line tools that let you modify controls, as well as GUI
applications. v4l2-ctl is a good candidate as a low-level command line tool.
Hi Michał,
On Wednesday 10 March 2010 22:27:20 Michał Górny wrote:
> On Thu, 4 Mar 2010 11:31:55 +0100 Laurent Pinchart wrote:
> > I don't have much experience with Windows, so I can't advice for a
> > test application that would allow you to configure the resolution.
>
at correct?
Yes it will. Of course, if you store the frames in a container that expects a
constant frame rate (let's say an AVI file, I think those don't support
variable frame rates) then the playback might take less than 10 seconds.
--
Regards,
Laurent Pinchart
___
You will need to
fix the application to support the YUYV format used by the camera.
libv4lconvert might help if you need transcoding.
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
ver uvcvideo
>
> Cheese and mercury doesn't recognize the webcam.
Do they print any error message ? Does the driver print messages to the kernel
log when you start cheese or mercury ?
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mail
Hi,
On Thursday 11 March 2010 22:05:30 Per Thomas Jahr wrote:
> On Tue, 2010-03-09 at 12:51 +0100, Laurent Pinchart wrote:
> > On Monday 01 March 2010 11:46:06 Per Thomas Jahr wrote:
> > > I just wanted to report that the IPEVO Point 2 View webcam works fine
> > > wi
mplete (overflow).
> uvcvideo: Dropping payload (out of sync).
> uvcvideo: Dropping payload (out of sync).
> uvcvideo: Dropping payload (out of sync).
> uvcvideo: Dropping payload (out of sync).
> uvcvideo: Dropping payload (out of sync).
--
Regards,
Laurent Pinchart
_
vices based on their class and subclass, not on their
vendor and product ID. UVC compatible cameras should be supported out of the
box without any need to modify the driver.
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@li
you check if the driver prints anything to the kernel log (use the dmesg
command) when you get the above error with GStreamer ?
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
e:075d model (there could be more than
one Microsoft Lifecam Cinema). That webcam exposes an auto-focus control which
you can access through the V4L2_CID_FOCUS_AUTO V4L2 control.
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-
t be able to help you. You might have more luck
with the gspca driver.
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
ation about webcam.
[snip]
Thanks a lot for the report. I'll update the supported devices list.
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
config <--- disable fireDTV or you will end up
> with errors when building
Quick side note, I don't think sudo is required for make menuconfig.
> make
> sudo make install
> sudo make unload
> sudo modprobe uvcvideo
--
Regards,
Laurent Pinchart
__
can
> only choose one format, no matter on USB1.1 or USB2.0.
It just means that it only exposes a single format (YUYV) on USB 2.0 for
whatever reason the vendor came up with during development. The camera
otherwise works.
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
> [ 8124.355069] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
lable.
If the webcam reports YUYV only, it probably means it doesn't support MJPEG.
It's not uncommon for vendors to ship different products under the same
VID:PID, and your model is probably restricted to YUYV.
> There is any workaroud about this?
--
Regards,
Laurent Pinchart
__
also report the output of
lsusb -v -d 17ef:480f
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
Dropping payload (out of sync).
> >> uvcvideo: Dropping payload (out of sync).
> >> uvcvideo: Dropping payload (out of sync).
> >> uvcvideo: Dropping payload (out of sync).
>
> BTW, if I look at the correct place in the driver, why uvc doesn't
> support r/w io and userptr?
Because nobody bothered to implement that :-)
read/write support is slow, and I'm not sure it will be implemented. I got a
patch for userptr support, I need to clean and submit it.
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
I can fix that, could you please send me the output of 'lsusb -v' for your
webcam ?
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
odule parameter
>
> nevertheless nothing changed this behaviour.
The -71 error often indicates bad hardware, including buggy firmwares or bad
cables. Try plugging your webcam into another port, changing the external hub
(if any) or hub cables. It would al
r webcam isn't UVC compatible. It's then
not supported by the uvcvideo driver, you're probably using another driver.
I maintain the uvcvideo driver only, you will need to contact your driver
mailing list or author for support.
--
Regards,
Laurent Pinchart
Hi,
On Monday 12 April 2010 05:36:49 Omari Stephens wrote:
> On 04/11/2010 10:36 AM, Laurent Pinchart wrote:
> > On Thursday 08 April 2010 15:13:43 Kurt Rosenfeld wrote:
> >> Hello,
> >>
> >> The UVC camera in the Lenovo T510 works if this small modif
ting purpose.
> [ 8583.592569] uvcvideo: Please report required quirks to the
> linux-uvc-devel mailing list
The lsusb output you posted on pastebin.com is for device 17dc:0200, not
17dc:0202.
--
Regards,
Laurent Pinchart
___
Linux-uvc-deve
VC_GUID_FORMAT_BY8 \
{ 'B', 'Y', '8', ' ', 0x00, 0x00, 0x10, 0x00, \
0x80, 0x00, 0x00, 0xaa, 0x00, 0x38, 0x9b, 0x71}
-
/*
* Driver specific constants.
*/
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
; Pixel Format: 'YUYV'
> Name: YUV 4:2:2 (YUYV)
>
> Index : 1
> Type: Video Capture
> Pixel Format: 'Y16 '
> Name: Greyscale (16-bit)
Great. I'll commit the patch. Could you please give
form would use
more USB bandwidth than available. This is usually the case when you capture
uncompressed high-resolution video from two webcams simultaneously.
You could try to select a smaller frame size, or use a compressed format if
your cameras support that (many
s printing messages to the kernel log.
You can get to the USB interface in sysfs through the
/sys/class/video4linux/videoX/device symlink. The parent of that device is the
USB device.
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing
w does your camera fail to work exactly ?
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
u want I can
> compile/patch code from source to figure this out.
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
ill let
you update the v4l-dvb subsystem completely (highly recommended for end
users).
> Note however that uvc is integrated in the kernel since 2.6.27, so if
> you are using a recent kernel version you really don't need to build
> it from source.
--
ng other information, the
formats supported by the device. In this case there's a single format
descriptor, of subtype 4 (FORMAT_UNCOMPRESSED). Devices supporting MJPEG have
a subtype 6 descriptor (in addition to the FORMAT_UNCOMPRESSED descriptor if
they support uncompressed formats).
Th
e, there's no non-volatile memory to store the controls in any of
the consumer webcams I know of.
> You would have to unplug the camera to loose the settings.
> This is not always a good think, sometimes the camera may crash,
> meaning that you must physically unplug i
as and handle them in a round-
robin way. When one of the cameras completes a frame, you will have to stop
submitting URBs for it, wait until all URBs have completed, and submit the
URBs for the next camera in the list.
> I don't think I can write them all out to storage fast enough anyway.
> (I can come close to keeping up with 10 fps on 8 cameras though.)
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
d bandwidth.
That might be the real culprit. Maybe the camera is simply requesting too much
bandwidth compared to its real requirements.
Can you check whether the video streaming interface has multiple alternate
settings ? If so, which one does the
>
> http://www.mjmwired.net/kernel/Documentation/leds-class.txt
I've thought about it, but that would be difficult. The uvcvideo driver has no
idead that the control actually controls a LED. Having access to that
information isn't straightforward, as it's not reported by the device.
uner are not either, any suggestions or
> info would be welcome.
That's out of my area of expertize, sorry :-)
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
irst case why don't
you just use lsusb ?
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
answer to this - and having a few
> pointers/explanations from the UVC implementors might help here !
>
> I saw the other forums and their approach - and somebody proposed there
--
Regards,
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
1 - 100 of 1880 matches
Mail list logo
