Re: [PATCH] support of GoTView PCI-E X5 3D Hybrid in cx23885
Hi, Is there a way to add such drivers to staging branch etc to make testing simple? Some times I don't understand why drivers are included with their current design and others not. Having extra repos like s2-liplianin is great but why were drivers there and non merged upstream? Popular multimedia distros are using that branch and not official driver :-(. Maybe some kind of decision in v4l-dvb should be adapted to fit other requirements. Getting useful answers to questions or problems is another example eg: http://www.mail-archive.com/linux-media@vger.kernel.org/msg12758.html http://www.mail-archive.com/linux-media@vger.kernel.org/msg21646.html I asked about several problems (last 6 months) but got not one useful answer from the lists (linux-media / v4l-dvb). Like this: tda8261_cfg.h: This header-file contains more than only declarations :-(. printk of tuned frequencies or used bandwith is maybe useful for debuging purposes but not for stable drivers in linux kernel. These printk's should be removed or changed to use an vebbose or debug module parameter. Otherwise you get your kernel log filed with useless tda messages and big syslog files. Sorry it's really frustrating to ask without getting any kind of answers. Regarding that new driver: I agree the new code should be tested with real dvb/... hardware before merging it upstream. -- 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
[PATCH] add Technisat skystar usb plus USB-ID
this device is a rebranded Technotrend s-2400 with USB id 0x3009. THx to Carsten Wehmeier for reporting Signed-off-by: Halim Sahin halim.sa...@freenet.de --- drivers/media/dvb/dvb-usb/dvb-usb-ids.h |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/drivers/media/dvb/dvb-usb/dvb-usb-ids.h b/drivers/media/dvb/dvb-usb/dvb-usb-ids.h index 192a40c..380066b 100644 --- a/drivers/media/dvb/dvb-usb/dvb-usb-ids.h +++ b/drivers/media/dvb/dvb-usb/dvb-usb-ids.h @@ -204,6 +204,7 @@ #define USB_PID_AVERMEDIA_A805 0xa805 #define USB_PID_AVERMEDIA_A815M0x815a #define USB_PID_TECHNOTREND_CONNECT_S2400 0x3006 +#define USB_PID_TECHNOTREND_CONNECT_S2400 0x3009 #define USB_PID_TECHNOTREND_CONNECT_CT3650 0x300d #define USB_PID_TERRATEC_CINERGY_DT_XS_DIVERSITY 0x005a #define USB_PID_TERRATEC_CINERGY_DT_XS_DIVERSITY_2 0x0081 -- 1.7.2.2 -- 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: where can I report dvb module related bug reports?
hi, It seems the storry never ends :-(. One of my reported problems is really old but not fixed in the knc1 dvb-c driver of the knc1 dvb-c card (same with tt-ct-3650). The cam-status changes frequently and vdr uses that to determine if a cam is ready or not. Please see also: http://www.mail-archive.com/v...@linuxtv.org/msg06132.html Please help. Regards Halim -- 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: where can I report dvb module related bug reports?
Hi, On So, Nov 28, 2010 at 06:05:57 -0600, Jonathan Isom wrote: Hi I am not developer however been on this list since move. This is the appropriate list. However I search my archive(gmail account) and I didn't get them. I find it interesting that they are in the mail-archive archive. I would assume something may have happened with the mail server. Hopefully as this reply shows you will get your help. Thats sounds interesting but I received my own messages from the list at that time. Ok anyway maybe somebody can help with the decribed issues? BR. Halim Please can you help with the following things: http://www.mail-archive.com/linux-media@vger.kernel.org/msg12758.html http://www.mail-archive.com/linux-media@vger.kernel.org/msg21646.html THX Regards halim -- 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 -- ASUS M4A78 PRO motherboard Athlon II X4 640 Processor 4 Gigabytes of DDR2-800 Gigabyte nVidia 9400gt Graphics adapter KWorld ATSC 110 TV Capture Card KWorld ATSC 115 TV Capture Card -- Halim Sahin E-Mail: halim.sahin (at) t-online.de -- 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
where can I report dvb module related bug reports?
Hi, Sorry folks I know that dvb driver development is done in your spare time. However posting to this list or linux-dvb I got no answers which is really frustrating :-(. Please can you tell me which is the prefered way for submitting bug reports to dvb driver developers? Please can you help with the following things: http://www.mail-archive.com/linux-media@vger.kernel.org/msg12758.html http://www.mail-archive.com/linux-media@vger.kernel.org/msg21646.html THX Regards halim -- 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
[no subject]
help -- 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
bugreport: strange issues in tda8261 frontend (missing symbols etc).
Hi List, 1. The module adds MODULE_PARM_DESC(verbose, Set verbosity level); but doesn't declare the needed variables or uses this parameter somewhere. This ends in missing symbol when trying to specify that parameter when loading the frontend. 2. The module logs many lines when tuning to a new channel. This results in fast growing big logs in /var/log (several mb's ad a day). Here some lines of the log: Aug 24 07:23:57 vdr kernel: [44045.944177] tda8261_get_frequency: Frequency=188 Aug 24 07:23:57 vdr kernel: [44045.952037] tda8261_get_bandwidth: Bandwidth=4000 Aug 24 07:24:04 vdr kernel: [44052.132637] tda8261_get_bandwidth: Bandwidth=4000 Aug 24 07:24:04 vdr kernel: [44052.136747] tda8261_get_bandwidth: Bandwidth=4000 Aug 24 07:24:04 vdr kernel: [44052.138596] tda8261_set_state: Step size=1, Divider=1000, PG=0x798 (1944) Aug 24 07:24:04 vdr kernel: [44052.138883] tda8261_set_state: Waiting to Phase LOCK Aug 24 07:24:04 vdr kernel: [44052.160156] tda8261_get_status: Tuner Phase Locked Aug 24 07:24:04 vdr kernel: [44052.160163] tda8261_set_state: Tuner Phase locked: status=1 Aug 24 07:24:04 vdr kernel: [44052.160168] tda8261_set_frequency: Frequency=1944000 Aug 24 07:24:04 vdr kernel: [44052.160173] tda8261_get_frequency: Frequency=1944000 Aug 24 07:24:04 vdr kernel: [44052.168031] tda8261_get_bandwidth: Bandwidth=4000 Aug 24 07:24:09 vdr kernel: [44057.016717] tda8261_get_bandwidth: Bandwidth=4000 Aug 24 07:24:09 vdr kernel: [44057.021165] tda8261_get_bandwidth: Bandwidth=4000 Aug 24 07:24:09 vdr kernel: [44057.023052] tda8261_set_state: Step size=1, Divider=1000, PG=0x60c (1548) Aug 24 07:24:09 vdr kernel: [44057.023305] tda8261_set_state: Waiting to Phase LOCK Aug 24 07:24:09 vdr kernel: [44057.044169] tda8261_get_status: Tuner Phase Locked Aug 24 07:24:09 vdr kernel: [44057.044177] tda8261_set_state: Tuner Phase locked: status=1 Aug 24 07:24:09 vdr kernel: [44057.044182] tda8261_set_frequency: Frequency=1548000 Aug 24 07:24:09 vdr kernel: [44057.044187] tda8261_get_frequency: Frequency=1548000 Aug 24 07:24:09 vdr kernel: [44057.053034] tda8261_get_bandwidth: Bandwidth=4000 Kernel 2.6.34 was used on that system. Thx. Halim -- 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
tda8261: produces unnecessary big debug logs
Hi Folks, /var/log/warn growed to several mb in two days. Most of the contents is the output of tda8261. Aug 21 19:52:10 vdr kernel: [181504.252173] tda8261_get_frequency: Frequency=2033000 Aug 21 19:51:49 vdr kernel: [181483.256031] tda8261_get_bandwidth: Bandwidth=4000 . After every channelswitch the module logs something like that. I tried to add verbose=0 but this didn't help. What can I do to reduce these messages. Regards halim -- 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
knc1 dvb-c card frequently looses CAM when switching channels quickly
Hello, I have experienced the following on my vdr machine: When changing channels quickly between encrypted channels, the card loosses cam and I get the following in my /var/log/messages: [ 67.645354] dvb_ca adapter 0: DVB CAM detected and initialised successfully [ 84.659047] budget-av: cam inserted A [ 85.656855] dvb_ca adapter 0: DVB CAM detected and initialised successfully [60706.931218] budget-av: cam inserted A [60707.485891] dvb_ca adapter 0: DVB CAM detected and initialised successfully lspci -vvv 03:00.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) Subsystem: KNC One Device 0022 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 64 (3750ns min, 9500ns max) Interrupt: pin A routed to IRQ 19 Region 0: Memory at f9fffc00 (32-bit, non-prefetchable) [size=512] Kernel driver in use: budget_av I am using drivers from kernel 2.6.34. Any Ideas for solving this issue? Thx. Halim -- 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
debug messages in tda8261 module
Hello, I am always getting the following in my dmesg: [749690.144036] tda8261_get_bandwidth: Bandwidth=4000 What does the message mean and how can I switch of this message? Thanks Halim -- 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
v4l-dvb build problem with soc_camera
Hi, Same environment like in my previous mail: /root/work/v4l-dvb/v4l/soc_camera.c:27:30: error: linux/pm_runtime.h: No such file or directory /root/work/v4l-dvb/v4l/soc_camera.c: In function 'soc_camera_open': /root/work/v4l-dvb/v4l/soc_camera.c:392: error: implicit declaration of function 'pm_runtime_enable' /root/work/v4l-dvb/v4l/soc_camera.c:393: error: implicit declaration of function 'pm_runtime_resume' /root/work/v4l-dvb/v4l/soc_camera.c:422: error: implicit declaration of function 'pm_runtime_disable' /root/work/v4l-dvb/v4l/soc_camera.c: In function 'soc_camera_close': /root/work/v4l-dvb/v4l/soc_camera.c:448: error: implicit declaration of function 'pm_runtime_suspend' make[3]: *** [/root/work/v4l-dvb/v4l/soc_camera.o] Error 1 make[2]: *** [_module_/root/work/v4l-dvb/v4l] Error 2 make[1]: *** [default] Fehler 2 make: *** [all] Fehler 2 BR. Halim -- 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
problem compiling modoule mt9t031 in current v4l-dvb-hg
Hi Folks, I was not able to build v4l-dvb from hg (checked out today). /root/work/v4l-dvb/v4l/mt9t031.c:729: error: unknown field 'runtime_suspend' specified in initializer /root/work/v4l-dvb/v4l/mt9t031.c:730: error: unknown field 'runtime_resume' specified in initializer /root/work/v4l-dvb/v4l/mt9t031.c:730: warning: initialization from incompatible pointer type make[3]: *** [/root/work/v4l-dvb/v4l/mt9t031.o] Error 1 make[2]: *** [_module_/root/work/v4l-dvb/v4l] Error 2 make[1]: *** [default] Fehler 2 make: *** [all] Fehler 2 Kernel 2.6.31 (x86_64) regards Halim -- 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
[linux-dvb] pcie dvb-c
Hello, I know of some dvb-s pcie cards but what about dvb-c. Do we have a working pcie dvb-c card?? with kind regards Halim -- 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: ok more details: Re: bttv problem loading takes about several minutes
Hi, Ok I have tested modprobe bttv audiodev=-1 card=34 tuner=24 gbuffers=16 I am seeing again the delay. More ideas? Regards Halim -- Halim Sahin E-Mail: halim.sahin (at) t-online.de -- 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: bttv problem loading takes about several minutes
Hi,
On Mi, Jun 17, 2009 at 10:06:26 +0200, Hans Verkuil wrote:
The log is from bttv version 0.9.17. The new code is only present in version
0.9.18. So this is definitely not related to any of my changes.
The text bttv0: gpio: en=, out= in=003ff502 [init] comes
from the call to bttv_gpio_tracking in bttv_probe, then the next
text bttv0: tuner type=24 comes from early in bttv_init_card2, before any
i2c modules have been loaded.
The code in bttv_probe (bttv-driver.c) does this:
if (bttv_verbose)
bttv_gpio_tracking(btv,init);
/* needs to be done before i2c is registered */
bttv_init_card1(btv);
/* register i2c + gpio */
init_bttv_i2c(btv);
/* some card-specific stuff (needs working i2c) */
bttv_init_card2(btv);
So it looks like it can be either bttv_init_card1 or init_bttv_i2c that is
causing the delay.
Halim, can you try to put some printk() statements in between the calls
above to see which call is taking so long? Actually, it would be nice if
you are able to 'drill-down' as well in whatever function is causing the
delay, since I truly don't see what might be delaying things for you.
So I have tested latest v4l-dvb from hg.
The mentioned code was changed like this:
if (bttv_verbose)
{
printk (bttv_gpio_tracking(bt);
bttv_gpio_tracking(btv,init);
}
/* needs to be done before i2c is registered */
printk(bttv_init_card1(btv););
printk(bttv_init_card1(btv););
bttv_init_card1(btv);
/* register i2c + gpio */
printk(init_bttv_i2c(btv););
init_bttv_i2c(btv);
Result:
[ 1069.277781] bttv: driver version 0.9.18 loaded
[ 1069.277788] bttv: using 8 buffers with 2080k (520 pages) each for capture
[ 1069.277886] bttv: Bt8xx card found (0).
[ 1069.277906] bttv0: Bt878 (rev 17) at :00:0b.0, irq: 19, latency: 32, mmio
: 0xf780
[ 1069.278105] bttv0: using: Leadtek WinFast 2000/ WinFast 2000 XP [card=34,insm
od option]
[ 1069.278167] bttv_gpio_tracking(bt7bttv0: gpio: en=, out= in
=003ff502 [init]
[ 1069.278173] bttv_init_card1(btv);bttv_init_card1(btv);init_bt
tv_i2c(btv);6bttv0: tuner type=24
Regards,
Hans
Giving this command with current drivers has some problems:
1. it takes several minutes to load bttv module.
2. capturing doesn't work any more (dropped frames etc).
Tested with current v4l-dvb from hg, ubuntu 9.04,
debian lenny.
I have a bt878 based card from leadtek.
Here is my output after loading the driver:
[ 3013.735459] bttv: driver version 0.9.17 loaded
[ 3013.735470] bttv: using 32 buffers with 16k (4 pages) each for
capture [ 3013.735542] bttv: Bt8xx card found (0).
[ 3013.735562] bttv0: Bt878 (rev 17) at :00:0b.0, irq: 19, latency:
32, mmio
: 0xf780
[ 3013.737762] bttv0: using: Leadtek WinFast 2000/ WinFast 2000 XP
[card=34,insm od option]
[ 3013.737825] bttv0: gpio: en=, out= in=003ff502
[init] [ 3148.136017] bttv0: tuner type=24
[ 3148.136029] bttv0: i2c: checking for MSP34xx @ 0x80... not found
[ 3154.536019] bttv0: i2c: checking for TDA9875 @ 0xb0... not found
[ 3160.936018] bttv0: i2c: checking for TDA7432 @ 0x8a... not found
[ 3167.351398] bttv0: registered device video0
[ 3167.351434] bttv0: registered device vbi0
[ 3167.351463] bttv0: registered device radio0
[ 3167.351485] bttv0: PLL: 28636363 = 35468950 . ok
[ 3167.364182] input: bttv IR (card=34) as /class/input/input6
Please help!
Regards
Halim
--
Halim Sahin
E-Mail:
halim.sahin (at) t-online.de
--
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
--
Hans Verkuil - video4linux developer - sponsored by TANDBERG Telecom
--
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
--
Halim Sahin
E-Mail:
halim.sahin (at) t-online.de
--
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
ok more details: Re: bttv problem loading takes about several minutes
Hi, sorry for the nusable output! I found the time consuming funktion: bttv_init_card2(btv); This takes about 4 min. today. my new testcode: /* needs to be done before i2c is registered */ printk(linke 2:bttv_init_card1(btv);\n); bttv_init_card1(btv); /* register i2c + gpio */ printk(line 3: init_bttv_i2c(btv);\n); init_bttv_i2c(btv); /* some card-specific stuff (needs working i2c) */ printk(line4: some card-specific stuff needs working i2c \n); bttv_init_card2(btv); printk(irq init\n); init_irqreg(btv); dmesg output: [ 2282.430209] bttv: driver version 0.9.18 loaded [ 2282.430216] bttv: using 8 buffers with 2080k (520 pages) each for capture [ 2282.430313] bttv: Bt8xx card found (0). [ 2282.430334] bttv0: Bt878 (rev 17) at :00:0b.0, irq: 19, latency: 32, mmio : 0xf780 [ 2282.430777] bttv0: using: Leadtek WinFast 2000/ WinFast 2000 XP [card=34,insm od option] [ 2282.430839] bttv_gpio_tracking(bt [ 2282.430843] bttv0: gpio: en=, out= in=003ff502 [init] [ 2282.430845] linke 2:bttv_init_card1(btv); [ 2282.430859] line 3: init_bttv_i2c(btv); [ 2282.430917] line4: some card-specific stuff needs working i2c [ 2282.430922] bttv0: tuner type=24 Ok here is the 4 min dely and after that the following linkes were printed out: [ 2416.836017] bttv0: audio absent, no audio device found! [ 2416.836024] irq init [ 2416.840551] bttv0: registered device video1 [ 2416.840684] bttv0: registered device vbi0 [ 2416.840716] bttv0: registered device radio0 [ 2416.840736] bttv0: PLL: 28636363 = 35468950 .6bttv0: PLL: 28636363 = 3546 8950 . ok [ 2416.856221] input: bttv IR (card=34) as /devices/pci:00/:00:0b.0/inpu t/input10 [ 2416.864069] ok Hope that helps! Regards Halim -- Halim Sahin E-Mail: halim.sahin (at) t-online.de -- 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: ok more details: Re: bttv problem loading takes about several minutes
Hi, On Do, Jun 18, 2009 at 01:09:56 +0200, Hans Verkuil wrote: Hi, sorry for the nusable output! I found the time consuming funktion: bttv_init_card2(btv); This takes about 4 min. today. my new testcode: /* needs to be done before i2c is registered */ printk(linke 2:bttv_init_card1(btv);\n); bttv_init_card1(btv); /* register i2c + gpio */ printk(line 3: init_bttv_i2c(btv);\n); init_bttv_i2c(btv); /* some card-specific stuff (needs working i2c) */ printk(line4: some card-specific stuff needs working i2c \n); bttv_init_card2(btv); printk(irq init\n); init_irqreg(btv); dmesg output: [ 2282.430209] bttv: driver version 0.9.18 loaded [ 2282.430216] bttv: using 8 buffers with 2080k (520 pages) each for capture [ 2282.430313] bttv: Bt8xx card found (0). [ 2282.430334] bttv0: Bt878 (rev 17) at :00:0b.0, irq: 19, latency: 32, mmio : 0xf780 [ 2282.430777] bttv0: using: Leadtek WinFast 2000/ WinFast 2000 XP [card=34,insm od option] [ 2282.430839] bttv_gpio_tracking(bt [ 2282.430843] bttv0: gpio: en=, out= in=003ff502 [init] [ 2282.430845] linke 2:bttv_init_card1(btv); [ 2282.430859] line 3: init_bttv_i2c(btv); [ 2282.430917] line4: some card-specific stuff needs working i2c [ 2282.430922] bttv0: tuner type=24 Ok here is the 4 min dely and after that the following linkes were printed out: [ 2416.836017] bttv0: audio absent, no audio device found! When you tested this with bttv 0.9.17, wasn't the delay then before the text 'tuner type=24'? Anyway, if you modprobe with the option 'audiodev=-1', will that solve this? If not, then can you do the same printk trick in the bttv_init_card2 function? I couldn't find a parameter audiodev in bttv module Do you mean audioall?? It has no effect. So I need an older revision of v4l-dvb to test the 17. drivers. Thanks regards Halim Regards, Hans [ 2416.836024] irq init [ 2416.840551] bttv0: registered device video1 [ 2416.840684] bttv0: registered device vbi0 [ 2416.840716] bttv0: registered device radio0 [ 2416.840736] bttv0: PLL: 28636363 = 35468950 .6bttv0: PLL: 28636363 = 3546 8950 . ok [ 2416.856221] input: bttv IR (card=34) as /devices/pci:00/:00:0b.0/inpu t/input10 [ 2416.864069] ok Hope that helps! Regards Halim -- Halim Sahin E-Mail: halim.sahin (at) t-online.de -- 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 -- Hans Verkuil - video4linux developer - sponsored by TANDBERG -- Halim Sahin E-Mail: halim.sahin (at) t-online.de -- 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: ok more details: Re: bttv problem loading takes about several minutes
Hi, you can see at my dmesg output [ 2282.430209] bttv: driver version 0.9.18 loaded i have done hg clone http://linuxtv.org/hg/v4l-dvb cd v4l-dvb make make install reboot No idea why I don't have the audiodev modparam? Regards Halim -- Halim Sahin E-Mail: halim.sahin (at) t-online.de -- 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
bttv problem loading takes about several minutes
Hi, In the past I could use this card by typing modprobe bttv card=34 tuner=24 gbuffers=16 Giving this command with current drivers has some problems: 1. it takes several minutes to load bttv module. 2. capturing doesn't work any more (dropped frames etc). Tested with current v4l-dvb from hg, ubuntu 9.04, debian lenny. I have a bt878 based card from leadtek. Here is my output after loading the driver: [ 3013.735459] bttv: driver version 0.9.17 loaded [ 3013.735470] bttv: using 32 buffers with 16k (4 pages) each for capture [ 3013.735542] bttv: Bt8xx card found (0). [ 3013.735562] bttv0: Bt878 (rev 17) at :00:0b.0, irq: 19, latency: 32, mmio : 0xf780 [ 3013.737762] bttv0: using: Leadtek WinFast 2000/ WinFast 2000 XP [card=34,insm od option] [ 3013.737825] bttv0: gpio: en=, out= in=003ff502 [init] [ 3148.136017] bttv0: tuner type=24 [ 3148.136029] bttv0: i2c: checking for MSP34xx @ 0x80... not found [ 3154.536019] bttv0: i2c: checking for TDA9875 @ 0xb0... not found [ 3160.936018] bttv0: i2c: checking for TDA7432 @ 0x8a... not found [ 3167.351398] bttv0: registered device video0 [ 3167.351434] bttv0: registered device vbi0 [ 3167.351463] bttv0: registered device radio0 [ 3167.351485] bttv0: PLL: 28636363 = 35468950 . ok [ 3167.364182] input: bttv IR (card=34) as /class/input/input6 Please help! Regards Halim -- Halim Sahin E-Mail: halim.sahin (at) t-online.de -- 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: bttv problem loading takes about several minutes
Hi, The card is a winfast tv 2000 xp rm edition lspci -vvv says: 00:0b.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 32 (4000ns min, 1ns max) Interrupt: pin A routed to IRQ 19 Region 0: Memory at f780 (32-bit, prefetchable) [size=4K] Capabilities: [44] Vital Product Data ? Capabilities: [4c] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: bttv Kernel modules: bttv 00:0b.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 32 (1000ns min, 63750ns max) Interrupt: pin A routed to IRQ 5 Region 0: Memory at f700 (32-bit, prefetchable) [size=4K] Capabilities: [44] Vital Product Data ? Capabilities: [4c] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- HTH. Halim -- Halim Sahin E-Mail: halim.sahin (at) t-online.de -- 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: bttv problem loading takes about several minutes
Hi, On Mi, Jun 17, 2009 at 10:06:26 +0200, Hans Verkuil wrote: The log is from bttv version 0.9.17. The new code is only present in version 0.9.18. So this is definitely not related to any of my changes. Yes it's from a debian lenny kernel 2.6.26. But I have tested latest v4l-dvb with the same result under 2.6.28 (ubuntu 9.04). The code in bttv_probe (bttv-driver.c) does this: if (bttv_verbose) bttv_gpio_tracking(btv,init); /* needs to be done before i2c is registered */ bttv_init_card1(btv); /* register i2c + gpio */ init_bttv_i2c(btv); /* some card-specific stuff (needs working i2c) */ bttv_init_card2(btv); So it looks like it can be either bttv_init_card1 or init_bttv_i2c that is causing the delay. Halim, can you try to put some printk() statements in between the calls above to see which call is taking so long? Actually, it would be nice if you are able to 'drill-down' as well in whatever function is causing the delay, since I truly don't see what might be delaying things for you. Yes I will test this tomorrow. Thanks a lot! Halim -- 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: TT 3650
Hi, On Mi, Feb 18, 2009 at 10:38:30 +0100, gimli wrote: Thats the Problem, you only can get the driver for your card from another repo, but not the main one. After the first rusch pusching s2api out, no one is intrested anymore to get more s2 cards working in the mainline development tree. FULLACK. What's the problem to merge these drivers into mainline repo? It's not easy for new users to find the drivers. it will be more userfriendly to have them in main linux kernel!!! BR. Halim -- 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
