V4L2-library

v4l2-library@linuxtv.org

81 discussions

frontend mac adress
by onur sentürk 25 Feb '10

25 Feb '10

Hi, i need to know the mac adress of a dvb frontend (pci number would also be helpfull). I found no way to identify a dvb device by its frontend. I looked at the dvb api code, and then i patched dvb_frontend.c, and frontend.h for my needs. Below are the changes I made. But the code don't works. I don't get the information I need. My devices: Philips TDA10046H DVB-T Conexant CX24123/CX24109 Conexant CX24123/CX24109 Montage Technology DS3000/TS2020 -> works The value dvbdev->adapter->proposed_mac seems to be empty, for some cards. But on driver load I can see a mac address for every dvb device I have. The mac address for these cards are outputted in function: void tveeprom_hauppauge_analog(...). Maybe someone can help me. Maybe there is another way of determining a dvb frontend by PCI Bus or something. Identifying dvb devices can be very important on some situations. Regards, onur ---------------------------------------------------------- dvb_frontend.c: static int dvb_frontend_ioctl_legacy(struct inode *inode, struct file *file, unsigned int cmd, void *parg) { struct dvb_device *dvbdev = file->private_data; struct dvb_frontend *fe = dvbdev->priv; struct dvb_frontend_private *fepriv = fe->frontend_priv; int cb_err, err = -EOPNOTSUPP; // FE_GET_PROPOSEDMAC if (cmd == FE_GET_PROPOSEDMAC) { struct dvb_proposed_mac* info = parg; memcpy(info, dvbdev->adapter->proposed_mac, sizeof(struct dvb_proposed_mac)); //memcpy(info->proposed_mac, dvbdev->adapter->proposed_mac, 6); return 0; } // FE_GET_PROPOSEDMAC ---------------------------------------------------------- frontend.h: ... // FE_GET_PROPOSEDMAC struct dvb_proposed_mac { __u8 proposed_mac [6]; }; #define FE_GET_PROPOSEDMAC _IOR('o', 84, struct dvb_proposed_mac) // FE_GET_PROPOSEDMAC #endif /*_DVBFRONTEND_H_*/

1 0

v4l2-apps compilation error
by roman chechulin 20 Jan '10

20 Jan '10

Hello, i have problem to compile the v4l2-apps from http://linuxtv.org/hg/v4l-dvb. I have loaded source archive of v4l-dvb (v4l-dvb-e4429a1b736c.tar.gz) I have unpacked archive in directory /home/u/pkgSources/v4l-dvb-e4429a1b736c, then have executed commands as root user: cd /home/u/pkgSources/v4l-dvb-e4429a1b736c/v4l2-apps [root@host-15 v4l2-apps]# make .... make[1]: Entering directory `/home/u/pkgSourceDir/v4l-dvb-e4429a1b736c/v4l2-apps/util' g++ -I../include -D_GNU_SOURCE -lm v4l2-ctl.cpp -o v4l2-ctl v4l2-ctl.cpp: In function ‘void printjpegcomp(const v4l2_jpegcompression&)’: v4l2-ctl.cpp:920: warning: format ‘%08lx’ expects type ‘long unsigned int’, but argument 2 has type ‘unsigned int’ g++ -I../include -D_GNU_SOURCE -c -o v4l2-dbg.o v4l2-dbg.cpp g++ v4l2-dbg.o v4l2-chipids.o -o v4l2-dbg g++ -I../include -D_GNU_SOURCE -lm v4l2-compliance.cpp -o v4l2-compliance CC ivtv-ctl ivtv-ctl.c: In function ‘dowrite’: ivtv-ctl.c:247: warning: format not a string literal and no format arguments In file included from /usr/include/stdio.h:912, from ivtv-ctl.c:25: In function ‘snprintf’, inlined from ‘pts_to_string’ at ivtv-ctl.c:184, inlined from ‘main’ at ivtv-ctl.c:512: /usr/include/bits/stdio2.h:65: error: call to __builtin___snprintf_chk will always overflow destination buffer make[1]: *** [ivtv-ctl] Error 1 make[1]: Leaving directory `/home/u/pkgSourceDir/v4l-dvb-e4429a1b736c/v4l2-apps/util' make: *** [all] Error 2 Compilation has stopped with error. [root@host-15 v4l2-apps]# uname -r 2.6.30-std-def-alt15 I use ALT Linux 5.0, but on Ubuntu 9.10 v4l2-apps has compiled successful. Somebody can prompt in what there can be a problem?

3 2

Chicony 04f2:b106 webcam vertically flipped in skype but not ekiga
by Florent Cayré 18 May '09

18 May '09

Hi all, Installing the newer v4l drivers from hg repo solved my webcam video being vertically flipped in ekiga, but not in skype, which I can not explain, as skype image seems sensible to guvcview settings (seen with guvcview --control_only). Do you have a probable explanation even if skype is non free code (I am forced to use it, working in a changing network environment, not suitable for SIP-based solutions)? Could libv4l help me to solve this problem by forcing vflip (through a hard coded patch at first, ultimately an environment variable or so, even if it is not clean enough to be included in the lib official code)? I have development skills although I do not know much about driver-level development. If you show me the way to go I can probably try a few things and hopefully get a simple solution working, at least for me, perhaps for others too... Thanks in advance, Regards, Florent Cayré. -- Ce message est la propriété de SecondWeb et peut contenir des informations confidentielles. Si vous n'êtes pas le destinataire désigné, nous vous remercions de bien vouloir nous en aviser immédiatement et de nous retourner ce message ou de le détruire, sans faire un quelconque usage de son contenu, ni le communiquer ou le diffuser, ni en prendre copie, électronique ou non. This message is the property of SecondWeb and may contain confidential information. If you are not the designated recipient, please notify us immediately and return the message to us or destroy it, without making any use whatsoever of the contents thereof. Furthermore you should not forward or copy the message by electronic or other means.

3 8

Re: [V4l2-library] proposal for evade bugs in libv4l
by Hans de Goede 15 Nov '08

15 Nov '08

Lukáš Karas wrote: >> Erm, I've successfully tested skype with the new gspca and libv4l with >> various webcams, that works fine without any if your hacks. Perhaps it >> would help if you would explain what you are seeing, what cam you are using >> and if you could attach a libv4l logfile of this. >> >> To make a log file (with an unpatched libv4l please) do: >> LIBV4L2_LOG_FILENAME=/tmp/log skype >> >> And then try to use the cam in skype, after exiting skype again attach >> /tmp/log. >> >> Regards, >> >> Hans > > Ok, of course. I have kernel 2.6.27-rc8, architecture x86_64, newest > gspca_m5602 driver, Skype version 2.0.0.27 and 2.0.0.72. > My camera id is 0402:5602 (lsusb). > > Own driver support only BA81 pixelformat with resolution 640x480. Ah only a resolution of 640x480, yes that will make skype unhappy, I'm amazed it does work with your, return -EINVAL when we do not support the pixelformat, workaround. Is skype showing the whole picture, or only the upper left corner of the picture with your workaround ? Anyways attached is a patch which will work around this in a different (IMHO less ugly) way. It actually removes a number of lines of code. Can you give this one a try please. Note with this patch skype will only show the middle 320x240 of the webcam picture. This could be fixed by checking if dest_width < 2 * src_width in v4lconvert_crop() from libv4lconvert/crop.c And if this is the case call special (to be written) versions of v4lconvert_crop_rgbbgr24() v4lconvert_crop_yuv420(). I would be very happy to take a patch doing this! Regards, Hans p.s. I'm really sorry I'm being a PITA with regards to taking patches, it is just that having a lib sitting between v4l-apps and devices open ups lots of posibilities and everyone seems to want to put everything including the kitchensync into libv4l. This was not how libv4l was envisioned at first, I'm fine with expanding what it does, but I want to be a bit careful as to not turn it into a big pile of spaghetti. I'll make some time the next couple of days to take a look at your whitebalance patches and write a proposal for a kernel driver <-> userspace API for finding out if a cam needs software whitebalancing or not (I don't want to add it unconditionally to all v4l devices). diff -r 7415d367a87a v4l2-apps/lib/libv4l/libv4lconvert/libv4lconvert.c --- a/v4l2-apps/lib/libv4l/libv4lconvert/libv4lconvert.c Tue Nov 04 10:33:55 2008 +0100 +++ b/v4l2-apps/lib/libv4l/libv4lconvert/libv4lconvert.c Wed Nov 12 09:59:01 2008 +0100 @@ -268,29 +268,26 @@ return result; } - /* In case of a non exact resolution match, see if this is a resolution we - can support by cropping a slightly larger resolution to give the app - exactly what it asked for */ + /* In case of a non exact resolution match, see if this is a well known + resolution some apps are hardcoded too and try to give the app what it + asked for by cropping a larger resolution */ if (try_dest.fmt.pix.width != desired_width || try_dest.fmt.pix.height != desired_height) { for (i = 0; i < ARRAY_SIZE(v4lconvert_crop_res); i++) { if (v4lconvert_crop_res[i][0] == desired_width && v4lconvert_crop_res[i][1] == desired_height) { - struct v4l2_format try2_dest, try2_src; + struct v4l2_format try2_src, try2_dest = *dest_fmt; + /* Note these are chosen so that cropping to vga res just works for vv6410 sensor cams, which have 356x292 and 180x148 */ - unsigned int max_width = desired_width * 113 / 100; - unsigned int max_height = desired_height * 124 / 100; - - try2_dest = *dest_fmt; - try2_dest.fmt.pix.width = max_width; - try2_dest.fmt.pix.height = max_height; + try2_dest.fmt.pix.width = desired_width * 113 / 100; + try2_dest.fmt.pix.height = desired_height * 124 / 100; result = v4lconvert_do_try_format(data, &try2_dest, &try2_src); if (result == 0 && try2_dest.fmt.pix.width >= desired_width && - try2_dest.fmt.pix.width <= max_width && + try2_dest.fmt.pix.width <= 2 * desired_width && try2_dest.fmt.pix.height >= desired_height && - try2_dest.fmt.pix.height <= max_height) { + try2_dest.fmt.pix.height <= 2 * desired_height) { /* Success! */ try2_dest.fmt.pix.width = desired_width; try2_dest.fmt.pix.height = desired_height;

2 2

gspca & libv4l & luvcview
by Thomas Kaiser 12 Nov '08

12 Nov '08

Hello Hans As you already know, I like to test gspca V2 & libv4l. I had big troubles to get the source from linuxtv.org working on my Ubuntu 8.04. But now it's working. And when the times go by, Ubuntu released 8.10. I upgrade to 8.10 on my "test Laptop". Here gspca v2 is already included. Thus, I decided to use the Ubuntu stock gspca V2 module to test at the beginning. gspca V2 is a V4L2 driver and therefor should work with a V4L2 frame grabber application. As far as I know the only formats which are allowed by V4L2 is MJPG and YUYV. When the cam cannot provide this format your libv4l is needed to convert from a vendor specific format to the known format of V4L2. So, I decided to use luvcview (which should be some reference implementation for a V4L2 grabber application?) to test my cams. I used following cam: Bus 002 Device 004: ID 041e:401c Creative Technology, Ltd WebCam NX [PD1110] because this one was working quite good in gspca V1 and this was the cam which got my attraction to work with webcams. It was my first one.... When I just run luvcview, I get: thomas@LAPI01:~$ luvcview -f yuv luvcview 0.2.4 SDL information: Video driver: x11 A window manager is available Device information: Device path: /dev/video0 Stream settings: ERROR: Requested frame format YUYV is not available and no fallback format was found. Init v4L2 failed !! exit fatal So, now it's time to use libv4l: thomas@LAPI01:~$ LD_PRELOAD=/usr/lib/libv4l/v4l2convert.so luvcview -f yuv luvcview 0.2.4 SDL information: Video driver: x11 A window manager is available Device information: Device path: /dev/video0 Stream settings: ERROR: Requested frame format YUYV is not available and no fallback format was found. Init v4L2 failed !! exit fatal Unfortunately, it looks that libv4l cant convert to any format luvcview knows. Lets check a v4l1 grabber: thomas@LAPI01:~$ LD_PRELOAD=/usr/lib/libv4l/v4l1compat.so gqcam -v /dev/video0 thomas@LAPI01:~$ No error messages and I got a picture :-) Long mail for 3 simple question: Why cant v4l2convert.so convert to YUYV? (Which should be V4L2 conform) Or I am wrong to use luvcview to test V4L2 webcams? Is there any other reference implementation for a V4L2 (webcam) grabber? Regards, Thomas PS: The cam is working in cheese, too. Looks like cheese is compiled against your lib :-) . I hope all application which deal with webcams will be soon including your libs!

3 4

proposal for evade bugs in libv4l
by Lukáš Karas 11 Nov '08

11 Nov '08

Hi Hans. I have proposal for way, how evade bugs in libv4l. Please see patch in attachment. For programs, there incorect process S_FMT results, we can set environment variable LIBV4L2_EVADE_BUGS. With these comands work mplayer fine: export LIBV4L2_EVADE_BUGS=1 export LIBV4L2_LOG_FILENAME=~/libv4l.log export LD_PRELOAD=~/lib/libv4l_test_64/lib/libv4l/v4l1compat.so export LD_LIBRARY_PATH=~/lib/libv4l_test_64/lib/libv4l/:~/lib/libv4l_test_64/lib/: mplayer tv:// -tv driver=v4l2:device=/dev/video0 -fps 30 By the way, I get green image in skype with version 0.5.3 (but I see move), with version 0.5.0 are colors fine in skype. Maybee is bug in crop method... Regards, Lukas

4 6

Announcing libv4l 0.4.1
by Hans de Goede 26 Aug '08

26 Aug '08

Hi All, Some assorted fixes, and support for Pixart cams JPEG's (which are non standard JPEG's) together with some gspca kernel changes this means that we now have working pac7302 and pac7311 webcams! Go grab the new release here http://people.atrpms.net/~hdegoede/libv4l-0.4.1.tar.gz Full list of changes: libv4l-0.4.1 ------------ * When the driver supports read() and we are not converting let the driver handle read() instead of emulating it with mmap mode * Fix errors and warnings when compiling with ICC (Gregor Jasny) * Add support to libv4lconvert for rotating images 90 (for Pixart 7302 cams) or 180 (Philips SPC200NC / Philips SPC300NC) degrees * Add support for Pixart custom JPEG format * Hide non public symbols (Gregor Jasny) * Fix and enable x86_64 asm jpeg decompress helper functions (Gregor Jasny) Regards, Hans

1 0

MS VX-3000 does not quite work
by Max Krasnyansky 09 Aug '08

09 Aug '08

VX-3000 is listed as supported by the kernel driver. But it looks like I need libv4l to properly support its video format. So I tried v4l2convert with Skype and the picture is very very dark. I mean I can see that it's kind of working but only very bright objects are visible. Tuning brightness controls makes no difference. I tried Ekiga too and got similar results. Any suggestions ? I'm using 0.4.0 version btw. Thanx Max

1 0

Announcing libv4l 0.3.8
by Hans de Goede 03 Aug '08

03 Aug '08

Hi All, I've installed a pci bttv tv card in my machine to test libv4l xawtv patches and I've found that libv4l was being to strict with the circumstances under which it allowed changing the fmt and changing between read / mmap mode. This new version fixes this: http://people.atrpms.net/~hdegoede/libv4l-0.4.0.tar.gz Full list of changes: libv4l-0.4.0 ------------ * Be more relaxed in our checks for mixing read and mmap access, we were being more strict in this then certain kernel drivers (bttv) making xawtv unhappy * With some drivers the buffers must be mapped before queuing, so when converting map the (real) buffers before calling the qbuf ioctl * Add support for conversion to RGB24 (before we only supported BGR24) based on a patch by Jean-Francois Moine * When the hardware supports a format natively prefer using the native version over converting from another supported format * Various Makefile and pkgconfig file improvements by Gregor Jasny (Debian) * Drop the appl-patches dir, all application patches are now available and tracked here: http://linuxtv.org/v4lwiki/index.php/Libv4l_Progress Regards, Hans

1 0

Announcing libv4l 0.3.8
by Hans de Goede 03 Aug '08

03 Aug '08

Hi All, Here is release 0.3.8: http://people.atrpms.net/~hdegoede/libv4l-0.3.8.tar.gz This release has the following changes (some small tweaks left and right for more to the spec behavior, none of this fixes any known bugs). libv4l-0.3.8 ------------ * work around wrong REQUEST_BUFFERS ioctl return code from certain drivers * add pkg-config (.pc) files for easier detection if libv4l is available * check capabilities for streaming, if the driver cannot do streaming don't insert ourselves between the application and the driver * intercept get capabilites and report read capability (which we always offer) * query buffer: indicate the mapping state of our (fake) buffer in the flags Regards, Hans

3 4

← Newer
1
2
3
4
5
6
7
8
9
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

V4L2-library