[linux-dvb] Problem with keys repeated
I've updated my machine and now my Logitech remote is giving me multiple events on a single keypress. I use the Logitech learning remote as a relacement for the original (which works fine) Card is a Hauppauge Win-TV Nova-T which I believe uses the budget-ci driver, I've heard this has been changed recently and this may be the problem? I've tried booting with a previous kernel but this doesn't work either as I assumed it was the built in driver changing that was causing the problem. Confused. 'sudo evtest /dev/input/irremote' shows the following with a single keypress (DOWN); Original Hauppauge Nova-T remote Event: time 1172928669.099038, type 1 (Key), code 108 (Down), value 1 Event: time 1172928669.099045, type 0 (Reset), code 0 (Reset), value 0 Event: time 1172928669.336429, type 1 (Key), code 108 (Down), value 0 Event: time 1172928669.336435, type 0 (Reset), code 0 (Reset), value 0 Logitech Harmony 525 Remote Event: time 1172928613.397507, type 1 (Key), code 108 (Down), value 1 Event: time 1172928613.397515, type 0 (Reset), code 0 (Reset), value 0 Event: time 1172928613.649279, type 1 (Key), code 108 (Down), value 2 Event: time 1172928613.649288, type 0 (Reset), code 0 (Reset), value 0 Event: time 1172928613.685270, type 1 (Key), code 108 (Down), value 2 Event: time 1172928613.685277, type 0 (Reset), code 0 (Reset), value 0 Event: time 1172928613.721272, type 1 (Key), code 108 (Down), value 2 Event: time 1172928613.721279, type 0 (Reset), code 0 (Reset), value 0 Event: time 1172928613.757279, type 1 (Key), code 108 (Down), value 2 Event: time 1172928613.757286, type 0 (Reset), code 0 (Reset), value 0 Event: time 1172928613.763489, type 1 (Key), code 108 (Down), value 0 Event: time 1172928613.763494, type 0 (Reset), code 0 (Reset), value 0 Any idea how to rectify this? I've tried different LIRC options with no success. Are there any options for the driver that would help to ignore the repeated codes? Many thanks Dom ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Problem with keys repeated
On Tue, March 6, 2007 12:20, Dom H wrote: Event: time 1172928613.397507, type 1 (Key), code 108 (Down), value 1 Key Down pressed Event: time 1172928613.649279, type 1 (Key), code 108 (Down), value 2 Event: time 1172928613.685270, type 1 (Key), code 108 (Down), value 2 Event: time 1172928613.721272, type 1 (Key), code 108 (Down), value 2 Event: time 1172928613.757279, type 1 (Key), code 108 (Down), value 2 Key Down repeated Event: time 1172928613.763489, type 1 (Key), code 108 (Down), value 0 Key Down released Any idea how to rectify this? I've tried different LIRC options with no success. Are there any options for the driver that would help to ignore the repeated codes? Try updating LIRC too? -- Simon Arlott ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Nova-T 500 user experience
Hi there, I was wondering, does every Nova-T 500 owner (using it on Linux) suffer from the USB disconnect malfunction? Or is there someone out there who runs it perfectly? My setup (Ubuntu 6.10 + 2.6.20.1 kernel + latest v4l dvb Mercurial) suffers from usb disconnects, and because of that, kernel oopsen. -- jussi ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Problem with keys repeated
On Tue, March 6, 2007 13:20, Dom H said: I've updated my machine and now my Logitech remote is giving me multiple events on a single keypress. I use the Logitech learning remote as a relacement for the original (which works fine) Card is a Hauppauge Win-TV Nova-T which I believe uses the budget-ci driver, I've heard this has been changed recently and this may be the problem? I've tried booting with a previous kernel but this doesn't work either as I assumed it was the built in driver changing that was causing the problem. Confused. I've already answered your question on the LIRC list. Did you try using kbd-utils to change the repeat rate? You might also try loading ir-common with the parameter repeat=0. -- David Härdeman ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Problem on SAA7134 Asustek (Tiger or Jayhawk components : 1043:4871) : HELP !
Hartmut Hackmann a écrit : Hi, Emmanuel Emmanuel Quémener schrieb: Hartmut Hackmann a écrit : Hi, Emmanuel Emmanuel Quémener schrieb: Emmanuel Quémener a écrit : Hartmut Hackmann a écrit : I noticed 2 things: tuner 2-004b: AGC2 gain is: 10 This means maximum gain. With active LNA, i would expect lower values... second: The reason for the tumbling channel decoder might be a not closed AGC loop. But if DVB-T works after analog was on once with tuner_config 3, this leads me to this: Analog - digital mode switch might be GPIO22 like it is with some ADS / Lifeview cards. Did you ever try card=87? But this would cause trouble with the LNA since in the Philips solutions, GPIO22 always is involved. Are you sure the board has a LNA? In the philips designs, it sits under the tuner shield and looks like a SMD voltage regulator. If there is a LNA, the board seems to have a mode switch we haven't seen yet. Except - did you try to invert tda1004x GPIO1, so .gpio_config = TDA10046_GP00_I, instead .gpio_config = TDA10046_GP01_I, Maybe this helps Hartmut I will do it this evening. So, if I sum up, there are 2 tests to perform : - #1 : try to change board from 109 to 87 : in this case, must I get an clean archive or do I keep some changes to tuner_config reference ? - #2 : try to change GPIO config reference : in this case, same as before : clean archive or modified one on tuner_config reference ? Bye EQ Is it necessary to keep tuner_config=3 to definitions or must I get a not modified archive to try to change my board from 109 to 87 and change only GPIO config Sorry, but I didn't take the time in the past 2 weeks to experiment the tests you'd like. I try on last sunday to compile a new kernel (the last one : 2.6.20) with a blank repository on v4l-dvb archive and make the changes on it : it sucks !!! - the new kernel 2.6.20 does not recognized my board - when I try to compile new repository and install the modules, the saa7134 module doesn't want to load - when I search in files saa7134-dvb.c and saa-7134-cards.c the references to tuner_config, It was impossible to find them So, my questions : - how is it possible for me to compile last kernel 2.6.20 with third party v4l-dvb archives ? - when can I get this 2.6.20 working archives ? - what modifications can I perform to test and make working my board (1043:4871 reference)... Please use my personal repository for the tests. It is at: http://linuxtv.org/hg/~hhackmann/v4l-dvb It does compile on kernel 2.6.20, i have it running here. Just to be sure: - if you compiled for another kernel before, you need to delete the file v4l/.version - don't try to merge the files into the kernel, compile them separately with make, make install (for the install, you need to be root - never mix modules with older versions. - afik, you need to enable the v4l and dvb stuff in the kernel tree. Looks like you missed a mail from me, i will just paste it here: I had a look at the eeprom dump again: The card should be a copy of the Tiger-S reference design without radio. So please try this: Get a copy of my personal repository, compile and install. Then do: modprobe saa7134 card=109 secam=l modprobe saa7134-alsa modprobe saa7134-dvb This should do it as long as there are not tricks with the windows driver. You sould no longer need to load the saa7134-alsa and saa7134-dvb modules manually. Good luck Hartmut ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb I've just compiled the modules on a fresh 2.6.20.1 kernel and the output is badly following : saa7134: disagrees about version of symbol videobuf_streamoff saa7134: Unknown symbol videobuf_streamoff saa7134: disagrees about version of symbol videobuf_poll_stream saa7134: Unknown symbol videobuf_poll_stream saa7134: disagrees about version of symbol videobuf_read_stop saa7134: Unknown symbol videobuf_read_stop saa7134: disagrees about version of symbol videobuf_dma_free saa7134: Unknown symbol videobuf_dma_free saa7134: disagrees about version of symbol videobuf_reqbufs saa7134: Unknown symbol videobuf_reqbufs saa7134: Unknown symbol ir_codes_encore_enltv saa7134: disagrees about version of symbol videobuf_waiton saa7134: Unknown symbol videobuf_waiton saa7134: disagrees about version of symbol videobuf_dqbuf saa7134: Unknown symbol videobuf_dqbuf saa7134: disagrees about version of symbol videobuf_queue_init saa7134: Unknown symbol videobuf_queue_init saa7134: Unknown symbol ir_rc5_timer_keyup saa7134: Unknown symbol ir_codes_asus_pc39 saa7134: Unknown symbol ir_rc5_timer_end
Re: [linux-dvb] Random kernel oopses using TwinhanDTV Alpha and dvb-usb-vp7045
I'm sorry that I haven't answered you ealier. I'm rather busy these days. Okay, the problem is with rmmod / insmod. Actually I have rmmod problems too with my PCI DVB-C-card. I can do anything with my card, but not use rmmod command. So my current fix is, that I never use rmmod. I just reboot instead. I can live with it, because I can't unplug the device when the power is on. I remember lockups and OOPSes also. Currently active email list thread [PATCH] dvb-core: Fix several lockingrelatedproblems. might be about the lockup problem that you have faced. They are making fixes also. Maybe you could help them for example by testing their fixes. This paticular problem seems to have attention now. These USB-related threads might also be interesting for you: [linux-dvb] Re: Nova-T 500 (dvb_usb_dib0700) usb disconnects [linux-dvb] Nova-T 500 user experience Regards, Marko Ristola Tomas wrote: On Sat, 3 Mar 2007 at 9:52am, Marko Ristola wrote: Hello, Hi, The randomness of problems suggest that the problem is bad memory hardware. Good idea. I hadn't thought about that, but there's a reason why (and I still don't believe that the cause): the only time I experience any problems is when loading and unloading the DVB modules. Not when I load/unload other modules (usb-related or otherwise; some examples are usb-storage, cdrom, ide-cd, forcedeth, nvidia etc.), compile new kernels, edit stuff recorded with my DVB cards, surf, mail... I simply haven't noticed any other problems that could be due to bad RAM. I'd suggest to use some memory testing tool to check that your memory works. You might find a memory testing tool on Linux distribution's recovery CD or install CD. I think that Knoppix CD has that also. The tool is named memtest. I have run the latest Debian unstable versions of memtest86+ (for 1.5 hours), memtest86 (for 2 hours), and memmxtest (for 1 hours) and none of them have found any errors. True, they can miss things (as they mention in the docs), but, like I wrote earlier, my system is solid except when loading/unloading DVB modules. So my money is still on some subtle error in the modules. Unfortunately. Does anyone have any ideas on how what my next step should be? (Except giving up or switching to another receiver, of course. :) /Tomas Regards, Marko Ristola Tomas kirjoitti: Hello, First of all, I apologize in advance for a long post, but I figure it's better to provide some error messages instead of just writing a stupid help, TwinhanDTV doesn't work, why? post. I find it hard to believe I'm the only one experiencing these problems, but digging around with google and on linuxtv.org haven't been of any help. Here goes: I'm experiencing random kernel errors with my TwinhanDTV Alpha USB 2.0 DVB-T receiver using the dvb-usb-vp7045 kernel module: 1. Sometimes the kernel completely freezes up. Powercycle needed. 2. Sometimes the kernel completely freezes up with the CapsLock and ScrLk LEDs on my keyboard blinking. Powercycle needed. 3. Sometimes the keyboard/mouse stops working in X but pressing the power button makes acpid initiate a shutdown (so at least the kernel isn't completely hosed). The shutdown hangs at Unmounting local filesystems at which point the keyboard is working again (I guess it was only dead in X) so I can do a Alt-SysRq-S followed by Alt-SysRq-B. 4. And very rarely not even the keyboard/mouse stops working in X, but I get all the syslog error messages printed to every xterm. Any one of these errors (though very rarely number 4) happens about 30%-50% of the time when I'm using the DVB receiver. My experience as a programmer tells me that when such random errors occur they're usually due to something simple such as an uninitialized variable being used (but there are no such warnings when compiling the modules) or a pointer that has an incorrect value. The freezes all seem to occur either when the dvb-usb-vp7045 module gets loaded by modprobe or when it's unloaded. At least that's what I'm guessing after reading through the error messages in /var/log/kern.log . The crashes occur with both kernel 2.6.18.2 and 2.6.20.1 . (AMD Athlon XP 2500+ with 512MB RAM on an ASUS A7N8X Deluxe motherboard.) Today's crash (of type 2) occurred when I was trying to start a recording scheduled by crontab at 12:58. I discovered the crash at 16:18. It left these traces in /var/log/kern.log : Mar 2 07:03:20 miguel kernel: usb 1-1: USB disconnect, address 4 Mar 2 12:58:01 miguel logger: Initializing recording Mar 2 12:58:01 miguel logger: rmmod dvb-usb-vp7045 Mar 2 12:58:15 miguel kernel: usbcore: deregistering interface driver dvb_usb_vp7045 Mar 2 12:58:15 miguel kernel: dvb-usb: Twinhan USB2.0 DVB-T receiver (TwinhanDTV Alpha/MagicBox II) successfully deinitialized and disconnected. Mar 2 12:58:15 miguel logger: rmmod dvb-usb Mar 2 12:58:15 miguel logger: rmmod dvb-usb-vp7045 Mar 2 12:58:15
Re: [linux-dvb] Nova-T 500 user experience (Juha Ruotsalainen) Re: Nova-T 500 user experience
On 3/6/07, Eduard Huguet [EMAIL PROTECTED] wrote: Hi there, I was wondering, does every Nova-T 500 owner (using it on Linux) suffer from the USB disconnect malfunction? Or is there someone out there who runs it perfectly? My setup (Ubuntu 6.10 + 2.6.20.1 kernel + latest v4l dvb Mercurial) suffers from usb disconnects, and because of that, kernel oopsen. -- jussi Hi, I've been following this topic on the mailing list without intervining, as (AFAIK at least...) I've never suffered this issue. I have a Nova-T 500 card mounted on a Asus P1-AH2 barebone (AMD-64), running Sabayon Linux 64-bit edition and MythTV 0.20. I really can't say if this has never happened, maybe I didn't notice it or else I simply don't leave the system enough hours working (with tuning activity, I mean...). One problem that I do suffer is that I can't detect any channels from within MythTV. I need to manually scan them by using dvbscan and then import the channels.conf file. Doing so, I can watch all the channels in my area. I don't receive any EIT info, though. I wonder if this is because of the relatively poor signal in my area or precisely because the channels are externally scanned and then MythTV doesn't have all the required info to receive EIT data. What is your experience with suspend (ram and disk)? BTW kaffeine tunes without issues /PG ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova-T 500 user experience (Juha Ruotsalainen) Re: Nova-T 500 user experience
On 6 Mar 2007, at 15:53, Eduard Huguet wrote: One problem that I do suffer is that I can't detect any channels from within MythTV. I need to manually scan them by using dvbscan and then import the channels.conf file. I've only managed to tune with kaffeine. Any other tool simply doesn't seem to lock properly with this card. I do have the usb disconnects though. -- Torgeir Veimo [EMAIL PROTECTED] ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] dvb_usb_dib0700 based devices and random usb disconnects
Richard Lithvall wrote: I asked a few questions in the linux-usb-dev mailing list. And one of the developers thought this might have been caused by a bug that only got fixed post-2.6.20. I haven't had a chance to try this yet, but you can read about it here: http://www.linuxtv.org/pipermail/linux-dvb/2007-February/015808.html I applied that patch on 2.6.20 and haven't got any kernel oops since then (Feb 7) and still keep my fingers crossed... =) Well, that was too much to hope for. I had another kernel oops Feb 27 but I must say that it's far more stable now. /Richard ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] RTP stored file reader
Hi at all, I'm testing a DVB-H TS file stored on my pc. In order to analyze the single H.264 over RTP flows, I need to extract the ES from TS and after analyze the RTP packet. I found on Internet some applications for ES extraction, but I don't know the way to 'read' a stored H.264 over RTP/UDP/IP file. Do you know some applications to do it? Thanks a lot for your support. Best Regards, Paolo ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova-T 500 user experience (Juha Ruotsalainen) Re: Nova-T 500 user experience
On Tuesday 06 March 2007 16:53:19 Eduard Huguet wrote: One problem that I do suffer is that I can't detect any channels from within MythTV. I need to manually scan them by using dvbscan and then import the channels.conf file. Doing so, I can watch all the channels in my area. I don't receive any EIT info, though. I wonder if this is because of the relatively poor signal in my area or precisely because the channels are externally scanned and then MythTV doesn't have all the required info to receive EIT data. The channels.conf from dvbscan doesn't contain original network and transport stream IDs which are crucial for EIT to work. Mythtv's channel scan works with my Nova-T 500 just fine. Could you please send the console output of mythtv-setup -v channel,record,siparser either to the mythtv-dev mailing list (subscription requirred) or me privately. Janne ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] bug in szap-utility
Hi folks, as part of the Debain package dvb-utils 1.1.1-2 the szap utility has the following bug: 1. The start transponder file of Eutelsat Hotbird13.0E contains a H as description of the polarization. 2. Unfortunately this H is being interpreted as V. 3. So if you try to produce a transponder list with the start transponder you are trapped as nothing works! To see the error yourself, try the following example in the console: szap -r -a0 -c trapz.txt -n1 where trapz.txt looks like this: Hotbird-13.0E:12539:H:1:27500 In the console you will see the right frequency and the right symbol rate. But the polarization will be printed out as V (vertical) instead of H (horizontal). In other words: The bug is: szap cannot set equal the letter h with the letter H Regards Uwe P. S.: I solved the problem by a TCL-TK workaround, but it rather should be solved in the sourcecode, shouldn't it? So can someone reading this please fix that bug in the source code? -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] bug in szap-utility
Uwe Bugla schreef: Hi folks, as part of the Debain package dvb-utils 1.1.1-2 the szap utility has the following bug: 1. The start transponder file of Eutelsat Hotbird13.0E contains a H as description of the polarization. 2. Unfortunately this H is being interpreted as V. 3. So if you try to produce a transponder list with the start transponder you are trapped as nothing works! To see the error yourself, try the following example in the console: szap -r -a0 -c trapz.txt -n1 where trapz.txt looks like this: Hotbird-13.0E:12539:H:1:27500 With which program did you create the trapz.txt file? My scan or scandvb program creates only lower cases polarization characters (v or h). I think the szap program only recognizes lowercase by design. In the console you will see the right frequency and the right symbol rate. But the polarization will be printed out as V (vertical) instead of H (horizontal). In other words: The bug is: szap cannot set equal the letter h with the letter H Regards Uwe P. S.: I solved the problem by a TCL-TK workaround, but it rather should be solved in the sourcecode, shouldn't it? So can someone reading this please fix that bug in the source code? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Linux DVB + PCI bus extender (Magma) - Anyone?
I'm looking to purchase a PCI bus extender by Magma to use with my Nexus-S, SkayStar2 and Twinhan cards. Before I spend the money, however, I wanted to cover my bases and make sure I'm not going to run into any latency or timing issues with slots in the extender. Has anyone has success using one of these with any DVB cards under Linux? Thanks in advance, Mark. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Re: DVB-H information
Le mardi 6 mars 2007 16:43, Francesco Schiavarelli a écrit : Stéphane Esté-Gracias wrote: I found on Internet a free application to extract PES or ES from a TS, but don't know how I can 'de-packetize' the RTP/UDP/IP stack to visualize the raw H.264 stream. Do you know application in order to do it? I used dvbnet apps (available with Linux DVB) to receive datagrams from TS on a virtual net interface and routing to a multicast group. Then you should be able to dump the H.264 ES with mplayer, I used VLC to watch audio and video. regards, Francesco Hello Francesco, I've tried without any succes to read DVB-H streams throught dvbnet and VLC. I only use tcpdump to extract packets from dvbnet interface. To get the ESG I've done the following: 1 - Tune and create dvb network interface with dvbnet on the ESG pid 2 - Bring up dvb0_0 in promisc mode (otherwise won't work) 3 - Start a multicast routing daemon to route packet to eth0 4 - Receive ALC/FLUTE packets to reassemble ESG using bootstrap 5 - Extract SDP file from ESG In 3) I used smcroute as I had problems with mrouted. In 4) I used MAD-FLUTE receiver In 5) you can have the SDP inspecting ESG fragments with a hex editor To get A/V you need the SDP and then again: 1 - Tune and create dvb network interface with dvbnet on the A/V pid 2 - Bring up dvb0_0 in promisc mode (otherwise won't work) 3 - Start a multicast routing daemon to route packet to eth0 4 - Start VLC with the given SDP and enjoy your TV! Thank you for this procedure :) For your information, I've started (first step) to write a library to decode ESG in order to obtain SDP (aka PMT like in DVB-H systems) Please see DVB-APPS repository for LIBESG : http://linuxtv.org/hg/dvb-apps?mf=8b37590c8695;path=/lib/libesg/;style=gi tweb Very good! I hacked in some c code to parse ESG and extract SDP files. It's ugly, incomplete and mostly unreadable code, but works here. I'll be happy to share it, you are warned :) Why not :) ! My code is only a library to parse most of ESG fragments (in LGPL). I wanted to code application against my library, but I have no time yet. Stephane regards, Francesco ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Problem with keys repeated
On Tue, Mar 06, 2007 at 04:38:17PM +, Dom H wrote: Forgot to say, my card uses the cx88 driver. I'm sorry but my knowledge is mostly on the ir handling of the budget-ci driver. I'll forward this to the linux-dvb list...hopefully someone with more insight in the cx88 driver will be able to help you with the repeat rate issue... -- David Härdeman ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Issues with Nova 500 T
Hi All! I have a couple of questions regarding the Nova 500 T. 1. How can I be sure that it is _the_ USB-disconnect bug i am getting? I guess there is other kinds of BUGs and Ooopses to. 2. SNR is not reported in tzap (always equal to ). Signal, ber, unc is reported. Does this depend on hardware limitations or is it just not implemented? 3. Adapter0 gets significantly higher signal strength on certain MUXes. (around 0x0a000 compared to 0x09000). How come? 4. Normally both unc and ber is zero, but sometimes I get around 0x01000 in ber and around 0x00010-0x00100 in unc. Strange thing is that it seems like a little tzapping cures it. It does not always seem to affect both adapters simultaneously, which would had indicated a bad reception. I don't know whether one adapter is more prone to this than the other. More research is needed. I use kernel 2.6.20-gentoo, and a couple of hours old hg. I don't know which version of the firmware I have, but the md5sum is: tevens firmware # md5sum dvb-usb-dib0700-01.fw 551df6387db5bf5a8ca4d10cc30beaa5 dvb-usb-dib0700-01.fw force_lna_activation is on. tevens ~ # cat /sys/module/dvb_usb_dib0700/parameters/force_lna_activation 1 Please let me know if you need more information. Kudos and Best regards, Simon ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [RFC] Reviewed development procedures
On Tue, 6 Mar 2007, Michael Krufky wrote: #2, I have made some corrections to the document. Please see these corrections inline below. I'll add some too. +drivers. They are a volunteer, non-remunerated, group of people that ^^^ ??? [I believe that unremunerated is the correct word, Contributing one's time without pay.] ^volunteer and unremunerated group of people +2. Git trees related with v4l/dvb development ^trees' relationhsips with + == + +The main kernel trees are hosted at http://git.kernel.org. Each tree +is owned by a maintainer. + +The main kernel tree is owned by Linus Torvalds, being located at: ^ and is located at: + http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git + +The subsystem master tree, is owned by the subsystem maintainer (Mauro ^ v4l ^ remove comma +Carvalho Chehab), being located at: ^and is located at: + http://git.kernel.org/?p=linux/kernel/git/mchehab/v4l-dvb.git + +Mike Krufky maintains a number of backport trees, having patches ^^^ Michael Krufky ^which have patches +3. Mercurial trees used on v4l/dvb development ^^ for +V4L/DVB driver development is hosted at http://linuxtv.org. There are a +number of trees there, owned by each developer of the LinuxTV team. Each ^^ each owned by a developer on the +developer use to keep and maintain one or more trees there with their +development stuff. ^^ [I'd delete this sentence.] +When a developer believes that he have patches done to be merged, he ^ has ^finished patches to be +send a request to developers ML and to the subsystem maintainer. The ^sends ^the developers' mailing list +patches are analised and, if they look ok, merged at the master ^ analyzed ^into ?? +It is a good practice that each developer will have at least one tree ^is good practice +called 'v4l-dvb', keeping their stable patches, periodically updating +his tree with master's patches. ^, which keeps their patches, and periodically update this tree with the master tree's patches. +4. Community best practices + + +From the accumulated experience, there are some basic rules that should ^^^ remove the +b) All commits at mercurial trees should have a consistent message, + describing the patch. This is done by using: + + make commit + + This will run some scripts that will check changed files, seeking for ^remove will ^correct bad whitespace + bad whitespace practices and will prepare the last Signed-off-by ^remove will + field, as described below. A good comment will have a brief + description at the first line, up to 68 characters wide, the patch author's ^a blank line, the patch author's + name at the second line, and a brief description, with no more than ^on the third line, a blank line, and then a brief description + 80 chars by line, like: ^per ^e.g. [Should we have the make commit script check the line length limits?] + All lines starting with # will be removed by make commit stripts. And all lines starting with HG: will be removed by Mercurial. + + *WARNING* Be careful not to leave the first line blank, otherwise hg + will leave subject in blank. ^the subject blank. + From: line shouldn't be suppressed, since it will be used when ^ omitted^for the patch author when converting to -git. +c) For make commit to work properly, the HGUSER shell environment var + should be defined (replacing the names at the left): + + HGUSER=My Name [EMAIL PROTECTED] If HGUSER is not set, then, if present, the username defined in the user's ~/.hgrc file will be used. Use of the .hgrc file is preferred over the HGUSER variable according to the hg man page. This name will be used for both the user metadata in the Hg commit log and the initial values of the From: and Signed-off-by: lines in the pre-made commit message. + It is also possible to use a different login name at the site ^for + hosting the repo, by using: + + CHANGE_LOG_LOGIN=my_log_name + +
Re: [linux-dvb] [RFC] Reviewed development procedures
Am Dienstag, den 06.03.2007, 11:14 -0500 schrieb Michael Krufky: Mauro Carvalho Chehab wrote: Hi Guys, The last time we've reviewed our procedures were on March, 2006. I think it is time to review the documents (there's still an even more ancient file, from 2005!). I'm enclosing a file, with my understanding on the current practices for V4L/DVB development. Please comment. Mauro, A few issues... #1, I think we're better off keeping this document called README.patches, as we have already directed users on the mailing lists to this file, and those emails remain indexed in google forever. IMHO, better to stay consistent. #2, I have made some corrections to the document. Please see these corrections inline below. Regards, Michael Krufky ... + +The main kernel trees are hosted at http://git.kernel.org. Each tree +is owned by a maintainer. + +The main kernel tree is owned by Linus Torvalds, being located at: + http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git + +The subsystem master tree, is owned by the subsystem maintainer (Mauro ^ v4l Hi, someone should stand up as dvb maintainer instead of blaming Mauro for doing the dirt. Then this spreading off lists, he wants to rewrite linux-dvb completely and other madness might stop. Hermann ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] dvb maintainer
hermann pitton wrote: Am Dienstag, den 06.03.2007, 11:14 -0500 schrieb Michael Krufky: Mauro Carvalho Chehab wrote: Hi Guys, The last time we've reviewed our procedures were on March, 2006. I think it is time to review the documents (there's still an even more ancient file, from 2005!). I'm enclosing a file, with my understanding on the current practices for V4L/DVB development. Please comment. Mauro, A few issues... #1, I think we're better off keeping this document called README.patches, as we have already directed users on the mailing lists to this file, and those emails remain indexed in google forever. IMHO, better to stay consistent. #2, I have made some corrections to the document. Please see these corrections inline below. Regards, Michael Krufky ... + +The main kernel trees are hosted at http://git.kernel.org. Each tree +is owned by a maintainer. + +The main kernel tree is owned by Linus Torvalds, being located at: + http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git + +The subsystem master tree, is owned by the subsystem maintainer (Mauro ^ v4l Hi, someone should stand up as dvb maintainer instead of blaming Mauro for doing the dirt. Then this spreading off lists, he wants to rewrite linux-dvb completely and other madness might stop. Hermann, I changed the subject so as not to deter from the original RFC. When somebody hijaacks a thread, discussing an entirely different topic, while retaining the original subject line, it makes these threads entirely difficult to follow. Please change the subject if you are going to change the discussion. About dvb maintainer -- The job is being done by the DVB maintainers, collectively. Mauro is the v4l maintainer, and he is acting patch monkey for both subsystems. This model is working OK for now. When a topic comes up and a decision needs to be made about the DVB subsystem, us DVB maintainers discuss it on email _and_ irc. Mauro does not make decisions for the DVB subsystem, and he has been sticking to his own area. Nobody blames Mauro for doing the dirt -- He does v4l stuff only. Mauro does a good job forwarding patches, and there is no reason to change it, unless a dvb maintainer has a problem with how he is doing so. If there is such a problem, then it should be discussed and dealt with. IN ITS OWN THREAD. Please keep unrelated topics separate. Regards, Michael Krufky ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Problem with keys repeated
On Tue, Mar 06, 2007 at 06:52:48PM +0200, Ville-Pekka Vainio wrote: David Härdeman kirjoitti viestissään (lähetysaika tiistai, 6. maaliskuuta 2007 15:26:20): On Tue, March 6, 2007 13:20, Dom H said: I've updated my machine and now my Logitech remote is giving me multiple events on a single keypress. I've already answered your question on the LIRC list. Did you try using kbd-utils to change the repeat rate? You might also try loading ir-common with the parameter repeat=0. I've been having the same kind of problems with Technotrend C-1500 and it's bundled remote (a grey one). I tried loading ir-common with repeat=0, but still it seems to take quite a long time before the keypress gets generated. It feels like I anyway have to invoke some kind of repeat handling to get the keypress through. I'm not quite sure I follow, you have the same kind of problem (i.e. that a continous keypress generates repeat events)? But then you talk about time before the keypress is generated? For repeat or no repeat, the keypress should be generated instantly (it is not the key down event but the key up event that might be delayed with the repeat handling). Then, if I keep pressing the key after one keypress has been generated, it sometimes generates no repeat keypresses, sometimes one or two more keypresses. And all this with repeat=0. As you might imagine, controlling VDR is a bit of a challenge right now. I had no problems with this remote before the recent changes to the IR handling. Could you explain why you tried using repeat=0 in the first place? -- David Härdeman ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Problem with keys repeated
Kirjoitit viestissäsi (lähetysaika keskiviikko, 7. maaliskuuta 2007 00:18:49): I've been having the same kind of problems with Technotrend C-1500 and it's bundled remote (a grey one). I tried loading ir-common with repeat=0, but still it seems to take quite a long time before the keypress gets generated. It feels like I anyway have to invoke some kind of repeat handling to get the keypress through. I'm not quite sure I follow, you have the same kind of problem (i.e. that a continous keypress generates repeat events)? But then you talk about time before the keypress is generated? I'll try to explain better how the remote works for me. I'm not sure if the problem is really the same, but it sounded similar, so I decided to tell about it on this thread... At first, maybe for about ten keypresses after boot or reloading the drivers, the remote works perfectly. The event happens immediately after pressing the key. Then it goes into a mode where I have to press the key for a long time before anything happens. And when the event actually occurs, then it often also generates a repeat. I tried repeat=0 to stop this unwanted repeat from occurring, but it didn't work very well. I tried to get an evtest log of the situation: Event: time 1173221474.755429, type 1 (Key), code 103 (Up), value 1 Event: time 1173221474.755434, type 0 (Reset), code 0 (Reset), value 0 Event: time 1173221475.155711, type 1 (Key), code 103 (Up), value 2 Event: time 1173221475.155716, type 0 (Reset), code 0 (Reset), value 0 Event: time 1173221475.219704, type 1 (Key), code 103 (Up), value 0 Event: time 1173221475.219707, type 0 (Reset), code 0 (Reset), value 0 -- Ville-Pekka Vainio [EMAIL PROTECTED] ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Problem on SAA7134 Asustek (Tiger or Jayhawk components : 1043:4871) : HELP !
Hi, Emmanuel Emmanuel Quémener schrieb: Hartmut Hackmann a écrit : Hi, Emmanuel Emmanuel Quémener schrieb: Hartmut Hackmann a écrit : Hi, Emmanuel Emmanuel Quémener schrieb: Emmanuel Quémener a écrit : Hartmut Hackmann a écrit : I noticed 2 things: tuner 2-004b: AGC2 gain is: 10 This means maximum gain. With active LNA, i would expect lower values... second: The reason for the tumbling channel decoder might be a not closed AGC loop. But if DVB-T works after analog was on once with tuner_config 3, this leads me to this: Analog - digital mode switch might be GPIO22 like it is with some ADS / Lifeview cards. Did you ever try card=87? But this would cause trouble with the LNA since in the Philips solutions, GPIO22 always is involved. Are you sure the board has a LNA? In the philips designs, it sits under the tuner shield and looks like a SMD voltage regulator. If there is a LNA, the board seems to have a mode switch we haven't seen yet. Except - did you try to invert tda1004x GPIO1, so .gpio_config = TDA10046_GP00_I, instead .gpio_config = TDA10046_GP01_I, Maybe this helps Hartmut I will do it this evening. So, if I sum up, there are 2 tests to perform : - #1 : try to change board from 109 to 87 : in this case, must I get an clean archive or do I keep some changes to tuner_config reference ? - #2 : try to change GPIO config reference : in this case, same as before : clean archive or modified one on tuner_config reference ? Bye EQ Is it necessary to keep tuner_config=3 to definitions or must I get a not modified archive to try to change my board from 109 to 87 and change only GPIO config Sorry, but I didn't take the time in the past 2 weeks to experiment the tests you'd like. I try on last sunday to compile a new kernel (the last one : 2.6.20) with a blank repository on v4l-dvb archive and make the changes on it : it sucks !!! - the new kernel 2.6.20 does not recognized my board - when I try to compile new repository and install the modules, the saa7134 module doesn't want to load - when I search in files saa7134-dvb.c and saa-7134-cards.c the references to tuner_config, It was impossible to find them So, my questions : - how is it possible for me to compile last kernel 2.6.20 with third party v4l-dvb archives ? - when can I get this 2.6.20 working archives ? - what modifications can I perform to test and make working my board (1043:4871 reference)... Please use my personal repository for the tests. It is at: http://linuxtv.org/hg/~hhackmann/v4l-dvb It does compile on kernel 2.6.20, i have it running here. Just to be sure: - if you compiled for another kernel before, you need to delete the file v4l/.version - don't try to merge the files into the kernel, compile them separately with make, make install (for the install, you need to be root - never mix modules with older versions. - afik, you need to enable the v4l and dvb stuff in the kernel tree. Looks like you missed a mail from me, i will just paste it here: I had a look at the eeprom dump again: The card should be a copy of the Tiger-S reference design without radio. So please try this: Get a copy of my personal repository, compile and install. Then do: modprobe saa7134 card=109 secam=l modprobe saa7134-alsa modprobe saa7134-dvb This should do it as long as there are not tricks with the windows driver. You sould no longer need to load the saa7134-alsa and saa7134-dvb modules manually. Good luck Hartmut ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb I've just compiled the modules on a fresh 2.6.20.1 kernel and the output is badly following : saa7134: disagrees about version of symbol videobuf_streamoff saa7134: Unknown symbol videobuf_streamoff saa7134: disagrees about version of symbol videobuf_poll_stream saa7134: Unknown symbol videobuf_poll_stream saa7134: disagrees about version of symbol videobuf_read_stop saa7134: Unknown symbol videobuf_read_stop saa7134: disagrees about version of symbol videobuf_dma_free saa7134: Unknown symbol videobuf_dma_free saa7134: disagrees about version of symbol videobuf_reqbufs saa7134: Unknown symbol videobuf_reqbufs saa7134: Unknown symbol ir_codes_encore_enltv saa7134: disagrees about version of symbol videobuf_waiton saa7134: Unknown symbol videobuf_waiton saa7134: disagrees about version of symbol videobuf_dqbuf saa7134: Unknown symbol videobuf_dqbuf saa7134: disagrees about version of symbol videobuf_queue_init saa7134: Unknown symbol videobuf_queue_init saa7134: Unknown symbol ir_rc5_timer_keyup saa7134: Unknown symbol
[linux-dvb] Is my card supported/known? 1461:4836
Hi, my new notebook is equipped with a DVB-T card, and I fear there may be no support for it on Linux, yet. The notebook (ASUS A7CC-7S018C) was released about a month ago, and I guess the hardware is about the same age. Therefore, I'm not really that surprised at not finding any information about the card on the Internet (well, it would be kinda nice if AverMedia mentioned it on one of its websites, but they don't seem to consider that necessary). Windows Vista calls the card AVerMedia M10D MiniPCI Hybrid DVBT. lspci says this: 01:02.0 Multimedia controller: Philips Semiconductors SAA7133/SAA7135 Video Broadcast Decoder (rev d1) Subsystem: Avermedia Technologies Inc Unknown device 4836 01:02.0 0480: 1131:7133 (rev d1) Subsystem: 1461:4836 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 64 Interrupt: pin A routed to IRQ 7 Region 0: Memory at f9dff800 (32-bit, non-prefetchable) [size=2K] Capabilities: [40] 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- And that's about all the information I got. I don't want to open the laptop unless it's really necessary, so I've never actually seen the card. I read that SAA7133 was supported quite well, so I tried to load the right modules, but I *think* it didn't work (actually I have no idea). People said I could use tvtime to check, but that doesn't work with my video card. Anyway, I wanna use mplayer. But I don't know exactly how to play TV with mplayer, so the reason I saw nothing but a black screen may alsa have been me making a mistake when invoking mplayer. Here's what I tried: mplayer tv:// -tv driver=v4l2:norm=PAL:input=0:amode=1:width=384:height=288:outfmt=yuy2:device=/dev/video0:chanlist=europe-west:channel=E2 (got it from Gentoo Wiki, didn't have time to read the mplayer manual, yet) So, if anyone could tell me how best to find out whether card and tuner are working (so I can try out all AverMedia cards or so), that would be nice. Here's what dmesg had to say: saa7130/34: v4l2 driver version 0.2.14 loaded ACPI: PCI Interrupt :01:02.0[A] - GSI 19 (level, low) - IRQ 19 saa7133[0]: found at :01:02.0, rev: 209, irq: 19, latency: 64, mmio: 0xf9dff800 saa7133[0]: subsystem: 1461:4836, board: UNKNOWN/GENERIC [card=0,autodetected] saa7133[0]: board init: gpio is 0 saa7133[0]: i2c eeprom 00: 61 14 36 48 00 00 00 00 00 00 00 00 00 00 00 00 saa7133[0]: i2c eeprom 10: ff ff ff ff ff 20 ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom 20: 01 40 01 32 32 01 01 43 88 ff 00 80 ff ff ff ff saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom 40: ff 6b 00 ff c2 1e ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c scan: found device @ 0xa0 [eeprom] saa7133[0]: registered device video0 [v4l2] saa7133[0]: registered device vbi0 So, my questions now are: Is the card known in any way? If not, how can I best test the different existing drivers? If I don't find anything there, are there some simple things I could change in the kernel sources, or will I have to build a completely new driver? (as you might notice, I'm not prepared to give up, no matter what it takes) Ah, also: will it be _really_ useful to open the laptop and take a look at the card? TIA, Florian Zwicke ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Problem on SAA7134 Asustek (Tiger or Jayhawk components : 1043:4871) : HELP !
... When we start debugging this, you should set the options debug=1 for the modules tuner and tda827x. Then the drivers report what they try to do with the gain. Hi, video_buf_dvb seems to be a problem on auto. I'll try again, if some stop teaching native english to the Indians. Cheers, Hermann ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Problem with keys repeated
On Tuesday, 6 March 2007 at 12:20:39 +, Dom H wrote:
I've updated my machine and now my Logitech remote is giving me multiple
events on a single keypress. I use the Logitech learning remote as a
relacement for the original (which works fine) Card is a Hauppauge Win-TV
Nova-T which I believe uses the budget-ci driver, I've heard this has been
changed recently and this may be the problem? I've tried booting with a
previous kernel but this doesn't work either as I assumed it was the built
in driver changing that was causing the problem. Confused.
This (and many other reports of similar behaviour) looks like the
problem that I had with my DVICO remote control. It suffers from
premature repeat: it's almost impossible to press a button without
creating at least one or two repeat events.
I've worked around this issue in LIRC with the following code in
daemons/hw_hiddev.c. This is part of a patch which makes it work
under FreeBSD; the complete patch is available via
http://www.freebsd.org/cgi/pds.cgi?ports/comms/lirc
/*
* This stuff is probably dvico specific.
* I don't have any other hid devices to test...
*/
- if (event.hid == 0x10046) {
- repeat_flag = (main_code dvico_repeat_mask);
+ if (pre_code == 0x10046) {
+if (main_code dvico_repeat_mask) /* repeated press */
+ repeat_count++;/* count them */
+else
+ repeat_count = 0; /* reset */
+repeat_flag = repeat_count 2; /* real repeat flag */
main_code = (main_code ~dvico_repeat_mask);
- return decode_all(remotes);
+/*
+ * Skip this if we're working around the premature
+ * repeat.
+ */
+if (repeat_flag || (repeat_count == 0))
+{
+ char *foo;
+
+ foo = decode_all(remotes);
+/*
+ * XXX Experimental code. Chop off the first
12
+ * bytes of the hex code, which FreeBSD does
not
+ * provide, and which I suspect nobody cares
+ * about.
+ *
+ * For some reason, we can get NULL back here,
+ * so we need to check for that before
returning
+ * address 0xc.
+ */
+if (foo)
+ foo = foo [12]; /* chop off the leading
chars. */
+return foo;
+}
+else
+ return 0;/* no data */
Clearly the important line is:
+repeat_flag = repeat_count 2; /* real repeat flag */
Depending on the sensitivity of your remote control, you may need some
other value of 2.
Greg
--
Finger [EMAIL PROTECTED] for PGP public key.
See complete headers for address and phone numbers.
pgpvoIAWLLKBR.pgp
Description: PGP signature
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova-T 500 user experience (Juha Ruotsalainen) Re:Nova-T 500 user experience (OT: Mythtv / EIT)
I don't receive any EIT info, though. I wonder if this is because of the relatively poor signal in my area or precisely because the channels are externally scanned and then MythTV doesn't have all the required info to receive EIT data. I also didn't get EIT data when importing the channels. Same experience as: http://www.mythtvtalk.com/forum/archive/o_t/t_4939/epg_eit_does_not_work.html After a channel scan by Mythtv EIT data worked for me. Maybe I used a non Nova-T-500 card for the scan - I don't remember. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Problem with keys repeated
On Tue, March 6, 2007 23:59, Ville-Pekka Vainio said: Kirjoitit viestissäsi (lähetysaika keskiviikko, 7. maaliskuuta 2007 00:18:49): I'm not quite sure I follow, you have the same kind of problem (i.e. that a continous keypress generates repeat events)? But then you talk about time before the keypress is generated? I'll try to explain better how the remote works for me. I'm not sure if the problem is really the same, but it sounded similar, so I decided to tell about it on this thread... At first, maybe for about ten keypresses after boot or reloading the drivers, the remote works perfectly. The event happens immediately after pressing the key. Then it goes into a mode where I have to press the key for a long time before anything happens. This is very weird, the keypress event (as opposed to the repeat or release event) should be instant. Could you try running the module with ir_debug=1 and send me the output of dmesg after such a run. It would be good if you could combine it with evtest so that there are timestamps to correlate the different key events. And when the event actually occurs, then it often also generates a repeat. I tried repeat=0 to stop this unwanted repeat from occurring, but it didn't work very well. I tried to get an evtest log of the situation: Event: time 1173221474.755429, type 1 (Key), code 103 (Up), value 1 Event: time 1173221474.755434, type 0 (Reset), code 0 (Reset), value 0 Event: time 1173221475.155711, type 1 (Key), code 103 (Up), value 2 Event: time 1173221475.155716, type 0 (Reset), code 0 (Reset), value 0 Event: time 1173221475.219704, type 1 (Key), code 103 (Up), value 0 Event: time 1173221475.219707, type 0 (Reset), code 0 (Reset), value 0 This looks like it should as far as I can tell...400 ms from first keypress until the first repeat, and then a key release event about 75 ms later. The delay until the first repeat event can be changed using kbdrate with the -d parameter. -- David Härdeman ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova-T 500 user experience (Juha Ruotsalainen) Re:Nova-T 500 user experience (OT: Mythtv / EIT)
It seems that effectively when using externally-generated data MythTV is not able to receive EIT. Unfortunately there seems to be a problem with my card and MythTV regarding internal channel scanning. Someone has pointed me to generate a log report some messages ago while scanning, maybe then I'll find any solution. It's not a very big issue for me, as I can get listings for the most popular channels using the internet grabber, but it would be great if it could be complemented with the (usually) more up-to-date info provided by EIT. Cheers Eduard 2007/3/7, Arnold Schulz [EMAIL PROTECTED]: I don't receive any EIT info, though. I wonder if this is because of the relatively poor signal in my area or precisely because the channels are externally scanned and then MythTV doesn't have all the required info to receive EIT data. I also didn't get EIT data when importing the channels. Same experience as: http://www.mythtvtalk.com/forum/archive/o_t/t_4939/epg_eit_does_not_work.html After a channel scan by Mythtv EIT data worked for me. Maybe I used a non Nova-T-500 card for the scan - I don't remember. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
