[linux-dvb] make errors multiproto
Hi all The following errors occurred during the 'make all' of the multiproto install The mercurial was the latest from jusste.de I am using the TT3200 so the stb0899 errors will matter /home/mythtv/dvb/multiproto/v4l/dvb_frontend.c: In function 'dvb_frontend_thread': /home/mythtv/dvb/multiproto/v4l/dvb_frontend.c:1123: warning: unused variable 'status' /home/mythtv/dvb/multiproto/v4l/stb0899_drv.c: In function 'stb0899_diseqc_init': /home/mythtv/dvb/multiproto/v4l/stb0899_drv.c:834: warning: unused variable 'ret_2' /home/mythtv/dvb/multiproto/v4l/stb0899_drv.c:833: warning: unused variable 'ret_1' /home/mythtv/dvb/multiproto/v4l/stb0899_drv.c:832: warning: unused variable 'trial' /home/mythtv/dvb/multiproto/v4l/stb0899_drv.c:830: warning: unused variable 'i' /home/mythtv/dvb/multiproto/v4l/stb0899_drv.c:830: warning: unused variable 'count' /home/mythtv/dvb/multiproto/v4l/stb0899_drv.c:826: warning: unused variable 'rx_data' /home/mythtv/dvb/multiproto/v4l/stb0899_drv.c: In function 'stb0899_sleep': /home/mythtv/dvb/multiproto/v4l/stb0899_drv.c:899: warning: unused variable 'reg' /home/mythtv/dvb/multiproto/v4l/stb0899_drv.c: In function 'stb0899_track': /home/mythtv/dvb/multiproto/v4l/stb0899_drv.c:1935: warning: unused variable 'internal' /home/mythtv/dvb/multiproto/v4l/stb0899_drv.c:1932: warning: unused variable 'lock_lost' /home/mythtv/dvb/multiproto/v4l/stb0899_drv.c: At top level: /home/mythtv/dvb/multiproto/v4l/stb0899_drv.c:1727: warning: 'stb0899_track_carrier' defined but not used /home/mythtv/dvb/multiproto/v4l/stb0899_drv.c:1744: warning: 'stb0899_get_ifagc' defined but not used /home/mythtv/dvb/multiproto/v4l/stb0899_drv.c:1761: warning: 'stb0899_get_s1fec' defined but not used /home/mythtv/dvb/multiproto/v4l/stb0899_drv.c:1789: warning: 'stb0899_get_modcod' defined but not used /home/mythtv/dvb/multiproto/v4l/radio-si470x.c: In function 'si470x_get_rds_registers': /home/mythtv/dvb/multiproto/v4l/radio-si470x.c:562: warning: format '%d' expects type 'int', but argument 3 has type 'long unsigned int' Regards Mike curtis ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [patch] support for key repeat with dib0700 ir receiver
Il giorno mar, 19/02/2008 alle 19.19 +, Nicolas Will ha scritto: Now this is rich! I love it! Key repeat works! Great :)! And the log flooding has stopped without the manual patch that was needed previously. Nice, fixing this was not my first purpose but I'm glad it's solved. I hope you live in Aberdeen, Scotland, because I want to buy you a few beers right here and now! (though your name suggest a very different origin) Thanks! I'm pleased that someone else finds this useful! I'm sorry I'm not from Scotland, I live in Italy but thank you for your offer, if I will travel to Aberdeen a beer would be great :D! Thanks also for mentioning me in the wiki. Greets, Filippo ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] uk-Sudbury dvb-t tuning data file question.
-Original Message- From: Christoph Pfister [mailto:[EMAIL PROTECTED] Sent: 10 February 2008 12:33 To: linux-dvb@linuxtv.org Cc: Goodey,SJ,Steve,ASAC6N R Subject: Re: [linux-dvb] uk-Sudbury dvb-t tuning data file question. Hi, Am Dienstag 05 Februar 2008 schrieb [EMAIL PROTECTED]: Hello, Apologies if this is the wrong list to ask. Perhaps you could answer a few questions for me? Sudbury, in England, is one of the sites with two DVB-T transmitters, Sudbury and SudburyB, main transmitter Tacolneston. On my Mythtv box I have found /usr/share/doc/dvb-utils/examples/scan/dvb-t/uk-SudburyB but there is no file for Sudbury. Now according to the www.ukfree.tv site Sudbury has six muxes, SudburyB has only one for ITV. I suspect I am missing something here, why is there only one frequency file for Sudbury and why is called SudburyB? I guess it's just wrongly named; will fix that. Should there be two files, as for Dover for example, uk-Sudbury with six muxes and uk_SudburyB with one? Geographically close transmitters should be in a single file; oh well, will fix that, too ... I assume MythTv does not use these files during tuning? Regards, Steve Goodey Christoph Christoph, Thanks for your work on this, appreciated. Steve ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [patch] support for key repeat with dib0700 ir receiver
Il giorno mer, 20/02/2008 alle 09.22 +0100, Filippo Argiolas ha scritto: Il giorno mer, 20/02/2008 alle 06.10 +0900, Matthew Vermeulen ha scritto: Hi all... I'm seeing exactly the same problems everyone else is (log flooding etc) except that I can't seem to get any keys picked by lirc or /dev/input/event7 at all... Are you sure that the input device is receiving the events? Did you try evtest /dev/input/event7? Is LIRC properly configured? Are you using this file for lircd.conf [http://linux.bytesex.org/v4l2/linux-input-layer-lircd.conf]? Does irw catch some event? I forgot to say to not use irrecord with dev/input driver since it's thinked to record raw events from remotes and doesn't work with input devices (usually it ends up with a lircd.conf file that interprets key press and release as separated events doubling each event). Just use the proper input-layer-lircd.conf. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [patch] support for key repeat with dib0700 ir receiver
Wouldn't going away from an event interface kill a possible direct link between the remote and X? Yes, it would. The way I see it, LIRC is an additional layer that may be one too many in most cases. From my point of view, it is a relative pain I could do without. But I may have tunnel vision by lack of knowledge. I agree with you. I'm more looking for a solution with existing things. LIRC is not in kernel. I don't think we should do something specific, new. If there is nothing which can be done with the event system I think we should either extend it or just drop this idea. IMHO, the event interface does not match well with the reduced key set on a remote control. The keys are mapped in the driver which makes it difficult to customize. I'm not talking about the current problem with the mappings being hardcoded -- that could probably be solved without too much work. The problem I see with the mapping taking place in the driver, is that the interpretation of the key presses and releases should be application-specific. If I'm in MythTV, I want one interpretation. In Evolution, the same keypress should be interpreted differently. Firefox has a third set of mappings. Lircd solves this problem for me, while the event interface creates one static mapping. // J ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Very quiet around Nova-T 500
The strange thing is that modinfo does not say anything about a level 15 debug for the dvb_usb_dib0700 module. http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500#dvb_usb_dib0700 The debug value is a bit field, with each bit representing a different category. With all bits on (ie full debugging) the decimal value becomes 15. // J ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Very quiet around Nova-T 500
On Wed, 2008-02-20 at 10:36 +0100, Jonas Anden wrote: The strange thing is that modinfo does not say anything about a level 15 debug for the dvb_usb_dib0700 module. http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500#dvb_usb_dib0700 The debug value is a bit field, with each bit representing a different category. With all bits on (ie full debugging) the decimal value becomes 15. I should have guessed. Documented for poor souls with slow brains like me. Nico ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Very quiet around Nova-T 500
On Wed, 2008-02-20 at 08:38 +0100, Patrik Hansson wrote: On 2/19/08, Jonas Anden [EMAIL PROTECTED] wrote: There is not a lot being said about the Nova-T 500 the last week. Don´t know if that is a good (coders coding) or a bad (nothin happening) Or coders busy on other code, or coders who ran out of ideas, or coders enjoying life, etc. ..or just waiting for the problem to reappear ;( The trouble with the second tuner dying is tricky (for me) to isolate. As a workaround, enabling full debug (debug=15) on the dvb_usb_dib0700 module has made my system rock solid. I turned on debugging to try to isolate the issue, but with debugging enabled the problem does not appear (at least not on my system). I haven't really figured out *what* in the debug code is helping yet, but I still suspect that this is timing-related and the debug code simply slows things down a bit. Enabling debugging will put a whole lot of junk in your system log files, but at least the second tuner wont die on you. If you go this path, make sure your log rotation works as it should -- my weekly rotated logs are up to 130 MB in size ;) // J Could someone that knows what they are doing document that option on the wiki ? Corrected. The strange thing is that modinfo does not say anything about a level 15 debug for the dvb_usb_dib0700 module. http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500#dvb_usb_dib0700 Nico ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [patch] support for key repeat with dib0700 ir receiver
Il giorno mar, 19/02/2008 alle 22.14 +0100, Patrick Boettcher ha scritto: That indeed looks OK to my eyes. I have to admit that I never took a look into the IR-code from DiBcom... In any case, especially to that problem with unknown key code I think it is time to change the IR-behavior of the DVB-USB. My problem is, I don't know how. My naive idea would be, that the IR-code is reporting each key (as raw as possible) without mapping it to an event to the event interface and then someone, somewhere is interpreting it. Also forward any repeat-attribute. Those endless tables in a lot of dvb-usb drivers are annoying me, firstly because they are endless and huge, and secondly, they are never complete. If there is an adequate replacement from userspace (somehow loading key-lists to the event-layer or in the worst case, to the dvb-usb-framework) would be a good solution. Filippo, it seems you understand quite some thing around that. Do you know if what I'm saying is somehow possible? Patrick, your doubts are the same that I've felt when, a few days ago, I started looking at the dib0700 code. I thinked why the driver decode events and binds them to a keymap instead of passing them raw to a user space tool (lirc?)? This prevents me to easily add a custom keymap for commercial remotes or even add a keymap for the remotes I have. So my device can decode most of my remote controllers but I cannot use them without editing the kernel code from development branch. Later I understood the idea behind all this: as Nicolas said binding keypress to an event interface turns the remote into a common input interface that works everywhere without additional user space tools and without difficult per-app configurations. So I think that current behavior is somewhat sane even if it lacks of a simple system (from a user point of view) to add more keymaps or edit current ones. Please note that this behavior does not conflict with having different settings for different application, since this is achievable configuring lirc. Another problem (as far as I understood with a quick look at the code) is that each different driver, being written by different people, faces the whole thing in different ways. As you said almost each driver has its own keymaps and its own methods to present events to the input interface. For example I've seen some effort towards a unified system in dvb-usb-remote.c but dib0700 seems not to use it. Regarding ir-common (as Darren suggested), after a quick look it seems more a framework for decoding remote events but it cannot be extended to all the devices since many of them do the decoding stuff on their own outputting directly decoded data that only has to be binded to a keymap and to an event device. I think that all the drivers should output keypress decoded data in a common format to be passed to a common framework that binds it to common keymaps (better if user customizable in some way) and generates input events. I don't know yet how this could be done and maybe it involves some work rewriting the ir stuff. So I think in the meanwhile my patch could be merged (if you think it's good) waiting for this work to be done. I'll take a deeper look at the code but I don't know if I'm able to do this thing, I've read kernel code a few days ago for the very first time and I've written the patch just because a I needed the repeat feature :) Regards, Filippo ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [patch] support for key repeat with dib0700 ir receiver
On Wed, 2008-02-20 at 10:27 +0100, Filippo Argiolas wrote: So I think in the meanwhile my patch could be merged (if you think it's good) waiting for this work to be done. I second that. I'm all for the greater good and Doing Things The Right Way (tm), but could this effort be spawned in a separate process for grander things? I'll take a deeper look at the code but I don't know if I'm able to do this thing, I've read kernel code a few days ago for the very first time and I've written the patch just because a I needed the repeat feature :) Scratched an itch, heh? ;o) Nico ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [patch] support for key repeat with dib0700 ir receiver
2008/2/20, Nicolas Will [EMAIL PROTECTED]: Scratched an itch, heh? ;o) eheh, the best thing of free software is that you can always take the source and change it to reflect your needs :) ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] HVR-3000
[EMAIL PROTECTED] wrote: -To:linux-dvb@linuxtv.orgFrom:"TravelFactoryS.r.l."[EMAIL PROTECTED]Sentby:[EMAIL PROTECTED]Date:19-02-200821:14Subject:[linux-dvb]HVR-3000I've been out from the dvb scene for a while and now I'm building anewsystem.I had to buy an HVR-3000 hybrid system because it's the only DVB-Tcard I found available in Rome on PCI slot and the DVB-S was okinordertohaveanewinputNow I have this card... I tried on Suse 10.0, downloaded the kernelmodule I found somewhere... tried compiling but I got errors duetosomechangesinastructure.Imaytryonsuse10.3...perhapsitworksonthat...Nowthequestionsis:- where can I find informations to update my knowledge about DVBreception (I read hints about drivers rewritten for DVB-S2,multi-proto,andthelike...).- does anybody have a HVR-3000 actually working on a suse linux ?Whichversion?ThanksFrancesco___linux-dvbmailinglistlinux-dvb@linuxtv.orghttp://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvbHave you looked here: http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-3000?I have two HVR-4000working on OpenSuse 10.3 following these instructions: http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-4000with one small addition. I had to do make release before make and make install.Suse 10.0 is getting quite old. I think you will have better luck with 10.3.Jens ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [patch] support for key repeat with dib0700 ir receiver
On Wed, 2008-02-20 at 09:22 +0100, Filippo Argiolas wrote: Are you using this file for lircd.conf [http://linux.bytesex.org/v4l2/linux-input-layer-lircd.conf]? Where is this file coming from? I have something more limited (and that works for all keys) here: http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500#Remote_control Nico ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DiSEqC trouble with TT S-1500
P. van Gaans wrote: On 02/18/2008 02:04 PM, Doru Marin wrote: P. van Gaans wrote: On 02/16/2008 01:20 AM, P. van Gaans wrote: On 02/13/2008 09:21 PM, P. van Gaans wrote: On 02/13/2008 03:01 PM, Doru Marin wrote: Hi, Can you explain how you select those 4 positions ? DiSEqC commands or tone/voltage changes ? Also can you determine the input type of those positions (Hi/Low, H/V, etc) ? A scenario to see when and why that happens, would be more useful. P. van Gaans wrote: Hi, I've got a Technotrend S-1500 (if it matters: I use it with Kaffeine 0.8.3). It works mostly fine, but there's a strange problem. With my Spaun 4/1 DiSEqC switch (they cost approx 25-40 euro), I can only switch without trouble to position 1 and 2. If I tune directly to position 3 it won't lock. However, if I first tune to a channel on position 1 or 2 and try a channel on position 3 after that, it will work. Position 4 however is completely unreachable. On a standalone receiver, there's no trouble with the same cable. Now Spaun is a really expensive and respected brand. So their switches possibly work in a different way, because a cheap Maximum 4/1 switch works perfectly with the S-1500. Position 1, 2, 3 and 4 all work perfectly. I also did some dry testing indoors and it looks like a 7 euro Satconn 4/1 switch would also work fine, but a 17 euro Axing SPU 41-02 probably won't. I'm guessing this could be solved in stv0299.c but I'm not much of an expert. I took a look at the code but I'm not really sure what to do. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb I select them with Kaffeine. Hi/low and H/V doesn't matter. I tried upgrading to Kaffeine 0.8.5 but that doesn't make a difference. The scan application has the same issues. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb Nobody any ideas? If not, does anybody have some idea what the difference between position 1+2, pos 3 and pos 4 could be? I was thinking 1 and 2 might be working because of toneburst, but I don't think Kaffeine uses such a signal and that doesn't explain why pos 3 works if first tuning to 1 or 2 and 4 doesn't work at all. I've figured out a bit more. If I tune directly to postion 3, I get pos 1. Whenever I tune to pos 4, I get pos 2. I'll also ask people from Kaffeine as I'm not sure if the problem is in the application, driver or somewhere else. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb Hi, Strange scenario. You're not saying anything about input types and the switch type. Are you sure that are properly connected ? How the switch inputs are marked and from where you got the input signals ? Please elaborate, if you want a proper answer. I suggest to play with 'scandvb' from dvb-apps package instead of Kaffeine. Look into scanning results if the scanned channels match with what you wished to have on those positions. Hi, What do you mean with input type? Anyway, this is my config: Visiosat Bisat G3C for 19.2/28.2/23.5 + Triax 54cm for Hotbird 4 quad LNBs Spaun SAR 411F: A = Astra 19.2 B = Astra 28.2/Eurobird1 C = Astra 23.5 D = Hotbird Maximum 4/1: A = Astra 19.2 B = Astra 28.2/Eurobird1 C = Astra 23.5 D = Hotbird All works fine on a standalone so it is connected correctly. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb Hi, Ok, If I understood you correctly, you're talking about only plain DiSEqC switch, with no polarity/tone management. Polarity and tone switching are done by LNB's. Recently, I found a branded switch, which was unable to decode a DiSEqC commands while polarity was on horizontal (18V). Maybe is the same situation, maybe not. That's why I asked you to check the polarity/tone settings of the channels while switching to a different channel on a different satellite. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [patch] support for key repeat with dib0700 ir receiver
2008/2/20, Nicolas Will [EMAIL PROTECTED]: On Wed, 2008-02-20 at 09:22 +0100, Filippo Argiolas wrote: Are you using this file for lircd.conf [http://linux.bytesex.org/v4l2/linux-input-layer-lircd.conf]? Where is this file coming from? I've found it here: http://osdir.com/ml/hardware.lirc/2005-01/msg00120.html With the lircd.conf from irrecord every keypress was interpreted as double since it was listeing to both keypress and release events. For me worked good and it has almost every key supported by dev input. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Null pointer in dvb_device_open
Hi, I'm (still) developing a driver for a dvb-device, I'm making some progress, but I'm currently stuck at a null-pointer in dvb_device_open. The (relevant) dmesg-output: [ 484.858908] BUG: unable to handle kernel NULL pointer dereference at virtual address [ 484.858917] printing eip:[ 484.858919] f8cd360a[ 484.858921] *pde = [ 484.858924] Oops: [#1][ 484.858925] SMP [ 484.858928] Modules linked in: dvb_driver dvb_core ipv6 af_packet rfcomm l2cap bluetooth ppdev cpufreq_ondemand cpufreq_stats cpufreq_powersave cpufreq_userspace freq_table cpufreq_conservative sbs button ac container dock video battery sbp2 lp snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd soundcore parport_pc parport pcspkr snd_page_alloc shpchp pci_hotplug i2c_nforce2 i2c_core nvidia_agp agpgart dv1394 evdev ext3 jbd mbcache sg sd_mod ide_cd cdrom usbhid hid amd74xx ide_core sata_sil ohci1394 ieee1394 ata_generic libata scsi_mod forcedeth ehci_hcd ohci_hcd usbcore thermal processor fan fuse apparmor commoncap[ 484.858978] CPU:0[ 484.858979] EIP:0060:[f8cd360a]Not tainted VLI[ 484.858981] EFLAGS: 00010293 (2.6.22-14-generic #1)[ 484.858999] EIP is at dvb_device_open+0x3a/0x120 [dvb_core][ 484.859002] eax: eafcfc04 ebx: 76697264 ecx: f8ce6600 edx: 0003[ 484.859006] esi: edi: eafcfc0c ebp: eafcfc00 esp: ea123ec0[ 484.859009] ds: 007b es: 007b fs: 00d8 gs: 0033 ss: 0068[ 484.859012] Process scan (pid: 5981, ti=ea122000 task=ea766f90 task.ti=ea122000)[ 484.859015] Stack: ec9ae960 eb2aa8d0 0003 f8cd35d0 f8ce65a0 eb2aa8d0 c0183466 [ 484.859021]ec9ae960 0003 ec9ae960 eb2aa8d0 c01833c0 c017ec48 dff5ac00 [ 484.859028] e9a2c440 ec9ae960 ff9c ea123f30 0003 c017ee05 ec9ae960 [ 484.859034] Call Trace:[ 484.859038] [f8cd35d0] dvb_device_open+0x0/0x120 [dvb_core][ 484.859048] [c0183466] chrdev_open+0xa6/0x190[ 484.859058] [c01833c0] chrdev_open+0x0/0x190[ 484.859062] [c017ec48] __dentry_open+0xb8/0x1c0[ 484.859073] [c017ee05] nameidata_to_filp+0x35/0x40[ 484.859079] [c017ee60] do_filp_open+0x50/0x60[ 484.859085] [c02f20ea] schedule+0x2ca/0x890[ 484.859099] [c017eebe] do_sys_open+0x4e/0xf0[ 484.859105] [c01813b1] sys_write+0x41/0x70[ 484.859110] [c017ef9c] sys_open+0x1c/0x20[ 484.859114] [c01041d2] sysenter_past_esp+0x6b/0xa9[ 484.859128] ===[ 484.859129] Code: 50 34 a1 6c 66 ce f8 81 e2 ff ff 0f 00 89 54 24 08 eb 02 89 d8 8b 18 0f 18 03 90 3d 6c 66 ce f8 74 35 8d 68 fc 8b 75 0c 8d 78 08 8b 0e 0f 18 01 90 39 fe 74 de 8b 46 14 8b 55 00 c1 e0 04 0b 46 [ 484.859154] EIP: [f8cd360a] dvb_device_open+0x3a/0x120 [dvb_core] SS:ESP 0068:ea123ec0 Since dvb_device_open is a function of the dvb_core, I'm guessing the function is ok and there's something wrong with my part of the code. But, as far as I can see, I never explicitly call or register the function, so there's probably something wrong with the initialisation. I don't really see what can go wrong, so if any of you guys can give me some hints/tips to what I should pay extra attention, this is really appreciated. Greetings, Ben ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Null pointer in dvb_device_open
Sorry for the messed-up dmesg-output, hopefully this time it's better: [ 484.858908] BUG: unable to handle kernel NULL pointer dereference at virtual address [ 484.858917] printing eip: [ 484.858919] f8cd360a [ 484.858921] *pde = [ 484.858924] Oops: [#1] [ 484.858925] SMP [ 484.858928] Modules linked in: dvb_driver dvb_core ipv6 af_packet rfcomm l2cap bluetooth ppdev cpufreq_ondemand cpufreq_stats cpufreq_powersave cpufreq_userspace freq_table cpufreq_conservative sbs button ac container dock video battery sbp2 lp snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd soundcore parport_pc parport pcspkr snd_page_alloc shpchp pci_hotplug i2c_nforce2 i2c_core nvidia_agp agpgart dv1394 evdev ext3 jbd mbcache sg sd_mod ide_cd cdrom usbhid hid amd74xx ide_core sata_sil ohci1394 ieee1394 ata_generic libata scsi_mod forcedeth ehci_hcd ohci_hcd usbcore thermal processor fan fuse apparmor commoncap [ 484.858978] CPU:0 [ 484.858979] EIP:0060:[f8cd360a]Not tainted VLI [ 484.858981] EFLAGS: 00010293 (2.6.22-14-generic #1) [ 484.858999] EIP is at dvb_device_open+0x3a/0x120 [dvb_core] [ 484.859002] eax: eafcfc04 ebx: 76697264 ecx: f8ce6600 edx: 0003 [ 484.859006] esi: edi: eafcfc0c ebp: eafcfc00 esp: ea123ec0 [ 484.859009] ds: 007b es: 007b fs: 00d8 gs: 0033 ss: 0068 [ 484.859012] Process scan (pid: 5981, ti=ea122000 task=ea766f90 task.ti=ea122000) [ 484.859015] Stack: ec9ae960 eb2aa8d0 0003 f8cd35d0 f8ce65a0 eb2aa8d0 c0183466 [ 484.859021]ec9ae960 0003 ec9ae960 eb2aa8d0 c01833c0 c017ec48 dff5ac00 [ 484.859028]e9a2c440 ec9ae960 ff9c ea123f30 0003 c017ee05 ec9ae960 [ 484.859034] Call Trace: [ 484.859038] [f8cd35d0] dvb_device_open+0x0/0x120 [dvb_core] [ 484.859048] [c0183466] chrdev_open+0xa6/0x190 [ 484.859058] [c01833c0] chrdev_open+0x0/0x190 [ 484.859062] [c017ec48] __dentry_open+0xb8/0x1c0 [ 484.859073] [c017ee05] nameidata_to_filp+0x35/0x40 [ 484.859079] [c017ee60] do_filp_open+0x50/0x60 [ 484.859085] [c02f20ea] schedule+0x2ca/0x890 [ 484.859099] [c017eebe] do_sys_open+0x4e/0xf0 [ 484.859105] [c01813b1] sys_write+0x41/0x70 [ 484.859110] [c017ef9c] sys_open+0x1c/0x20 [ 484.859114] [c01041d2] sysenter_past_esp+0x6b/0xa9 [ 484.859128] === [ 484.859129] Code: 50 34 a1 6c 66 ce f8 81 e2 ff ff 0f 00 89 54 24 08 eb 02 89 d8 8b 18 0f 18 03 90 3d 6c 66 ce f8 74 35 8d 68 fc 8b 75 0c 8d 78 08 8b 0e 0f 18 01 90 39 fe 74 de 8b 46 14 8b 55 00 c1 e0 04 0b 46 [ 484.859154] EIP: [f8cd360a] dvb_device_open+0x3a/0x120 [dvb_core] SS:ESP 0068:ea123ec0 _ From: Ben Backx [mailto:[EMAIL PROTECTED] Sent: 20 February 2008 12:07 To: 'linux-dvb@linuxtv.org' Subject: Null pointer in dvb_device_open Hi, I'm (still) developing a driver for a dvb-device, I'm making some progress, but I'm currently stuck at a null-pointer in dvb_device_open. The (relevant) dmesg-output: [ 484.858908] BUG: unable to handle kernel NULL pointer dereference at virtual address [ 484.858917] printing eip:[ 484.858919] f8cd360a[ 484.858921] *pde = [ 484.858924] Oops: [#1][ 484.858925] SMP [ 484.858928] Modules linked in: dvb_driver dvb_core ipv6 af_packet rfcomm l2cap bluetooth ppdev cpufreq_ondemand cpufreq_stats cpufreq_powersave cpufreq_userspace freq_table cpufreq_conservative sbs button ac container dock video battery sbp2 lp snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd soundcore parport_pc parport pcspkr snd_page_alloc shpchp pci_hotplug i2c_nforce2 i2c_core nvidia_agp agpgart dv1394 evdev ext3 jbd mbcache sg sd_mod ide_cd cdrom usbhid hid amd74xx ide_core sata_sil ohci1394 ieee1394 ata_generic libata scsi_mod forcedeth ehci_hcd ohci_hcd usbcore thermal processor fan fuse apparmor commoncap[ 484.858978] CPU:0[ 484.858979] EIP:0060:[f8cd360a]Not tainted VLI[ 484.858981] EFLAGS: 00010293 (2.6.22-14-generic #1)[ 484.858999] EIP is at dvb_device_open+0x3a/0x120 [dvb_core][ 484.859002] eax: eafcfc04 ebx: 76697264 ecx: f8ce6600 edx: 0003[ 484.859006] esi: edi: eafcfc0c ebp: eafcfc00 esp: ea123ec0[ 484.859009] ds: 007b es: 007b fs: 00d8 gs: 0033 ss: 0068[ 484.859012] Process scan (pid: 5981, ti=ea122000 task=ea766f90 task.ti=ea122000)[ 484.859015] Stack: ec9ae960 eb2aa8d0 0003 f8cd35d0 f8ce65a0 eb2aa8d0 c0183466 [ 484.859021]ec9ae960 0003 ec9ae960 eb2aa8d0 c01833c0 c017ec48 dff5ac00 [ 484.859028] e9a2c440 ec9ae960 ff9c
Re: [linux-dvb] Very quiet around Nova-T 500
I have now set the debug to 15 and will test this tonight. On 2/20/08, Nicolas Will [EMAIL PROTECTED] wrote: On Wed, 2008-02-20 at 10:36 +0100, Jonas Anden wrote: The strange thing is that modinfo does not say anything about a level 15 debug for the dvb_usb_dib0700 module. http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500#dvb_usb_dib0700 The debug value is a bit field, with each bit representing a different category. With all bits on (ie full debugging) the decimal value becomes 15. I should have guessed. Documented for poor souls with slow brains like me. Nico ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DiSEqC trouble with TT S-1500
On 02/20/2008 10:48 AM, Doru Marin wrote: P. van Gaans wrote: On 02/18/2008 02:04 PM, Doru Marin wrote: P. van Gaans wrote: On 02/16/2008 01:20 AM, P. van Gaans wrote: On 02/13/2008 09:21 PM, P. van Gaans wrote: On 02/13/2008 03:01 PM, Doru Marin wrote: Hi, Can you explain how you select those 4 positions ? DiSEqC commands or tone/voltage changes ? Also can you determine the input type of those positions (Hi/Low, H/V, etc) ? A scenario to see when and why that happens, would be more useful. P. van Gaans wrote: Hi, I've got a Technotrend S-1500 (if it matters: I use it with Kaffeine 0.8.3). It works mostly fine, but there's a strange problem. With my Spaun 4/1 DiSEqC switch (they cost approx 25-40 euro), I can only switch without trouble to position 1 and 2. If I tune directly to position 3 it won't lock. However, if I first tune to a channel on position 1 or 2 and try a channel on position 3 after that, it will work. Position 4 however is completely unreachable. On a standalone receiver, there's no trouble with the same cable. Now Spaun is a really expensive and respected brand. So their switches possibly work in a different way, because a cheap Maximum 4/1 switch works perfectly with the S-1500. Position 1, 2, 3 and 4 all work perfectly. I also did some dry testing indoors and it looks like a 7 euro Satconn 4/1 switch would also work fine, but a 17 euro Axing SPU 41-02 probably won't. I'm guessing this could be solved in stv0299.c but I'm not much of an expert. I took a look at the code but I'm not really sure what to do. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb I select them with Kaffeine. Hi/low and H/V doesn't matter. I tried upgrading to Kaffeine 0.8.5 but that doesn't make a difference. The scan application has the same issues. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb Nobody any ideas? If not, does anybody have some idea what the difference between position 1+2, pos 3 and pos 4 could be? I was thinking 1 and 2 might be working because of toneburst, but I don't think Kaffeine uses such a signal and that doesn't explain why pos 3 works if first tuning to 1 or 2 and 4 doesn't work at all. I've figured out a bit more. If I tune directly to postion 3, I get pos 1. Whenever I tune to pos 4, I get pos 2. I'll also ask people from Kaffeine as I'm not sure if the problem is in the application, driver or somewhere else. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb Hi, Strange scenario. You're not saying anything about input types and the switch type. Are you sure that are properly connected ? How the switch inputs are marked and from where you got the input signals ? Please elaborate, if you want a proper answer. I suggest to play with 'scandvb' from dvb-apps package instead of Kaffeine. Look into scanning results if the scanned channels match with what you wished to have on those positions. Hi, What do you mean with input type? Anyway, this is my config: Visiosat Bisat G3C for 19.2/28.2/23.5 + Triax 54cm for Hotbird 4 quad LNBs Spaun SAR 411F: A = Astra 19.2 B = Astra 28.2/Eurobird1 C = Astra 23.5 D = Hotbird Maximum 4/1: A = Astra 19.2 B = Astra 28.2/Eurobird1 C = Astra 23.5 D = Hotbird All works fine on a standalone so it is connected correctly. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb Hi, Ok, If I understood you correctly, you're talking about only plain DiSEqC switch, with no polarity/tone management. Polarity and tone switching are done by LNB's. Recently, I found a branded switch, which was unable to decode a DiSEqC commands while polarity was on horizontal (18V). Maybe is the same situation, maybe not. That's why I asked you to check the polarity/tone settings of the channels while switching to a different channel on a different satellite. That's right, no multiswitches or something like that. The last time I checked (a while ago), the Spaun was still completely working on my standalones. But as I figured out yesterday, something is wrong with that now. The standalones don't see D (Hotbird) anymore either. So I'm first going to fix that. Trying to switch from Flaunt (V) to 4fun.tv (V) doesn't work either, so it's not the same problem I guess. ___ linux-dvb mailing list linux-dvb@linuxtv.org
Re: [linux-dvb] [patch] support for key repeat with dib0700 ir receiver
On Feb 20, 2008 5:27 PM, Filippo Argiolas [EMAIL PROTECTED] wrote: Il giorno mer, 20/02/2008 alle 09.22 +0100, Filippo Argiolas ha scritto: Il giorno mer, 20/02/2008 alle 06.10 +0900, Matthew Vermeulen ha scritto: Hi all... I'm seeing exactly the same problems everyone else is (log flooding etc) except that I can't seem to get any keys picked by lirc or /dev/input/event7 at all... Are you sure that the input device is receiving the events? Did you try evtest /dev/input/event7? Is LIRC properly configured? Are you using this file for lircd.conf [http://linux.bytesex.org/v4l2/linux-input-layer-lircd.conf]? Does irw catch some event? I forgot to say to not use irrecord with dev/input driver since it's thinked to record raw events from remotes and doesn't work with input devices (usually it ends up with a lircd.conf file that interprets key press and release as separated events doubling each event). Just use the proper input-layer-lircd.conf. I've got that file all set up, my hardware.conf for lirc is pasted below: # /etc/lirc/hardware.conf # #Chosen Remote Control REMOTE=Compro Videomate U500 REMOTE_MODULES= REMOTE_DRIVER=devinput REMOTE_DEVICE=/dev/input/event7 REMOTE_LIRCD_CONF=/etc/lirc/lircd.conf REMOTE_LIRCD_ARGS= #Chosen IR Transmitter TRANSMITTER=None TRANSMITTER_MODULES= TRANSMITTER_DRIVER= TRANSMITTER_DEVICE= TRANSMITTER_LIRCD_CONF= TRANSMITTER_LIRCD_ARGS= #Enable lircd START_LIRCD=true #Don't start lircmd even if there seems to be a good config file #START_LIRCMD=false #Try to load appropriate kernel modules LOAD_MODULES=true # Default configuration files for your hardware if any LIRCMD_CONF= #Forcing noninteractive reconfiguration #If lirc is to be reconfigured by an external application #that doesn't have a debconf frontend available, the noninteractive #frontend can be invoked and set to parse REMOTE and TRANSMITTER #It will then populate all other variables without any user input #If you would like to configure lirc via standard methods, be sure #to leave this set to false FORCE_NONINTERACTIVE_RECONFIGURATION=false START_LIRCMD= My /etc/lirc/lircd.conf contains the contents of the lircd.conf file you linked to. Like I said previously, the only way I know the thing is seeing keypresses is by looking at dmesg or the syslog - evtest and irw pick up nothing, nor does xev or anything else I know to test with. I think lirc is properly configured, insofar as i can change the device to point to my multimedia keyboard using the devinput driver which can then be picked up by lirc... I do know the actual tuner is receiving the remote keypresses because of the changes to the codes listed in syslog... Hope this helps you (help me ;) ) Cheers, Matt -- Matthew Vermeulen http://www.matthewv.id.au/ MatthewV @ irc.freenode.net ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Yuan EC372S (STK7700D based device)
Albert Comerma wrote: It seems ok. Could you test a scan with kaffeine instead of looking for a specific location? And if you do so it reports signal strenght? Kaffeine reports 100% signal strength. There must be some setting wrong in the driver. Tuner locks to the correct frequency but signal from uner to demodulator could be wrong and thats why PID-filter timeouts. Even bad, I cannot snoop it in windows because I did not find all the required Windows XP drivers for my brand new laptop. Laptop is only computer I have ExpressCard slot... By the way, what does it mean moi and moikka? Hello in finish? yes :) regards Antti -- http://palosaari.fi/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [patch] support for key repeat with dib0700 ir receiver
On Feb 20, 2008 4:54 PM, Nicolas Will [EMAIL PROTECTED] wrote: On Wed, 2008-02-20 at 16:39 +0900, Matthew Vermeulen wrote: On Feb 20, 2008 7:09 AM, Nicolas Will [EMAIL PROTECTED] wrote: On Wed, 2008-02-20 at 06:10 +0900, Matthew Vermeulen wrote: Hi all... I'm seeing exactly the same problems everyone else is (log flooding etc) except that I can't seem to get any keys picked by lirc or /dev/input/event7 at all... Would this patch help in this case? It would help with the flooding, most probably, though there was a patch for that available before. As for LIRC not picking up the event, I would be tempted to say no, it won't help. Are you certain that your LIRC is configured properly? Are you certain that your event number is the right one? Nico I believe so... in so far as I can tell... I sent an email to this list about a week ago describing my problems, but there was no response. (subject: Compro Videomate U500). I've copied it below: Hi all, I've still been trying to get the inluded remote with my USB DVB-T Tuner working. It's a Compro Videomate U500 - it useses the dibcom 7000 chipset. After upgrading to Ubuntu 8.04 (hardy) I can now see the remote when I do a cat /proc/bus/input/devices: I: Bus=0003 Vendor=185b Product=1e78 Version=0100 N: Name=IR-receiver inside an USB DVB receiver P: Phys=usb-:00:02.1-4/ir0 S: Sysfs=/devices/pci:00/ :00:02.1/usb1/1-4/input/input7 U: Uniq= H: Handlers=kbd event7 B: EV=3 B: KEY=10afc332 2842845 0 0 0 4 80018000 2180 4801 9e96c0 0 800200 ffc Weird. You went through all this, I guess: http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500#Remote_control And you are running a recent v4l-dvb tree, I assume. However, I get now output running irrecord: I was never too lucky with irrecord on my system, IIRC. Nico Ok - just thought I'd try the patch on the latest tree and see what happens... as expected, it put an end to the syslog flooding - but nothing really has improved... I still see a single error line in the syslog every time I press a key - so obviously the kernel is seeing something happen, but deciding it's unknown and not taking it any further. Something must be wrong with some mappings somewhere.. :S Here's the syslog output anyway - there is one line for every key press: Feb 20 22:07:07 matthew-desktop kernel: [38161.388548] dib0700: Unknown remote controller key: 12 7E 1 0 Feb 20 22:07:09 matthew-desktop kernel: [38162.678839] dib0700: Unknown remote controller key: 18 7C 1 0 Feb 20 22:07:10 matthew-desktop kernel: [38162.906413] dib0700: Unknown remote controller key: 18 7C 1 0 Feb 20 22:07:14 matthew-desktop kernel: [38165.183338] dib0700: Unknown remote controller key: 1C 4D 1 0 Feb 20 22:07:18 matthew-desktop kernel: [38167.156040] dib0700: Unknown remote controller key: 1F 7D 1 0 Feb 20 22:07:21 matthew-desktop kernel: [38168.598632] dib0700: Unknown remote controller key: 19 43 1 0 This is very annoying because it seems that polling the syslog every 150ms might even give you something if you could work it out ;) Anyway.. any ideas where to now...? Cheers, Matt -- Matthew Vermeulen http://www.matthewv.id.au/ MatthewV @ irc.freenode.net ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [patch] support for key repeat with dib0700 ir receiver
Sorry forgot to reply to teh list On Feb 20, 2008 10:34 PM, Filippo Argiolas [EMAIL PROTECTED] wrote: 2008/2/20, Matthew Vermeulen [EMAIL PROTECTED]: Ok - just thought I'd try the patch on the latest tree and see what happens... as expected, it put an end to the syslog flooding - but nothing really has improved... I still see a single error line in the syslog every time I press a key - so obviously the kernel is seeing something happen, but deciding it's unknown and not taking it any further. Something must be wrong with some mappings somewhere.. :S Here's the syslog output anyway - there is one line for every key press: Feb 20 22:07:07 matthew-desktop kernel: [38161.388548] dib0700: Unknown remote controller key: 12 7E 1 0 Feb 20 22:07:09 matthew-desktop kernel: [38162.678839] dib0700: Unknown remote controller key: 18 7C 1 0 Feb 20 22:07:10 matthew-desktop kernel: [38162.906413] dib0700: Unknown remote controller key: 18 7C 1 0 Feb 20 22:07:14 matthew-desktop kernel: [38165.183338] dib0700: Unknown remote controller key: 1C 4D 1 0 Feb 20 22:07:18 matthew-desktop kernel: [38167.156040] dib0700: Unknown remote controller key: 1F 7D 1 0 Feb 20 22:07:21 matthew-desktop kernel: [38168.598632] dib0700: Unknown remote controller key: 19 43 1 0 This is very annoying because it seems that polling the syslog every 150ms might even give you something if you could work it out ;) Anyway.. any ideas where to now...? Ok, I didn't take a look at your previous messages, so I was thinking you were trying to make a hauppauge remote work. As far as I can see from this output and from dib0700 code your remote is not supported, hence there is no keymap hardcoded for it, hence the drivers outputs unknow key since it really doesn't know what to do with the key received. Looking at your log it seems even that your remote is not an rc5 standard one since the toggle bit is always set to 1. Please try to press the same key many times (do not hold it down) and look if the unknown key is always the same and if the 3rd value changes alternatively from 0 to 1. If everything is ok you can start to take note of the values outputed by your keys and try to add a keymap on your own or send the results here. Note that if toggle bit is not working properly it the repeat feature would not work perfectly. I cannot do anything more since I don't have that remote control to make some test. Filippo Hmm... Maybe you can make more sense of this - the is the result of pressing the same key repeatedly very rapidly (ie as fast as i can ;) ) Feb 20 22:39:48 matthew-desktop kernel: [39332.403671] dib0700: Unknown remote controller key: 13 7E 1 0 Feb 20 22:39:48 matthew-desktop kernel: [39332.555469] dib0700: Unknown remote controller key: 13 7E 1 0 Feb 20 22:39:48 matthew-desktop kernel: [39332.631930] dib0700: Unknown remote controller key: 1F A 1 0 Feb 20 22:39:48 matthew-desktop kernel: [39332.707392] dib0700: Unknown remote controller key: F 39 0 0 Feb 20 22:39:48 matthew-desktop kernel: [39332.783229] dib0700: Unknown remote controller key: 13 7E 1 0 Feb 20 22:39:49 matthew-desktop kernel: [39332.859565] dib0700: Unknown remote controller key: 13 7E 1 0 Feb 20 22:39:49 matthew-desktop kernel: [39333.010863] dib0700: Unknown remote controller key: 13 7E 1 0 Feb 20 22:39:49 matthew-desktop kernel: [39333.086825] dib0700: Unknown remote controller key: 13 7E 1 0 Feb 20 22:39:49 matthew-desktop kernel: [39333.238810] dib0700: Unknown remote controller key: 13 7E 1 0 Feb 20 22:39:49 matthew-desktop kernel: [39333.315022] dib0700: Unknown remote controller key: 13 7E 1 0 Feb 20 22:39:50 matthew-desktop kernel: [39333.390859] dib0700: Unknown remote controller key: 13 7E 1 0 Feb 20 22:39:50 matthew-desktop kernel: [39333.542656] dib0700: Unknown remote controller key: 13 7E 1 0 Feb 20 22:39:50 matthew-desktop kernel: [39333.618559] dib0700: Unknown remote controller key: 13 7E 1 0 Feb 20 22:39:50 matthew-desktop kernel: [39333.694392] dib0700: Unknown remote controller key: 13 7E 1 0 Feb 20 22:39:51 matthew-desktop kernel: [39333.846254] dib0700: Unknown remote controller key: 13 7E 1 0 Feb 20 22:39:51 matthew-desktop kernel: [39333.922152] dib0700: Unknown remote controller key: 13 7E 1 0 Feb 20 22:39:51 matthew-desktop kernel: [39333.998053] dib0700: Unknown remote controller key: 13 7E 1 0 Feb 20 22:39:51 matthew-desktop kernel: [39334.149849] dib0700: Unknown remote controller key: 13 7E 1 0 Feb 20 22:39:51 matthew-desktop kernel: [39334.225750] dib0700: Unknown remote controller key: 13 7E 1 0 Feb 20 22:39:51 matthew-desktop kernel: [39334.301647] dib0700: Unknown remote controller key: 1F A 1 0 Feb 20 22:39:52 matthew-desktop kernel: [39334.453384] dib0700: Unknown remote controller key: 13 7E 1 0 Feb 20 22:39:52 matthew-desktop kernel: [39334.529281] dib0700: Unknown remote controller key: 13 7E 1 0 Feb 20 22:39:52 matthew-desktop kernel: [39334.681017]
Re: [linux-dvb] [patch] support for key repeat with dib0700 ir receiver
On Wed, 2008-02-20 at 21:36 +0900, Matthew Vermeulen wrote: I've got that file all set up, my hardware.conf for lirc is pasted below: I'm running Ubuntu Gutsy and my /etc/lirc/hardware.conf has wildly different variable names. See what I have here: http://www.youplala.net/~will/htpc/LIRC/ You are running Hardy, but I would't expect conf files to change so dramatically. I may be wrong, so I'll check. Ah, yes they are... oh well, I'm wrong. # /etc/lirc/hardware.conf # #Chosen Remote Control REMOTE=Compro Videomate U500 REMOTE_MODULES= REMOTE_DRIVER=devinput shouldn't that be dev/input, instead? Nico ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] drivers
hi am new to this site. im having NOVA-S-Plus card, and re i dont know how to download the drivers for this,can u tell me the sites. Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [patch] support for key repeat with dib0700 ir receiver
Il giorno mer, 20/02/2008 alle 22.43 +0900, Matthew Vermeulen ha
scritto:
Feb 20 22:39:53 matthew-desktop kernel: [39334.832815] dib0700:
Unknown remote controller key: 13 7E 1 0
Feb 20 22:39:53 matthew-desktop kernel: [39334.908277] dib0700:
Unknown remote controller key: 13 7E 1 0
Feb 20 22:39:53 matthew-desktop kernel: [39335.060139] dib0700:
Unknown remote controller key: 13 7E 1 0
Feb 20 22:39:53 matthew-desktop kernel: [39335.136473] dib0700:
Unknown remote controller key: 13 7E 1 0
Feb 20 22:39:53 matthew-desktop kernel: [39335.211810] dib0700:
Unknown remote controller key: 13 7E 1 0
Feb 20 22:39:54 matthew-desktop kernel: [39335.364108] dib0700:
Unknown remote controller key: 13 7E 1 0
Not sure if that's what we were hoping for...
It seems that your remote does not use the toggle bit. I don't know why
since afaik it is a feature of the rc5 protocol.
By the way you can try to make some test writing the keymap on your own.
Just edit dib0700_devices.c about at line 400, look at the other keymaps
to have a model:
for example if the key you logged was the UP key you have to add a line
like:
{ 0x13, 0x7E, KEY_UP },
and so on for the other keys, after that see if the keymap works with
evtest.
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] SkyStar rev 2.8A driver?
Hi, 1: Do you need any help or support? emailing, asking from TechniSat or anybody else? 2: Most of this card components are now supported under linux, such as frontend from Conexant, so why you have NDA problems? 3: You said OpenSource driver is not insight. Do you mean they plan to give a closed source dirver for linux? On Wed, Feb 20, 2008 at 12:52 AM, Patrick Boettcher [EMAIL PROTECTED] wrote: Hi, an OpenSource driver is not in sight for that card. There are some NDA problems... I will see what I can do. Patrick. On Sat, 16 Feb 2008, Ali H.M. Hoseini wrote: On 2/14/08, CityK [EMAIL PROTECTED] wrote: Ali H.M. Hoseini wrote: Hi, I searched linuxtv.org http://linuxtv.org/ mailing list archive about SkyStar2 rev2.8A driver, or any suggestion, but I found nothing. The 2.6.22 kernel initialize B2C2 chip itself, but it could not identify the frontend for card. The chips used in this card for frontend are conexant cx24123 and cx24113 . I tried to load cx24123 module exists in the kernel, but later I found it is not defined for b2c2-flexcop module to use it, and hence it is not useful. Could anybody help me? See: http://marc.info/?l=linux-dvbm=120042808124927w=2 I took a look at that link, but it does not have any useful information, such as release time, or anything else. Anybody knows when support for this card release? I bought one of this cards and I have to use windows until I find linux support for it. Somebody helps me! I really need to use my SkyStar2 rev 2.8A under linux! ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [patch] support for key repeat with dib0700 ir receiver
On Wed, 2008-02-20 at 15:15 +0100, Filippo Argiolas wrote:
It seems that your remote does not use the toggle bit. I don't know
why
since afaik it is a feature of the rc5 protocol.
By the way you can try to make some test writing the keymap on your
own.
Just edit dib0700_devices.c about at line 400, look at the other
keymaps
to have a model:
for example if the key you logged was the UP key you have to add a
line
like:
{ 0x13, 0x7E, KEY_UP },
and so on for the other keys, after that see if the keymap works with
evtest.
Between this discussion and some wiki rework I have been doing today on
all dib0700 equipped hardware, i am starting to understand where Patrick
was coming from regarding all that hard-coding of specific remote
keys...
Nico
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] RTL2831U kernel driver success
Just to post that I have total success with the RTL2831U kernel drivers and watching with Kaffeine. I took the source from realtek, and added a makefile so it will compile as a standalone. This needed a bit of dirtyness in the form of copying several files that the modules depend upon from the kernel source to the module directory. It still throws up a few warnings when compiling, mostly to do with redefining things (to be expected really) and unsigned constants, so the realtek code needs some clean up. I am using Kubuntu Gutsy. I have put a .txt file in the Doc directory showing what is needed so it can be easily changed for other kernels. The package is availble from here. http://coronach.adsl24.co.uk/code/rtl2831u_dvb-usb_v0.0.1.tar.bz2 Just unpack, make, sudo make install and it should work on Ubuntu Gutsy as is. I have tested it on 2 Kubuntu i386 systems and it works. I know this is a nasty hack, but it works and the quality and responsiveness seems a lot better that it does in windows. I would be interested if anyone else gets this to work. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Very quiet around Nova-T 500
Hi Nico, Am Mittwoch, den 20.02.2008, 07:12 + schrieb Nicolas Will: On Wed, 2008-02-20 at 01:12 +0100, hermann pitton wrote: Now stop that logging madness and get back to work! ... ;o) This is a rather comical situation, though... The debugging tool is providing a rather unexpected and unwelcomed fix. Nico Hi, no, it is not. It is well known! Timings are very critical on almost all drivers. We hold breath on almost everything coming down from above, nobody has the ability, or whom should ever want it, to test all possible side effects on all supported devices ... That something breaks is very common, and that others have to give the plumbers, is nothing new. To stay fair, it mostly has a good reason, and if there are some remaining ticks left, you might get it adjusted, but ... On the other side it is the same ... May post may have sounded offensive, apparently. Sorry about that, my intentions were on the lighter sides of life. Nico nothing offending at all, did enjoy your above comment :) and like your active support for others. It is just not totally unexpected that high debug levels can have some spin-off and I'm curious about it. Cheers, Hermann ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Yuan EC372S (STK7700D based device)
Albert Comerma wrote: Is it a coincidence, but there have been updates in kaffeine (0.8.5-35.pm http://0.8.5-35.pm) (libxine1, libxine1-dvb version: 1.1.9-1-0.pm http://1.1.9-1-0.pm , for example) and since then everything works. To be confirmed in time. So please try if you can use this versions (or newer) and let me know. xinelib is even newer and Kaffeine version is same. I doubt that xinelib and Kaffeine has any effect. It should lock and find PIDs even without xinelib when using dvb-apps tools. xinelib and Kaffeine has only effect when viewing picture. regards Antti -- http://palosaari.fi/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Any idea about my CI error ?
Hi, For my S2-3200, I've done : # modprobe dvb-core cam_debug=255 [thank you Manu ;-)] # modprobe stb6100 # modprobe stb0899 # modprobe lnbp21 # modprobe budget-c and I have some more information about my CI : saa7146: register extension 'budget_ci dvb'. ACPI: PCI Interrupt :05:01.0[A] - GSI 22 (level, low) - IRQ 22 saa7146: found saa7146 @ mem c20001046c00 (revision 1, irq 22) (0x13c2,0x1019). saa7146 (0): dma buffer size 192512 DVB: registering new adapter (TT-Budget S2-3200 PCI) adapter has MAC addr = 00:d0:5c:0b:a5:8b input: Budget-CI dvb ir receiver saa7146 (0) as /class/input/input9 dvb_ca_en50221_init budget_ci: CI interface initialised CAMCHANGE IRQ slot:0 change_type:1 dvb_ca_en50221_thread_wakeup dvb_ca_en50221_thread stb0899_write_regs [0xf1b6]: 02 stb0899_write_regs [0xf1c2]: 00 stb0899_write_regs [0xf1c3]: 00 _stb0899_read_reg: Reg=[0xf000], data=81 stb0899_get_dev_id: ID reg=[0x81] stb0899_get_dev_id: Device ID=[8], Release=[1] _stb0899_read_s2reg Device=[0xf3fc], Base address=[0x0400], Offset=[0xf334], Data=[0x444d4431] _stb0899_read_s2reg Device=[0xf3fc], Base address=[0x0400], Offset=[0xf33c], Data=[0x0001] stb0899_get_dev_id: Demodulator Core ID=[DMD1], Version=[1] _stb0899_read_s2reg Device=[0xfafc], Base address=[0x0800], Offset=[0xfa2c], Data=[0x46454331] _stb0899_read_s2reg Device=[0xfafc], Base address=[0x0800], Offset=[0xfa34], Data=[0x0001] stb0899_get_dev_id: FEC Core ID=[FEC1], Version=[1] stb0899_attach: Attaching STB0899 stb6100_attach: Attaching STB6100 DVB: registering frontend 0 (STB0899 Multistandard)... dvb_ca adaptor 0: PC card did not respond :( Does anyone have an idea about this error ? Thank you. David. signature.asc Description: PGP signature ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Scan patched...
Hi again, I'm trying to compile scan. First, I've downloaded dvb-apps : # hg clone http://linuxtv.org/hg/dvb-apps Then, I've downloaded scan package from : http://jusst.de/manu/scan.tar.bz2 I've replaced dvb-apps/util/scan with files from this package. I've added the 'include' folder from multiproto to the dvb-apps folder. Then, in dvb-apps/util/scan, I've done : # make clean # make and I have this error : perl section_generate.pl atsc_psip_section.pl CC scan.o scan.c:449: warning: unused parameter ‘buf’ scan.c: In function ‘tune_to_transponder’: scan.c:1676: error: storage size of ‘fe_info1’ isn’t known scan.c:1679: error: invalid application of ‘sizeof’ to incomplete type ‘struct dvbfe_info’ scan.c:1682: error: ‘DVBFE_DELSYS_DVBS’ undeclared (first use in this function) scan.c:1682: error: (Each undeclared identifier is reported only once scan.c:1682: error: for each function it appears in.) scan.c:1684: error: ‘DVBFE_DELSYS_DVBS2’ undeclared (first use in this function) scan.c:1686: error: ‘DVBFE_GET_INFO’ undeclared (first use in this function) scan.c:1697: error: ‘DVBFE_DELSYS_DSS’ undeclared (first use in this function) scan.c:1676: warning: unused variable ‘fe_info1’ make: *** [scan.o] Erreur 1 To be honest, I'm lost... Do you have any idea ? Thank you. David. signature.asc Description: PGP signature ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] HVR-1800 status
Barry Quiel wrote: I haven't seen any code updates to support the analog portion of the HVR-1800 in a few weeks. Is it still being worked on? Not recently, the current tree is under ~stoth. The encoder is working, the tuner is tuning, everything looks OK. I need to cleanup the ioctl handling. - Steve ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] FireDTV driver status?
Hi all, is there any development for a FireDTV driver? Best regards Mikael Carlsson ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [patch] support for key repeat with dib0700 ir receiver
On Thu, Feb 21, 2008 at 7:57 AM, Matthew Vermeulen [EMAIL PROTECTED]
wrote:
On Wed, Feb 20, 2008 at 11:15 PM, Filippo Argiolas
[EMAIL PROTECTED] wrote:
Il giorno mer, 20/02/2008 alle 22.43 +0900, Matthew Vermeulen ha
scritto:
Feb 20 22:39:53 matthew-desktop kernel: [39334.832815] dib0700:
Unknown remote controller key: 13 7E 1 0
Feb 20 22:39:53 matthew-desktop kernel: [39334.908277] dib0700:
Unknown remote controller key: 13 7E 1 0
Feb 20 22:39:53 matthew-desktop kernel: [39335.060139] dib0700:
Unknown remote controller key: 13 7E 1 0
Feb 20 22:39:53 matthew-desktop kernel: [39335.136473] dib0700:
Unknown remote controller key: 13 7E 1 0
Feb 20 22:39:53 matthew-desktop kernel: [39335.211810] dib0700:
Unknown remote controller key: 13 7E 1 0
Feb 20 22:39:54 matthew-desktop kernel: [39335.364108] dib0700:
Unknown remote controller key: 13 7E 1 0
Not sure if that's what we were hoping for...
It seems that your remote does not use the toggle bit. I don't know why
since afaik it is a feature of the rc5 protocol.
By the way you can try to make some test writing the keymap on your own.
Just edit dib0700_devices.c about at line 400, look at the other keymaps
to have a model:
for example if the key you logged was the UP key you have to add a line
like:
{ 0x13, 0x7E, KEY_UP },
and so on for the other keys, after that see if the keymap works with
evtest.
Ok thanks I'll give that a shot and see what happens :)
Thanks a lot
Cheers,
Matt
--
Matthew Vermeulen
http://www.matthewv.id.au/
MatthewV @ irc.freenode.net
Ok I just tried this with a few keys - and I know have volume control
working on the remote... :D :D
Thanks so much... will let you know how the rest of it turns out!
Cheers,
Matt
--
Matthew Vermeulen
http://www.matthewv.id.au/
MatthewV @ irc.freenode.net
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Driver source for Freecom DVB-T (with usb id 14aa:0160) v0.0.2 works
Great. I've compiled it, and found some compilation problems. I've fixed those and put them into a zipped patch for the v4l hg management system. I've sent it to a couple of people, but did not yet include some copyright message into it. Does anybody know how to put it onto the v4l site ? Thanks a lot Andy ! ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Avermedia PCIe combo tv card
I was woundering on the status of support of the Avermedia PCIe oem tv card. it's probly only used in gateway computers. no rush just woundering. thanx ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
