Re: [linux-dvb] Future of Multiproto
Johannes Stezenbach wrote: On Fri, Oct 12, 2007, Manu Abraham wrote: Johannes Stezenbach wrote: Does that mean that Manu has no intentions to get his multiproto API changes merged? It will be merged When? Why hasn't it been merged months ago when HVR4000 worked? HVR4000 was struggling even recently howto handle pilots, because it had a hard time trying to figure out how pilots worked. Eventually, the implementation from the STB0899 had to be copied to the same, for it to work. The reason being CX24116 being mostly RE'd, AFAIH. (If so, then wtf was the point of doing them and keep everyone waiting? But I guess the DVB API update thread meant he isn't happy with it anymore.)) As i wrote, there are more things in the S2 specification, also currently stuff like proper statistics cannot be done for example As I tried to tell you in one of my replies in the DVB API update thread statistics is totally independent of DVB-S2. And the more things were not spelled out in detail by you -- and why don't you just fix the API if you know something is missing, instead of saying something's missing, can't merge yet? Please, Just look at the changesets for the same. I just can't understand why you were dragging this out so long, usually I would expect the desire of any developer is to get the code merged ASAP. With a working HVR4000 driver you could've FYI, the STB0899 driver is much older than the HVR4000 driver, it has been delayed because of 1) too much noise on the ML (you had bit much to do with it) 2) The feedback that resulted from the discussions on the ML, were not sufficient for a complete API, eventually STM chipped in, was a lot of struggle at my side too. got the API and dvb-core changes merged months ago -- which would've allowed you to merge the STB0899 driver in CONFIG_EXPERIMENTAL status to expose it to a wider audience if you'd wanted to. Your earlier statements resulted thus: * go experimental * no experimental * go experimental Looks like some square wave function. Are harmonics expected ? Instead you seem to have the desire to work on your private branch forever, adding patch upon patch to make it as big and important as possible. Can you please point to the changesets which cause you to mention adding patch upon patch to make it as big and important as possible ? If you can't point that, it is fairly evident that you are blindly accusing me and thereby blurting nonsense and sparking politics. Any not caring at all that you block Steve's work as a consequence. hmm.. accusations again. ATM, Steve was/is prejudiced because of something else. I asked you for your plans in this thread but I didn't get an answer. I had mentioned the same earlier (not in this thread), maybe you missed those mails or that you like to read selectively. The basic idea is that STM contributed to many stuff, including comments as how things should be done. Maybe you are not aware how you work with a vendor for their devices and or when you have taken support from them, you need their final approval. Thus, before anything is done, i need to get a confirmation from STM as well. I have asked STM as well, please read the inlined mail. Original Message Subject: STB0899 driver and mixed results Date: Mon, 08 Oct 2007 16:35:11 +0400 From: Manu Abraham [EMAIL PROTECTED] To: XXX --- snip --- The STB0899 driver is finally getting to shape by now. Currently supported hardware is like this, by the driver here: http://jusst.de/hg/multiproto/ Some cleanups etc pending on it. The entire drivers can be downloaded from this URL: http://jusst.de/hg/multiproto/archive/tip.tar.gz * KNC1 DVB-S2 Plus * KNC1 DVB-S2 OEM (Also known as Satelco DVB-S2) * Technotrend TT S2 3200 * Technisat DVB-S2 Skystar HD The Technisat card, as it seems looks to be the same as that of the Technotrend TT S2 3200 card, except that it has a STB0899 with version C2L. Now i have a question (well, it's a problem that i am facing) It goes like this The KNC1 cards (both) and the Technotrend TT S2 3200 cards tune quite fine, and LOCK is almost immediate, less than half a second (impressive results) i did make a small change, from the case where it selects between MCPC/SCPC config where it uses 2 different clocks, for the MCPC case i changed it from 99 MHz to 90 MHz which makes the tuning quite fast and a bit more reliable (ie no more LOCK failures on the KNC1 and the TT S2 3200 cards) Now, on the Technisat Skystar HD card, there have been mixed results. One person got back stating that performance was real pathetic and LOCK 'ing time took minutes and or sometimes no LOCK's at all. Another person got back stating that he had 90% successful locks with DVB-S and 50% successful locks on DVB-S2 both cases with the Technisat card. --- snip --- Regards, Manu Anyway, I don't know what has been said on irc and I can't be bothered to read the irc
Re: [linux-dvb] UDP encapsulated MPEG{2,4} TS into dvbsnoop?
Il Friday 12 October 2007 10:43:01 Alexander E. Patrakov ha scritto: Sigmund Augdal wrote: payload type 96 and 97 is in the dynamic payload type range according to current rfcs. OK. The question is, still, how to play this. To play it you will need a SDP that describes what the ESes is. My guess is that is is in fact some kind of VOD service and not actually convensional TV. The names in the scan output do correspond to well-known TV stations. I have tried to extract the RTP payload from the dump using a simple C program. The result is that the payload of each packet starts with the same bytes (another header?). I tried to guess the length of this header and remove it (tried all even lengths between 0 and 20 bytes), and then decode the result as raw mp2, mp3, aac, mpeg4, h261, h264 and h264 data with ffmpeg. No luck yet, although the h261 codec announces the frame size (apparently for cellphones) and refuses to decode further. What to do next? if in the SDP of the broadcast transmission there's some kind of configuration (base64-encoded) string (generally known as extradata ) then you won't get ffmpeg (or any other decoder) decode the raw ESs without passing the extradata before feeding it the payloads. This is the common practice for that abomination that is RT[SC]P, which encourages this splitting between extradata and payloads even for formats that may have headers in-stream like H26x and Mpeg4. Your best best is to use ffmpeg or vlc directly on the udp:// or rtp:// transmissions you receive from the dvbnet interface ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Compro Videomate S350 card
Alexander E. Patrakov wrote: OM Ugarcina wrote: Linux video capture interface: v2.00 PCI: Enabling device :00:1f.3 (0001 - 0003) ACPI: PCI Interrupt :00:1f.3[C] - GSI 18 (level, low) - IRQ 20 saa7130/34: v4l2 driver version 0.2.14 loaded ACPI: PCI Interrupt :04:01.0[A] - GSI 22 (level, low) - IRQ 21 saa7130[0]: found at :04:01.0, rev: 1, irq: 21, latency: 64, mmio: 0xfeaffc00 saa7130[0]: subsystem: 185b:c900, board: Compro Videomate DVB-T300 [card=70,insmod option] saa7130[0]: board init: gpio is 843f00 input: saa7134 IR (Compro Videomate DV as /class/input/input4 saa7130[0]: i2c eeprom 00: 5b 18 00 c9 54 20 1c 00 43 43 a9 1c 55 d2 b2 92 saa7130[0]: i2c eeprom 10: 00 ff 86 0f ff 20 ff ff ff ff ff ff ff ff ff ff saa7130[0]: i2c eeprom 20: 01 40 01 02 02 01 03 01 08 ff 00 87 ff ff ff ff saa7130[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7130[0]: i2c eeprom 40: ff d6 00 c0 86 1c 02 01 02 ff ff ff ff ff ff ff saa7130[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff cb saa7130[0]: i2c eeprom 60: 30 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7130[0]: i2c eeprom 70: 00 00 00 10 03 9c ff ff ff ff ff ff ff ff ff ff tuner 1-0068: chip found @ 0xd0 (saa7130[0]) saa7130[0]: registered device video0 [v4l2] saa7130[0]: registered device vbi0 saa7130[0]/dvb: frontend initialization failed Then it is not an exact clone of Compro Videomate DVB-T300. You can try looking at the card, writing down the chip numbers, searching for ones that exist in http://www.linuxtv.org/hg/v4l-dvb/file/7dba1f554c4a/linux/Documentation/video4linux/CARDLIST.tuner, and adding the tuner=XX option to the saa7134 module. Not sure, however, if this makes sense at all for DVB-S cards. Hello Alexander, I have just tried running dmesg on my regular kernel which is a 2.6.22-9.61 fc6 and now I get much the same as above . So looks like support for T300 might be in there already . But that is neither here nor there . From what I can see the brake down of the S350 is : saa7130 , demodulator : zl10313 which has now been re-badged by Intel as CE6313 and tuner zl10039 which has also been re-badged by Intel as CE 5039 . Looking through the archives looks like there was some mention of zl10313 in December 2006 here : http://www.linuxtv.org/pipermail/linux-dvb/2006-December/015092.html and perhaps some work done on demodulator drivers here : http://www.mcmilk.de/projects/dvb-card/patches/ I guess what we might need is some driver development for the demodulator/tuner . I noticed there is a lot of interest for linux drivers out there for S350 . Looks like there is quite a large user base of this card including Broadband Internet via Satellite . Especially in forums such as this : http://forum.ixbt.com/topic.cgi?id=73:2477-18 To developers : If any printouts or info is needed please do not hesitate to ask . Best Regards Milorad ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Future of Multiproto
Hi, On Fri, Oct 12, 2007, Marcel Siegert wrote: can everybody _please_ stop this unnessessary discussion? When a developer deletes his mercurial repositories and announces he's going to rewrite the code to be independent of multiproto, then IMHO it is _necessary_ to find out why, and how to continue now. I have a vague idea about the state of multiproto now, but now I'm waiting for Steve to comment if he's happy if multiproto would be merged _now_, or if he wants to do something else, and explain what. Anyway, the decisions to make are not mine, I'm just trying to extract the information needed so all the cards are on the table for everyone to see easily. Johannes ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] UDP encapsulated MPEG{2,4} TS into dvbsnoop?
Il Friday 12 October 2007 13:57:26 Alexander E. Patrakov ha scritto: Nico Sabbi wrote: if in the SDP of the broadcast transmission there's some kind of configuration (base64-encoded) string (generally known as extradata ) then you won't get ffmpeg (or any other decoder) decode the raw ESs without passing the extradata before feeding it the payloads. This is the common practice for that abomination that is RT[SC]P, which encourages this splitting between extradata and payloads even for formats that may have headers in-stream like H26x and Mpeg4. I don't have any means to get the SDP except guessing. the sdp is surely in one of the multicast transmissions you have Does this mean that, if extradata are present in the required SDP, I have to give up, for technical reasons? yes And, just in case if extradata are in fact not needed, is my strip headers and feed to ffmpeg technique equivalent to trying with the correct SDP? yes, but remember that RTP defines a different payload format for each supported codec (nice, isn't it?) , so in each rtp packet you have to analyze the payload indicator (or however it's called) and demux the payload accordingly ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Strage SkyStar HD modprobe
Hi, Reinhard Nissl wrote: Hi, Manu Abraham wrote: this Logfile looks a bit strange, and I can't tune to DVB-S2 channels. DVB-S works fine. I really have the feeling that this card is demaged I experience a similar behaviour. There are days (like to today) when I have to completely power off my machine to get the card working. Sometimes tuning DVB-S channels works, but DVB-S2 doesn't work. After a power off, it most likely works. Today I had to power off the machine for more than one times. That's really strange. Can you please check whether pin 18 of the stb0899 on your card is at GND level ? You can check the continuity with a meter. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] UDP encapsulated MPEG{2,4} TS into dvbsnoop?
Nico Sabbi wrote: the sdp is surely in one of the multicast transmissions you have Do you mean that it should be hidden somewhere in my udp.dump file? But it contains only UDP packets sent to ports 2 and 20002, and all of them are valid RTP packets. How to search for it? Might it be broadcasted on a different PID? And, to make the task a bit simpler: could you please point me to a known good (i.e., decodable with VLC) RTP stream on the Internet, so that I can see what the real-world SDP looks like and how to demux the known good payload by hand? -- Alexander E. Patrakov ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Future of Multiproto
Marcel Siegert wrote: hi, can everybody _please_ stop this unnessessary discussion? manu, nobody is playing politics in the moment, not johannes, not steven, not anyone else. What was discussed yesterday was that, if you don't do what i write, i'll just take your code nevertheless as it is. maybe sometimes it is hard to understand what people want to say if you have all the bad past in mind. what was said in coherence to your multiproto api change is just as simple as follows: please state if you are ready to merge multiproto to the main repository, whatever way it will take into. steven has got a ready driver, that demonstrated your api is fine and works, you have got your stb0899 driver nearly done, and also beside some small problems due to the device, its also proven working. if there is something missing from dvb-s2 specs that is not needed to actually watch tv, dont take any care on that to prevent multiproto to be merged. we can get rid of _all_ the momentary stupid discussions if you are ready to merge it. I am ready, but waiting for a final acknowledgement, that's what it is. If someone would like to find offending changesets, that can be done in the meantime. If that's done, i will do the cleanups for the same, such that it can go in. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Future of Multiproto
hi, can everybody _please_ stop this unnessessary discussion? manu, nobody is playing politics in the moment, not johannes, not steven, not anyone else. maybe sometimes it is hard to understand what people want to say if you have all the bad past in mind. what was said in coherence to your multiproto api change is just as simple as follows: please state if you are ready to merge multiproto to the main repository, whatever way it will take into. steven has got a ready driver, that demonstrated your api is fine and works, you have got your stb0899 driver nearly done, and also beside some small problems due to the device, its also proven working. if there is something missing from dvb-s2 specs that is not needed to actually watch tv, dont take any care on that to prevent multiproto to be merged. we can get rid of _all_ the momentary stupid discussions if you are ready to merge it. thus we could go back concentrate developing stuff, merge it, satisfy endusers instead of having to spent all of our time to behave like linuxtv.childhood. HTH marcel ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Compro Videomate S350 card
OM Ugarcina wrote: Linux video capture interface: v2.00 PCI: Enabling device :00:1f.3 (0001 - 0003) ACPI: PCI Interrupt :00:1f.3[C] - GSI 18 (level, low) - IRQ 20 saa7130/34: v4l2 driver version 0.2.14 loaded ACPI: PCI Interrupt :04:01.0[A] - GSI 22 (level, low) - IRQ 21 saa7130[0]: found at :04:01.0, rev: 1, irq: 21, latency: 64, mmio: 0xfeaffc00 saa7130[0]: subsystem: 185b:c900, board: Compro Videomate DVB-T300 [card=70,insmod option] saa7130[0]: board init: gpio is 843f00 input: saa7134 IR (Compro Videomate DV as /class/input/input4 saa7130[0]: i2c eeprom 00: 5b 18 00 c9 54 20 1c 00 43 43 a9 1c 55 d2 b2 92 saa7130[0]: i2c eeprom 10: 00 ff 86 0f ff 20 ff ff ff ff ff ff ff ff ff ff saa7130[0]: i2c eeprom 20: 01 40 01 02 02 01 03 01 08 ff 00 87 ff ff ff ff saa7130[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7130[0]: i2c eeprom 40: ff d6 00 c0 86 1c 02 01 02 ff ff ff ff ff ff ff saa7130[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff cb saa7130[0]: i2c eeprom 60: 30 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7130[0]: i2c eeprom 70: 00 00 00 10 03 9c ff ff ff ff ff ff ff ff ff ff tuner 1-0068: chip found @ 0xd0 (saa7130[0]) saa7130[0]: registered device video0 [v4l2] saa7130[0]: registered device vbi0 saa7130[0]/dvb: frontend initialization failed Then it is not an exact clone of Compro Videomate DVB-T300. You can try looking at the card, writing down the chip numbers, searching for ones that exist in http://www.linuxtv.org/hg/v4l-dvb/file/7dba1f554c4a/linux/Documentation/video4linux/CARDLIST.tuner, and adding the tuner=XX option to the saa7134 module. Not sure, however, if this makes sense at all for DVB-S cards. -- Alexander E. Patrakov ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] UDP encapsulated MPEG{2,4} TS into dvbsnoop?
Il Friday 12 October 2007 14:55:17 Alexander E. Patrakov ha scritto: Nico Sabbi wrote: the sdp is surely in one of the multicast transmissions you have Do you mean that it should be hidden somewhere in my udp.dump file? But it contains only UDP packets sent to ports 2 and 20002, and all of them are valid RTP packets. How to search for it? Might it be broadcasted on a different PID? yes, of course. What you are trying to access looks very much dvbh to me, a real PITA that afaic is not worth the painfatigue And, to make the task a bit simpler: could you please point me to a known good (i.e., decodable with VLC) RTP stream on the Internet, so that I can see what the real-world SDP looks like and how to demux the known good payload by hand? dunno, better ask to [EMAIL PROTECTED] or [EMAIL PROTECTED] ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] About fixes into Mantis branch. Was: Asus Tiger can't find any channels
--- Manu Abraham [EMAIL PROTECTED] wrote: Manu Abraham wrote: Kristian Slavov wrote: Manu Abraham wrote: Marko Ristola wrote: If the current Mantis branch changes would be merged into v4l-dvb, you could concentrate more on other maybe more important projects. You would just sometimes pull v4l-dvb changes into your Mantis branch and if some bug is found in v4l-dvb, you could fix it first into Mantis branch, or then you could send a fix into v4l-dvb directly and pull the changes back. Eh ? You wanted to fix INVERSION for the CU1216. This file itself doesn't exist in linuxtv.org/hg/v4l-dvb I don't see your problem, though I'm not sure if this is related, but I have both mantis dvb-c pci card and em2880 based dvb-t usb stick. I would like to get them working at the same time. Since the mantis branch is probably quite outdated wrt. dvb core, and due to the recent disagreements between Marcus and some other developers, my problem might go unsolved for quite some time. However, if the mantis branch would be closer to the main dvb tree, I might have a chance to hack the drivers to coexist in my system. Give me a bit of time Updated tree: http://jusst.de/hg/mantis/ The major improvements are for the VP-1034 * Demodulator status check made reliable * Code simplification for Viterbi Sync check, makes acquisition more reliable * Implement a BER monitor measured for a base of 2 ^ 20 * Implement a Signal strength monitor provides a relative scale in terms of percentage (SNR is in dBmV) * Implement a simple UCB monitor, no real UCB monitor (just a kid's toy thing to watch like the other frontends) Also fixed a bug on BE machines, thanks to David Woodhouse Hi Manu, Is there any chance to include support for the VP DVS-S2 card some time in future? Thanks! Simeon Boardwalk for $500? In 2007? Ha! Play Monopoly Here and Now (it's updated for today's economy) at Yahoo! Games. http://get.games.yahoo.com/proddesc?gamekey=monopolyherenow ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] dvb-dibusb.c error linux 2.6.10
Hey, Sorry, not really my area of experience in regards to getting dvb on older kernels, but whoever manufactures the NAS must provide the appropriate patches for the kernel to get it to work on their hardware. They should provide the source on their website or something, you could track it down and apply the patches to the latest kernel. Hope this helps, Plantain On 10/12/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hello List, I'm trying to get dvb-t via usb to work with my NAS. Because the NAS got some hardware not supported by the mainline kernel I can not simply update the kernel. After some time I figured out how to load the firmware without udev/mdev. But still I get a a error message: ... drivers/media/dvb/dibusb/dvb-dibusb.c: bulk message failed: -110 (1/0) usb 1-1: events/0 timed out on ep1out drivers/media/dvb/dibusb/dvb-dibusb.c: bulk message failed: -110 (1/0) usb 1-1: events/0 timed out on ep1out drivers/media/dvb/dibusb/dvb-dibusb.c: bulk message failed: -110 (1/0) usb 1-1: events/0 timed out on ep1out drivers/media/dvb/dibusb/dvb-dibusb.c: bulk message failed: -110 (1/0) ... Im not really sure if its a usb or a dvb error. But all other usb devices are working so far ... The card is recognised as: Grandtec USB1.1 DVB-T/DiBcom USB1.1 DVB-T reference design (MOD3000) and the green light is burning after the firmware is loaded. I created the following devices: mkdir -p /dev/dvb/adapter0 mknod /dev/dvb/adapter0/frontend0 c 212 3 mknod /dev/dvb/adapter0/demux0 c 212 4 mknod /dev/dvb/adapter0/dvr0 c 212 5 mknod /dev/dvb/adapter0/net0 c 212 7 I have the following modules loaded: [EMAIL PROTECTED]:/system/some_Modules # cat /proc/modules dvb_dibusb 14628 0 - Live 0xbf09c000 net2280 18444 0 - Live 0xbf0aa000 dummy 2148 0 - Live 0xbf06 usbhid 30496 0 - Live 0xbf0a1000 dib3000mb 11680 1 dvb_dibusb, Live 0xbf098000 dib3000mc 13600 1 dvb_dibusb, Live 0xbf093000 dib3000_common 2656 2 dib3000mb,dib3000mc, Live 0xbf091000 dvb_core 74436 1 dvb_dibusb, Live 0xbf07d000 i2c_dev 7680 0 - Live 0xbf07a000 i2c_core 17936 3 dvb_dibusb,dib3000_common,i2c_dev, Live 0xbf074000 videodev 7520 0 - Live 0xbf071000 v4l2_common 4800 0 - Live 0xbf06e000 v4l1_compat 11652 0 - Live 0xbf06a000 firmware_class 7584 1 dvb_dibusb, Live 0xbf067000 yealink 10240 0 - Live 0xbf063000 snd_seq 48360 0 - Live 0xbf053000 snd_usb_audio 58176 0 - Live 0xbf043000 snd_pcm 79688 1 snd_usb_audio, Live 0xbf02e000 snd_usb_lib 10368 1 snd_usb_audio, Live 0xbf02a000 snd_rawmidi 2 1 snd_usb_lib, Live 0xbf024000 snd_timer 19396 2 snd_seq,snd_pcm, Live 0xbf01e000 snd_seq_device 6472 1 snd_rawmidi, Live 0xbf01b000 snd 40796 6 snd_seq,snd_usb_audio,snd_pcm,snd_rawmidi,snd_timer,snd_seq_device, Live 0xbf01 snd_page_alloc 6884 1 snd_pcm, Live 0xbf00d000 soundcore 7172 1 snd, Live 0xbf00a000 usblcd 4964 0 - Live 0xbf007000 loop 21040 0 - Live 0xbf00 [EMAIL PROTECTED]:/system/some_Modules # cat /proc/devices Character devices: 1 mem 2 pty 3 ttyp 4 /dev/vc/0 4 tty 5 /dev/tty 5 /dev/console 5 /dev/ptmx 7 vcs 10 misc 13 input 14 sound 36 netlink 81 video4linux 89 i2c 90 mtd 116 alsa 128 ptm 136 pts 180 usb 204 ttySL 212 DVB If anybody can give me a hint what I'm missing would be great. Thanks -- flip ___ 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
