Quoting Joe Burks <joe-v4l@xxxxxxxxxxx>: > >The ibmcam driver produces BGR24 - this is almost the native format in > >many IBM/Xirlink cameras. > > > >It is gnomemeeting's responsibility to take one of standard formats and > >make use of it. xawtv, for example, does exactly that. > > I know from experience making my own driver work with everything that with > several applications (such as gnomemeeting), if they call VIDIOCSPICT with > a palette type you do not support and you do not return -EINVAL (saying, NO > you can't have that palette) they will NOT work. A cursory glance at the > drivers/usb/usbvideo.c seems to indicate that apps doing this speculative > palette request will not work with any minidriver unless the first palette > requested happens to be the native one of the hardware. I didn't think of that. Indeed, there is no validation of the palette code in VIDIOCSPICT. The palette checking code from VIDIOCMCAPTURE should be copied into VIDIOCSPICT as well. I'll try to do this in few days. Makes sense. Thanks, Dmitri -- > I get the following error messages at bootup, could anyone tell me > what they mean? > fcntl_setlk() called by process 51 (lpd) with broken flock() emulation They mean that you have not read the documentation when upgrading the kernel. (Seen on c.o.l.misc)
Attachment:
pgpZWt0giYbkr.pgp
Description: PGP signature