cpu load of webcam read out with omap3/beagleboard

2009-10-18 Thread Rath

Hi,

I have beagleboard with the OMAP3530 processor and I want to read a usb 
webcam out. But I only get usable results at 160x120 resolution.
I set the pixelformat to V4L2_PIX_FMT_RGB24 and the resolution to 
160x120. With these settings I get 30fps at 4% cpu load. But when I set 
the resolution to 320x240 or 640x480 the cpu load is at 98% and I get 
only 17 or 4fps. Also I get at 640x480 errors like libv4lconvert: Error 
decompressing JPEG: fill_nbits error: need 9 more bits.


Is this a normal behavior or is  there a way to fix  this?  I think the 
problem is the conversion from MJPEG to RGB, because when I set the 
pixelformat to MJPEG the cpu load is 1%.  But  I need RGB data for 
image processing.


I hope someone can help me.

Regards, Joern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[cron job] v4l-dvb daily build 2.6.22 and up: ERRORS, 2.6.16-2.6.21: ERRORS

2009-10-18 Thread Hans Verkuil
This message is generated daily by a cron job that builds v4l-dvb for
the kernels and architectures in the list below.

Results of the daily build of v4l-dvb:

date:Sun Oct 18 19:00:04 CEST 2009
path:http://www.linuxtv.org/hg/v4l-dvb
changeset:   13101:3919b17dc88e
gcc version: gcc (GCC) 4.3.1
hardware:x86_64
host os: 2.6.26

linux-2.6.22.19-armv5: OK
linux-2.6.23.12-armv5: OK
linux-2.6.24.7-armv5: OK
linux-2.6.25.11-armv5: OK
linux-2.6.26-armv5: OK
linux-2.6.27-armv5: OK
linux-2.6.28-armv5: OK
linux-2.6.29.1-armv5: OK
linux-2.6.30-armv5: OK
linux-2.6.31-armv5: OK
linux-2.6.32-rc3-armv5: ERRORS
linux-2.6.32-rc3-armv5-davinci: ERRORS
linux-2.6.27-armv5-ixp: ERRORS
linux-2.6.28-armv5-ixp: ERRORS
linux-2.6.29.1-armv5-ixp: ERRORS
linux-2.6.30-armv5-ixp: ERRORS
linux-2.6.31-armv5-ixp: ERRORS
linux-2.6.32-rc3-armv5-ixp: ERRORS
linux-2.6.28-armv5-omap2: OK
linux-2.6.29.1-armv5-omap2: OK
linux-2.6.30-armv5-omap2: OK
linux-2.6.31-armv5-omap2: ERRORS
linux-2.6.32-rc3-armv5-omap2: ERRORS
linux-2.6.22.19-i686: ERRORS
linux-2.6.23.12-i686: ERRORS
linux-2.6.24.7-i686: ERRORS
linux-2.6.25.11-i686: ERRORS
linux-2.6.26-i686: OK
linux-2.6.27-i686: OK
linux-2.6.28-i686: OK
linux-2.6.29.1-i686: WARNINGS
linux-2.6.30-i686: WARNINGS
linux-2.6.31-i686: WARNINGS
linux-2.6.32-rc3-i686: ERRORS
linux-2.6.23.12-m32r: OK
linux-2.6.24.7-m32r: OK
linux-2.6.25.11-m32r: OK
linux-2.6.26-m32r: OK
linux-2.6.27-m32r: OK
linux-2.6.28-m32r: OK
linux-2.6.29.1-m32r: OK
linux-2.6.30-m32r: OK
linux-2.6.31-m32r: OK
linux-2.6.32-rc3-m32r: ERRORS
linux-2.6.30-mips: WARNINGS
linux-2.6.31-mips: OK
linux-2.6.32-rc3-mips: ERRORS
linux-2.6.27-powerpc64: ERRORS
linux-2.6.28-powerpc64: ERRORS
linux-2.6.29.1-powerpc64: ERRORS
linux-2.6.30-powerpc64: ERRORS
linux-2.6.31-powerpc64: ERRORS
linux-2.6.32-rc3-powerpc64: ERRORS
linux-2.6.22.19-x86_64: ERRORS
linux-2.6.23.12-x86_64: ERRORS
linux-2.6.24.7-x86_64: ERRORS
linux-2.6.25.11-x86_64: ERRORS
linux-2.6.26-x86_64: OK
linux-2.6.27-x86_64: OK
linux-2.6.28-x86_64: OK
linux-2.6.29.1-x86_64: WARNINGS
linux-2.6.30-x86_64: WARNINGS
linux-2.6.31-x86_64: WARNINGS
linux-2.6.32-rc3-x86_64: ERRORS
sparse (linux-2.6.31): OK
sparse (linux-2.6.32-rc3): OK
linux-2.6.16.61-i686: ERRORS
linux-2.6.17.14-i686: ERRORS
linux-2.6.18.8-i686: ERRORS
linux-2.6.19.5-i686: ERRORS
linux-2.6.20.21-i686: ERRORS
linux-2.6.21.7-i686: ERRORS
linux-2.6.16.61-x86_64: ERRORS
linux-2.6.17.14-x86_64: ERRORS
linux-2.6.18.8-x86_64: ERRORS
linux-2.6.19.5-x86_64: ERRORS
linux-2.6.20.21-x86_64: ERRORS
linux-2.6.21.7-x86_64: ERRORS

Detailed results are available here:

http://www.xs4all.nl/~hverkuil/logs/Sunday.log

Full logs are available here:

http://www.xs4all.nl/~hverkuil/logs/Sunday.tar.bz2

The V4L2 specification failed to build, but the last compiled spec is here:

http://www.xs4all.nl/~hverkuil/spec/v4l2.html

The DVB API specification from this daily build is here:

http://www.xs4all.nl/~hverkuil/spec/dvbapi.pdf

--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: More about Winfast TV USB Deluxe

2009-10-18 Thread Magnus Alm
Hi again.

Started to look at getting the remote to work also.
I used Terratec Cinergy 250 USB as template and added the needed
information in:

em28xx-cards.c
em28xx.h
em28xx-input.c
ir-common.h
ir-keymaps.c

Compiled it with: make, make install and rebooted.

But it seems that I've missed something since ir-kbd-i2c loads, but it
doesn't seem to look for any ir devices.
Tried loading ir-kbd-i2c with debug=1, but not even an error message
shows up in dmesg, it looks just as before.

What I've added in the files is in a text file attachment.

The keymap I added is just garabage and the polling structure in
em28xx is probably wrong too.
But I have to start somewhere.

/Magnus



2009/10/15 Magnus Alm magnus@gmail.com:
 yay

 [ 2478.224015] tda9887 4-0043: configure for: Radio Stereo
 [ 2478.224017] tda9887 4-0043: writing: b=0xcc c=0x90 e=0x3d

 /Magnus

 2009/10/15 Magnus Alm magnus@gmail.com:
 Strange, but changeing the tvaudio_addr = 0xb0 to 88, (half of the
 decimal value of b0) made tvaudio find my tda9874.

 [ 1186.725140] tvaudio: TV audio decoder + audio/video mux driver
 [ 1186.725142] tvaudio: known chips: tda9840, tda9873h, tda9874h/a/ah,
 tda9875, tda9850, tda9855, tea6300, tea6320, tea6420, tda8425,
 pic16c54 (PV951), ta8874z
 [ 1186.725151] tvaudio 4-0058: chip found @ 0xb0
 [ 1186.736444] tvaudio 4-0058: chip_read2: reg254=0x11
 [ 1186.749704] tvaudio 4-0058: chip_read2: reg255=0x2
 [ 1186.749708] tvaudio 4-0058: tda9874a_checkit(): DIC=0x11, SIC=0x2.
 [ 1186.749710] tvaudio 4-0058: found tda9874a.
 [ 1186.749712] tvaudio 4-0058: tda9874h/a/ah found @ 0xb0 (em28xx #0)
 [ 1186.749714] tvaudio 4-0058: matches:.
 [ 1186.749716] tvaudio 4-0058: chip_write: reg0=0x0
 [ 1186.760012] tvaudio 4-0058: chip_write: reg1=0xc0
 [ 1186.772014] tvaudio 4-0058: chip_write: reg2=0x2
 [ 1186.784013] tvaudio 4-0058: chip_write: reg11=0x80
 [ 1186.796010] tvaudio 4-0058: chip_write: reg12=0x0
 [ 1186.808013] tvaudio 4-0058: chip_write: reg13=0x0
 [ 1186.820012] tvaudio 4-0058: chip_write: reg14=0x1
 [ 1186.832015] tvaudio 4-0058: chip_write: reg15=0x0
 [ 1186.844012] tvaudio 4-0058: chip_write: reg16=0x14
 [ 1186.856018] tvaudio 4-0058: chip_write: reg17=0x50
 [ 1186.868011] tvaudio 4-0058: chip_write: reg18=0xf9
 [ 1186.880745] tvaudio 4-0058: chip_write: reg19=0x80
 [ 1186.892347] tvaudio 4-0058: chip_write: reg20=0x80
 [ 1186.904015] tvaudio 4-0058: chip_write: reg24=0x80
 [ 1186.916011] tvaudio 4-0058: chip_write: reg255=0x0
 [ 1186.928021] tvaudio 4-0058: tda9874a_setup(): A2, B/G [0x00].
 [ 1186.928091] tvaudio 4-0058: thread started

 Now I probably need to set some gpio's too

 /Magnus

 2009/10/14 Magnus Alm magnus@gmail.com:
 Loaded em28xx with i2c_scan and i2c_debug and tvaudio with tda9874a
 option and debug.

 sudo modprobe -v em28xx i2c_scan=1 i2c_debug=1
 sudo modprobe -v tvaudio tda9874a=1 debug=1

 And got this ouput:

 [91083.588182] em28xx #0: found i2c device @ 0x30 [???]
 [91083.590179] em28xx #0: found i2c device @ 0x3e [???]
 [91083.590804] em28xx #0: found i2c device @ 0x42 [???]
 [91083.600308] em28xx #0: found i2c device @ 0x86 [tda9887]
 [91083.603805] em28xx #0: found i2c device @ 0xa0 [eeprom]
 [91083.606183] em28xx #0: found i2c device @ 0xb0 [tda9874]
 [91083.608808] em28xx #0: found i2c device @ 0xc2 [tuner (analog)]
 [91083.617682] em28xx #0: Identified as Leadtek Winfast USB II Deluxe 
 (card=28)
 [91083.617684] em28xx #0:
 [91083.617684]
 [91083.617687] em28xx #0: The support for this board weren't valid yet.
 [91083.617688] em28xx #0: Please send a report of having this working
 [91083.617690] em28xx #0: not to V4L mailing list (and/or to other 
 addresses)
 [91083.617691]
 [91083.980702] saa7115 4-0021: saa7114 found (1f7114d0e00) @ 0x42
 (em28xx #0)
 [91086.173114] tvaudio: TV audio decoder + audio/video mux driver
 [91086.173116] tvaudio: known chips: tda9840, tda9873h, tda9874h/a/ah,
 tda9875, tda9850, tda9855, tea6300, tea6320, tea6420, tda8425,
 pic16c54 (PV951), ta8874z
 [91086.173125] tvaudio 4-00b0: chip found @ 0x160
 [91086.173127] tvaudio 4-00b0: no matching chip description found
 [91086.173131] tvaudio: probe of 4-00b0 failed with error -5


 It seems to be a tda9874 there - em28xx #0: found i2c device @ 0xb0 
 [tda9874]

 But does tvaudio stop @ 0x160 (decimal value of 0xa0 rigth? ) and
 doesn't look further?
 I mean does tvaudio find my boards eeprom, cant talk to it and gives up?


 /Magnus


 2009/10/13 Magnus Alm magnus@gmail.com:
 Hi!

 Thanks to Devin's moral support I  now have sound in television. ;-)

 Thanks!!

 I pooked around some more managed to get radio to function with these 
 settings:

 [EM2820_BOARD_LEADTEK_WINFAST_USBII_DELUXE] = {
                .name         = Leadtek Winfast USB II Deluxe,
                .valid        = EM28XX_BOARD_NOT_VALIDATED,
                .tuner_type   = TUNER_PHILIPS_FM1216ME_MK3,
                .tda9887_conf = TDA9887_PRESENT |
                                TDA9887_PORT1_ACTIVE,