Re: [linux-dvb] linux-dvb Digest, Vol 33, Issue 9
2. Re: DiB0700 firmware problems (Darren Salt) -- Missatge reenviat -- From: Darren Salt [EMAIL PROTECTED] To: linux-dvb@linuxtv.org Date: Wed, 03 Oct 2007 12:52:09 +0100 Subject: Re: [linux-dvb] DiB0700 firmware problems I demand that Eduard Huguet may or may not have written... [snip] Briefly: it works nearly perfect since lastest firmware release. I'm currently using the remote, which it was completely impossible before because the system hanged very often when I used the TV remote (and when I say hanged I mean hanged: That'd be remote control as executioner, then... ;-) (Hint: you mean hung.) [snip] -- | Darren Salt| linux or ds at | nr. Ashington, | Toon | RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army | + Burn less waste. Use less packaging. Waste less. USE FEWER RESOURCES. Don't vote - it only encourages them! LOL. It results obvious that English is not my mother language... ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] linux-dvb Digest, Vol 33, Issue 9
Eduard Huguet wrote: 2. Re: DiB0700 firmware problems (Darren Salt) ... because the system hanged very often when I used the TV remote (and when I say hanged I mean hanged: That'd be remote control as executioner, then... ;-) (Hint: you mean hung.) [snip] ... LOL. It results obvious that English is not my mother language... Don't be too upset - plenty of native English people get this one wrong too - especially since we abandoned that particular barbaric practice last century, this usage of the word is now becoming archaic. How other nationalities cope with the ridiculous irregularities of the English language always amazes me, but not as much as our laziness as a nation in not bothering even to try to learn other people's. I suspect that if North America hadn't generally adopted a fork of English the boot might be on the other foot by now. But their variant(s) contain plenty of their own traps for the unwary. Getting a bit OT here... -- Cheers Richard (MQ) ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] linux-dvb Digest, Vol 33, Issue 11
-- Missatge reenviat -- From: Richard (MQ) [EMAIL PROTECTED] To: linux-dvb@linuxtv.org Date: Thu, 04 Oct 2007 08:00:47 +0100 Subject: Re: [linux-dvb] linux-dvb Digest, Vol 33, Issue 9 Eduard Huguet wrote: 2. Re: DiB0700 firmware problems (Darren Salt) ... because the system hanged very often when I used the TV remote (and when I say hanged I mean hanged: That'd be remote control as executioner, then... ;-) (Hint: you mean hung.) [snip] ... LOL. It results obvious that English is not my mother language... Don't be too upset - plenty of native English people get this one wrong too - especially since we abandoned that particular barbaric practice last century, this usage of the word is now becoming archaic. How other nationalities cope with the ridiculous irregularities of the English language always amazes me, but not as much as our laziness as a nation in not bothering even to try to learn other people's. I suspect that if North America hadn't generally adopted a fork of English the boot might be on the other foot by now. But their variant(s) contain plenty of their own traps for the unwary. Getting a bit OT here... -- Cheers Richard (MQ) A fork of english... LOL: That's TOO geeky XD XD Cheers Eduard ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] RE : RE : linux-dvb and Dektec [was: DVB API update]
I think there is at least one usage case where one might want to have the DekTec card integrated into the linux-dvb driver framework, which already has been mentioned: us the existing linux-dvb applications with it! Especially dvbsnoop is a very helpful tool for some cases. I definitely want to start another war about which functionality should be in the kernel and which not, but IMHO the usage is not as separate as you claim. You mean don't want maybe ;-) To address both requirements: - Keep kernel code as small as possible - Use exotic devices through linux-dvb (not only Dektec, why not also VideoPropulsion or Optibase devices, and even recorded TS files on disk). you may need a generic dvb loopback driver as described in my previous post. In that case, the device-specific code is written in userland and feeds the loopback driver. Again, if linux-dvb had kept only device-specific features in kernel and moved generic code in a userland library, this library could offer hooks for user-specific TS input and, in the case of non-standard DVB input, everything specific whould remain in userland. But, as we say here, with a lot of IF you could put Paris in a bottle... -Thierry ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] RE : RE : linux-dvb and Dektec [was: DVB API update]
Thierry Lelegard wrote: you may need a generic dvb loopback driver as described in my previous post. In that case, the device-specific code is written in userland and feeds the loopback driver. In the ideal world, yes. Copying in and out of kernel is not fun and eats a lot of your CPU. Which is quite useless. Again, if linux-dvb had kept only device-specific features in kernel and moved generic code in a userland library, this library could offer hooks It is. What is that you see reflected in userspace as device specifics ? Of course you might want to use the memory frontend for that, but again not for any real sane use, but just for testing alone. You might like to read a bit about copying in and out of userspace http://en.wikipedia.org/?title=Ring_0 Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] RE : RE : linux-dvb and Dektec [was: DVB API update]
On Thu, Oct 04, 2007 at 10:30:50AM +0200, Thierry Lelegard wrote: I think there is at least one usage case where one might want to have the DekTec card integrated into the linux-dvb driver framework, which already has been mentioned: us the existing linux-dvb applications with it! Especially dvbsnoop is a very helpful tool for some cases. I definitely want to start another war about which functionality should be in the kernel and which not, but IMHO the usage is not as separate as you claim. You mean don't want maybe ;-) oops... of course! To address both requirements: - Keep kernel code as small as possible - Use exotic devices through linux-dvb (not only Dektec, why not also VideoPropulsion or Optibase devices, and even recorded TS files on disk). you may need a generic dvb loopback driver as described in my previous post. In that case, the device-specific code is written in userland and feeds the loopback driver. [...] Hmm... I am not sure if this is possible for all scenarios. For the budget cards with no TS manipulation I see no problem, but for other cards and functionalities, the user-space approach also has disadvantages. (E.g. in another project, we used a software PLL for synchronization of a decoder to an input TS - for such a thing to work, the TS handling has to be quite near to the hardware, and I doubt this would be possible in userland.) But again, this just as an example of the advantages the current drivers have, I think there is no need for such a change. (Unless someone wants to start a completely new and incompatible dvb framework, which I think would be the consequence.) Best regards, Wolfgang ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DiB0700 firmware problems
My findings... 1) system (uname -a) Linux vdr-tng 2.6.20-rc6 #1 PREEMPT Tue Jan 30 10:27:20 GMT 2007 i686 GNU/Linux (This is with DVB drivers checked out from mercurial repository on 28/09/07.) System is a Via Epia MII-12000 with a 1200 MHz Via Nehemiah processor. 2) lspci-output 00:00.0 Host bridge: VIA Technologies, Inc. VT8623 [Apollo CLE266] 00:01.0 PCI bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP] 00:0d.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80) 00:10.0 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 80) 00:10.1 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 80) 00:10.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 80) 00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) 00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge 00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) 00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50) 00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74) 00:14.0 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 61) 00:14.1 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 61) 00:14.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 63) 01:00.0 VGA compatible controller: VIA Technologies, Inc. VT8623 [Apollo CLE266] integrated CastleRock graphics (rev 03) Output of lsusb: Bus 003 Device 001: ID : Bus 007 Device 002: ID 2040:9950 Hauppauge Bus 007 Device 001: ID : Bus 006 Device 004: ID 2040:9301 Hauppauge Hauppauge WinTV NOVA-T USB2 (warm) Bus 006 Device 001: ID : Bus 005 Device 001: ID : Bus 004 Device 001: ID : Bus 001 Device 003: ID 0a81:0101 Chesen Electronics Corp. Keyboard Bus 001 Device 001: ID : Bus 002 Device 001: ID : 3) DiB0700 device name (USB Stick, Nova-T 500) Nova-T 500 in the only PCI slot and a Nova-T USB2 plugged into a USB port. I have no remote connected to the Nova-T 500 and I'm using options dvb-usb disable_rc_polling=1 with the dvb-usb module to disable them (I'm using a LIRC remote on a serial port.) I'm also using options dvb_usb_dib0700 force_lna_activation=1 to enable the amplifiers, although I've not really tested to see whether I need to or not. 4) Application using the device (MythTV, VDR etc) Vdr-1.5.9, using hardware MPEG-2 decoding with softdevice. The system runs 24 h a day because it doesn't always power itself off fully for some reason so I can't use nvram-wakeup. 5) Symptoms (unusable, disconnect after x days, no problem) When I was using the DVB drivers from this kernel (built back in January, I think) the system would work fine for a few days and then I would see a USB disconnect followed by lots of dib-usb (I think: they've now rotated out of my logs!) error messages because there was no data. These disconnects seemed to be mainly the Nova-T USB2, i.e. the external USB device, and would be accompanied by the LED going out. The only way to get it going again was to reboot: presumably it was in a warm state and there was no firmware upload (dvb-usb-nova-t-usb2-01.fw). These disconnects seemed to happen pretty randomly: sometimes it would work for a few hours, sometimes for a week or so. I have a cron job running which tests to see if it's disconnected and reboots it if so. (I have a second Nova-T USB2 but the disconnects seemed to occur much more frequently with two of them connected.) If anything, the disconnects tended to happen a few minutes after a timed recording had started, i.e. possibly after tuning to a different MUX but I can't be certain of this. I updated to the more recent drivers a few days back and I'm now using the dvb-usb-dib0700-1.10.fw firmware. Since updating, I haven't seen any of the USB disconnects but it has hung totally a few times. On a couple of occasions it ran perfectly for about a day or two and then hung; another time it only worked for about 30 minutes before it hung. Each time it has hung there has been nothing in any log files but the LED on the external USB device is still illuminated, unlike when it was disconnecting with the older drivers + firmware. I'll keep monitoring this...might try with two external USB devices too! Cheers, Laz ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] RE : RE : RE : linux-dvb and Dektec [was: DVB API update]
Copying in and out of kernel is not fun and eats a lot of your CPU. Which is quite useless. It is not a matter of performance, it is a matter of operating system security and stability. Access to a device is a matter of security, it needs access to internal kernel structure, it needs user access control. It must be in the kernel. Once you gain access to a DBV device, there is no security involved in demuxing the TS. There is no *need* to implement a software demux in the kernel. Concerning stability, the more code you put in the kernel, the more potential bugs you get. Bugs in the kernel means potential security breach, potential system hang or crash. So, when there is no good security reason to put something the kernel, you don't. This is what it done in microkernels such as Chorus, Mach or L4. I know, Linux is a monolithic kernel, not a microkernel. But monolithic does not mean bloated. See Solaris or OpenVMS, they are monolithic kernels, but they know when it is reasonable to put code in the kernel and when it is not. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] linux-dvb Digest, Vol 33, Issue 11
Eduard Huguet wrote: -- Missatge reenviat -- From: Richard (MQ) [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] To: linux-dvb@linuxtv.org mailto:linux-dvb@linuxtv.org Date: Thu, 04 Oct 2007 08:00:47 +0100 Subject: Re: [linux-dvb] linux-dvb Digest, Vol 33, Issue 9 Eduard Huguet wrote: 2. Re: DiB0700 firmware problems (Darren Salt) ... because the system hanged very often when I used the TV remote (and when I say hanged I mean hanged: That'd be remote control as executioner, then... ;-) (Hint: you mean hung.) [snip] ... LOL. It results obvious that English is not my mother language... Don't be too upset - plenty of native English people get this one wrong too - especially since we abandoned that particular barbaric practice last century, this usage of the word is now becoming archaic. How other nationalities cope with the ridiculous irregularities of the English language always amazes me, but not as much as our laziness as a nation in not bothering even to try to learn other people's. I suspect that if North America hadn't generally adopted a fork of English the boot might be on the other foot by now. But their variant(s) contain plenty of their own traps for the unwary. Getting a bit OT here... -- Cheers Richard (MQ) A fork of english... LOL: That's TOO geeky XD XD Cheers Eduard You've done well and to be congratulated. Some English speakers can't distinguish between two simple four letter words like than and then, probably Dyslexia sufferers whom I'd have to forgive, so we see such as more then and than you have to. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] RE : RE : RE : linux-dvb and Dektec [was: DVB API update]
Thierry Lelegard wrote: Copying in and out of kernel is not fun and eats a lot of your CPU. Which is quite useless. It is not a matter of performance, it is a matter of operating system security and stability. In the outlook that we can accept that fact that we can live with reduced performance. (Though i am not following your security viewpoint) Access to a device is a matter of security, it needs access to internal kernel structure, it needs user access control. It must be in the kernel. Once you gain access to a DBV device, there is no security involved in demuxing the TS. There is no *need* to implement a software demux in the kernel. Consider, this view as though everything else is fine: What do you do about devices having HW filters ? Then you will need to implement them in userland, in your view, which brings in inconsistent userspace interfaces. Concerning stability, the more code you put in the kernel, the more potential bugs you get. Bugs in the kernel means potential security breach, potential system hang or crash. So, when there is no good security reason to put something the kernel, you don't. This is what it done in microkernels such as Chorus, Mach or L4. You should look at Minix as well, but then the OS design is completely different. I know, Linux is a monolithic kernel, not a microkernel. But monolithic does not mean bloated. See Solaris or OpenVMS, they are monolithic kernels, but they know when it is reasonable to put code in the kernel and when it is not. Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] RE : RE : RE : RE : linux-dvb and Dektec [was: DVB API update]
What do you do about devices having HW filters ? Then you will need to implement them in userland, in your view, which brings in inconsistent userspace interfaces. I addressed this in a previous mail of this thread. The device driver should report capabilities in a standard way: able to demux PIDs, able to demux PES packets, etc. The public API of the userland library offers a standard demux API to the application. Internally, the library checks if the frontend device can do hardware demux. It it can, the library invokes it. If it can't, the library reads the TS and does software demux. This is more or less what is done now, except that everything is in the kernel. But I agree that this is a theoretical discussion. The reality is different. Linux-dvb is entirely in the kernel and we have to live with that. Starting a new incompatible dvb framework would we create more trouble than solving problems. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] RE : RE : RE : RE : linux-dvb and Dektec [was: DVB API update]
Thierry Lelegard wrote: What do you do about devices having HW filters ? Then you will need to implement them in userland, in your view, which brings in inconsistent userspace interfaces. I addressed this in a previous mail of this thread. The device driver should report capabilities in a standard way: able to demux PIDs, able to demux PES packets, etc. The public API of the userland library offers a standard demux API to the application. Internally, the library checks if the frontend device can do hardware demux. It it can, the library invokes it. If it can't, the library reads the TS and does software demux. Agreed, although this moves part of the hardware specific information such as how many filters a device can provide etc etc to the userspace. It will look a bit more cleaner (in kernel) if done that way. Also for newer devices there would be routable filters for some specifc things and so on. Now (suppose that we have moved out to userspace) that we have filtering in userland, now all the hardware specific ugliness comes to userspace. This is more or less what is done now, except that everything is in the kernel. ACK. But I agree that this is a theoretical discussion. The reality is different. Linux-dvb is entirely in the kernel and we have to live with that. Starting a new incompatible dvb framework would we create more trouble than solving problems. :) Although that said, for some delivery systems, we will need the vanilla TS out. ie there is no straight away demux (practically possible) in kernel So it might not be completely theoretical, some amounts we can apply it. ie the only concept is we shouldn't break the existing behaviour of the old devices. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] a question
Erez D wrote: On 10/3/07, Manu Abraham [EMAIL PROTECTED] wrote: Hi, Erez D wrote: manu, i see you are the expert regarding linux dvb-s2. i would like to help make the TT 3600 work under linux. knowing it's status will help me know what part of the linux drivers i need to master. First of all, i don't know what hardware is in it. You have any information on it ? other then reading on this list your talk with STM saying it is STB0899 based, no. Even STM doesn't know what USB interface it has. (I had asked STM) Only Technotrend knows, maybe someone from TT can fill in some details in here ? If someone can find out, the details of it, then easier. what should i do to get it ? do i need to open-it, or will lspci/lsusb suffice ? Just open it and see. Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] RE : linux-dvb and Dektec [was: DVB API update]
hi, ehi, what a thorough explanation.. maybe things are not all this black and white.. i wrote my first answer a bit quickly but now i'd like to give two more bits for added value! Thierry Lelegard wrote: Also, as you pointed out, Dektec products can be either input, output or both. Their output products also include very nice modulators on PCI boards. I presently use a DTA-110T, a DVB-T modulator. Since linux-dvb is an input-only framework, it would address only part of Dektec products (and even part of a device in the case of a DTA-140). indeed, the fact of the linux-dvb driver to be actually an input only framework for MPEG (TS/PS) stream it's beginning to fall a little short. IMHO there are already a number of stuff and environment, old and newer, that need to be addressed, on linux, with an outgoing path for native MPEG streams. historically there were two devices with such a capability: - the Fully Fledged (nexus) cards with their MPEG2 decoder on board - the ancient REALmagic Hollywood Plus - actually there is also the MPEG2 decoder inside the iTVC15 / CX23415 chip in the PVR350 card.. (ivtv driver not coping with it, i think..) then, there's the big mess of video decoding of MPEG2 PES stream (SD/HD) and some acceleration for H264 stream inside the core of the recent GPUs (avivo and purehd marketing vaporware.. something from via and intel too..) are we going to leave this feature available as a sub-set of the X driver or there's a place for a MPEG driver without the X? i think for example to use-cases like the media center like myth-tv running with DirecFB.. in a bit different scenario, the embedded one, there are also devices natively decoding MPEG2 TS streams like: - the PowerPc SoC inside some DVB SET TOP BOX as Dreambox and the DGStation CubeCafe (Vulcan and Pallas) they do have actually a linux kernel running on the powerpc core but the decoding API are a bit home made and binary too (maybe thing are changing..) BTW we are a bit involved in a design of an open source java based middleware running on such HW so we are really using it and would prefer linux-dvb drivers for MPEG decoding.. - i really don't know how are coping with DVB decoding inside the other big player of the linux-based STB market, the Sigma Designs EM863x. - and then there is the third player, STM ST710x who's running linux too with some DVB hack for decoding purposes.. IMHO plenty of situations where a linux dvb API for decoding stuff should/could be useful for the masses, because this generation of STBs are flooding our houses today or tomorrow, so we need and should have a way to hack them.. [..skipping lot of things about userland against kernel stuff..] Anyway, coming back to linux-dvb and Dektec, kernel drivers exist for both, just write userland code to access the one you want. then i'd like to add some bits about the professional market using DVB ASI interfaces. as someone already have told, there are plenty of DVB card producers; i can say out of my mind these: dektec, videopropulsion, optibase, dveo/computermodules, alitronika, bluetop (and other too..) all these cards are of course running on linux today, but each with is own driver API.. i think only dektec is the one with open source driver openly available on the site and i know that some chinese are providing drivers with wrapper to mimic the dektec API. that's how i see this market. I don't know IF there's interest for the linux community at large to promote a unified driver for this technology.. in theory, the professional customers of such cards should be interested to get a single unified compatibility layer to escape the vendor lock in, BUT, if they are fine as they stay today, why the linux community should give them an hand? i don't think we would get back something useful in the short term, but i'm open to hear other opinions too.. bye andrea venturi -Thierry -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Andrea Venturi Envoyé : mercredi 3 octobre 2007 15:10 À : linux-dvb Objet : Re: [linux-dvb] DVB API update Manu Abraham wrote: Hi, Simon Hailstone wrote: Hi All, If it sheds any light on the nature of DVB-ASI, there are Linux drivers available ( with source ) for the DekTec ASI adapters here : http://www.dektec.com/Products/LinuxSDK/Downloads/LinuxSDK.zip If someone has the hardware, we can take a go at it. hi, here in Cineca, we are running an open source project called JustDvb-It, it's a DVB DSMCC carousel server for interactive television, you could grab it here: http://www.cineca.tv/labs/mhplab/JustDVb-It%202.0.html as we need to interface broadcaster stuff like multiplexer (with DVB ASI interfaces), we use plenty of these Dektec card like DTA140 and so on.. but for that purpose we found sufficient the driver provided by Dektec. it's a simple character device with some
[linux-dvb] I-Frame Detection
Hi there, this is a bit off-topic since it is not a really linux-specific question, but maybe someone does know this right away. I'm lookig for a way to recognize the type of a video-frame in MPEG-2 (I.P or B) to create smooth transitions between video files, without having to decode the whole frame. I looked through the MPEG-2 TS and PES definitions, but all i found was a splicing_point_falg in the TS Adaptation Field. Unfortunately the hardware-encoder i'm working with doesn't seem to set these flags. Does anybody know another way how to determin the frame type? Regards, Thomas ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] a question
On 10/3/07, Manu Abraham [EMAIL PROTECTED] wrote: Hi, Erez D wrote: manu, i see you are the expert regarding linux dvb-s2. i would like to help make the TT 3600 work under linux. knowing it's status will help me know what part of the linux drivers i need to master. First of all, i don't know what hardware is in it. You have any information on it ? other then reading on this list your talk with STM saying it is STB0899 based, no. what should i do to get it ? do i need to open-it, or will lspci/lsusb suffice ? thanks, erez. Regards, Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Hauppauge HVR-4000
Hi All, I've been searching list archives for a while and can't find an absolute answer to this, but can someone please let me know the status of the HVR-4000 at the moment please? I'm using Steve's driver (thanks for the work on this Steve) and can get DVB-S/2 perfectly, including BBC-HD. I'm now trying to tune to local DVB-T channels, but can't really find any recent info on the status of this card. Kaffeine only sees the DVB-S section of the card, and finds channels on Astra 28.2e no probs, but there is no entry for DVB-T. I do have entries in dev for video, radio and vbi, but nothing seems to use them properly. MythTV sees the /dev/video0 but cannot find any channels either as analogue or DVB. The DVB-T signal is strong down here, as I have had success getting a Hauppauge Nova-T USB stick tuned in. I've read fragmented info on lists about using ivtv with the T portion of the card and lots of other bits and pieces on maybe getting it working. However nothing seems concrete about it. If someone could please take a sec to let me know the status, and if the DVB-T should be working if you can set me on the right track I'll work it out from there! I'm trying to tune to Spanish/European DVB-T (if that makes any difference? I'm not sure if there is a different rev. of the card between EU/USA) Many thanks for taking the time to read/reply, Bon P.S - For info, I'm located in Gibraltar (Very Southern Spain) and using a 1.5m dish can get a good signal on Astra 28.2e (Sky). Anyone looking to receive BBC/ITV FTA (Freeview) channels in Southern Spain could do worse than look at this card. Considering the Astra footprint is borderline down here and even some Sky boxes struggle, this card is very good at getting all FTA channels here, and with the addition of BBC-HD coming in well, I'm very pleased/surprised with the results. Thanks go again to Steve for working on the driver. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] RE : linux-dvb and Dektec [was: DVB API update]
Andrea Venturi wrote:
- the PowerPc SoC inside some DVB SET TOP BOX as Dreambox and the
DGStation CubeCafe (Vulcan and Pallas)
they do have actually a linux kernel running on the powerpc core but the
decoding API are a bit home made and binary too (maybe thing are
changing..)
The PowerPC-based Dreamboxes still use the old DVB-API (its initial
drivers predate the change to the new API, and never followed it),
whereas the newer Dreamboxes (DM7025 and the hopefully upcoming DM8000)
are using the current API. (There was also an effort to build new
Pallas/Vulcan APIv3 drivers as GPL, but this had to be pulled for legal
reasons. Those drivers were never complete, though.)
All are using binary-only driver modules for different reasons, but all
conform to the available userspace API as much as possible. Sometimes a
few additions were required (see also my discussion about
VIDEO_GET_{PTS,STC} etc.), but they use (for example) the
/dev/dvb/adapter0/video0-API.
Another implementation is the dbox2, which uses open-source drivers. And
don't forget the old full-featured cards.
However sometimes the API is not completely clear (like the order: Do
you first have to do a VIDEO_PLAY, then start the demux? Things like
that are sometimes even hardware-dependent and are likely to differ from
implementation to implementation. Sometimes you need to be tricky for
proper syncing, and trickmodes are a completely gray area...) But for
just playing video, the API should be ok. Don't forget that all hardware
MPEG decoders are beasts, and likely to be tricky in operation. The API
should hide the ugly details, but that's not always possible.
Felix
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] RE : linux-dvb and Dektec [was: DVB API update]
Felix Domke wrote: Andrea Venturi wrote: - the PowerPc SoC inside some DVB SET TOP BOX as Dreambox and the DGStation CubeCafe (Vulcan and Pallas) they do have actually a linux kernel running on the powerpc core but the decoding API are a bit home made and binary too (maybe thing are changing..) The PowerPC-based Dreamboxes still use the old DVB-API (its initial drivers predate the change to the new API, and never followed it), whereas the newer Dreamboxes (DM7025 and the hopefully upcoming DM8000) are using the current API. (There was also an effort to build new Pallas/Vulcan APIv3 drivers as GPL, but this had to be pulled for legal reasons. Those drivers were never complete, though.) A while back i had asked Amino communications for the driver/kernel sources, when their STB wasn't able to do MPTS properly. The reply i got was pay up $50,000 and you get the sources. Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] SkyStar2 Flexcop IIB 2.6D
Hi, I have tried to setup my debian etch with a skystar2 dvb-s card. Using dvbscan to create the channels.conf file and dvbtune to tune to one of the channels. mplayer /dev/dvb/adapter0/dvr0 Mplayer reports No Video PID but has Audio which works and I can listen to it. The dvbtune shows the pid for video and audio and has the Lock. Do I need a definition file for the card. Only markings on the card are. metal box - Technisat DAS Original SkyStar2PN 92105-20003d Rev 2.6D Im not sure if this is the problem but under /dev/dvb/adapter0/dvr0 I have audio0 but no video0. ? Any Ideas on what to try ? Thanks Nick -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] I-Frame Detection
Thomas Lagemann wrote: Hi there, this is a bit off-topic since it is not a really linux-specific question, but maybe someone does know this right away. I'm lookig for a way to recognize the type of a video-frame in MPEG-2 (I.P or B) to create smooth transitions between video files, without having to decode the whole frame. I looked through the MPEG-2 TS and PES definitions, but all i found was a splicing_point_falg in the TS Adaptation Field. Unfortunately the hardware-encoder i'm working with doesn't seem to set these flags. Does anybody know another way how to determin the frame type? Not that i can help you much, but what you are looking at is available in 13818-2 AFAICT. Regards, Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] I-Frame Detection
Il Thursday 04 October 2007 15:34:11 Thomas Lagemann ha scritto: Hi there, this is a bit off-topic since it is not a really linux-specific question, but maybe someone does know this right away. I'm lookig for a way to recognize the type of a video-frame in MPEG-2 (I.P or B) to create smooth transitions between video files, without having to decode the whole frame. I looked through the MPEG-2 TS and PES definitions, but all i found was a splicing_point_falg in the TS Adaptation Field. Unfortunately the hardware-encoder i'm working with doesn't seem to set these flags. Does anybody know another way how to determin the frame type? you need to demux the video stream and analyze the picture_coding type in the picture_header. Search for some draft of ISO 13818-2 in google ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Warning, there seems to be a new Nova TD stick out!!
Hi, I´ve posted some yesterday and I´ve done some more poking around and it just doesn´t find any signal in linux I´ve tried with two different antenna feeds who both works with windows, if I spilt my primary feed I can still run the t-500 PCI card but no matter what the TD stick never finds anything. Found DVB-T frontend. Using adapter /dev/dvb/adapter2/frontend0 -_-_-_-_ Getting frontend capabilities-_-_-_-_ frontend DiBcom 7000PC supports INVERSION_AUTO QAM_AUTO TRANSMISSION_MODE_AUTO GUARD_INTERVAL_AUTO HIERARCHY_AUTO FEC_AUTO -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_ initial_tune:1379: Setting frontend parameters failed f17750 bw7initial_tune:1379: Setting frontend parameters failed f18450 bw7initial_tune:1379: Setting frontend parameters failed f19150 bw7initial_tune:1379: Setting frontend parameters failed f19850 bw7initial_tune:1379: Setting frontend parameters failed f20550 bw7initial_tune:1379: Setting frontend parameters failed f21250 bw7initial_tune:1379: Setting frontend parameters failed f21950 bw7initial_tune:1379: Setting frontend parameters failed f22650 bw7474000: 482000: ^C /Henrik ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] KNC1 DVB-S2 Plus, Satelco DVB-S2, TT S2 3200, Technisat DVB-S2
hy, is there a updated mantis snapshot available that is compatible with the multiproto hg tree? i'd like to see my VP-1041 tunning faster (not 35 seconds)... thx, notz On Saturday 29 September 2007 02:29:16 Manu Abraham wrote: Hi folks, I have pushed out a tree containing support for the mentioned hardware. Please note, support is still incomplete. Still much more to happen. NOTE: Still in BETA stage. Please collect all your issues, will go through one by one. I can go through the issues one by one only, so please bear with me. The hacked szap is here http://abraham.manu.googlepages.com/szap.c I would like to know the issues you face. Some people have said that the STB0899 tunes and LOCK's incredibly faster than any of the demodulator drivers we have. Would like to verify this as well. I am wondering whether this is too good to believe. Please give it a go. Testers, please give results with the stb0899 module with verbose=5 module parameter by the way i forgot to mention the tree. http://jusst.de/hg/multiproto Please change the subject to reflect the hardware you have, for getting back results. Will get some sleep now. Regards, Manu ___ 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] KNC1 DVB-S2 Plus, Satelco DVB-S2, TT S2 3200, Technisat DVB-S2
Gernot Pansy wrote: hy, is there a updated mantis snapshot available that is compatible with the multiproto hg tree? Not right now. But, soon. After this initial session. i'd like to see my VP-1041 tunning faster (not 35 seconds)... :) Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DiB0700 firmware problems
On Thursday 04 October 2007 10:09, Laz wrote: My findings... When I was using the DVB drivers from this kernel (built back in January, I think) the system would work fine for a few days and then I would see a USB disconnect followed by lots of dib-usb (I think: they've now rotated out of my logs!) error messages because there was no data. These disconnects seemed to be mainly the Nova-T USB2, i.e. the external USB device, and would be accompanied by the LED going out. The only way to get it going again was to reboot: presumably it was in a warm state and there was no firmware upload (dvb-usb-nova-t-usb2-01.fw). I've just experienced a USB disconnect from the external Nova-T USB2 with the new firmware: the LED went out but the system didn't hang. syslog contained: Oct 4 20:28:59 vdr-tng kernel: hub 6-0:1.0: state 7 ports 6 chg evt 0002 Oct 4 20:28:59 vdr-tng kernel: ehci_hcd :00:10.3: GetStatus port 1 status 00100a POWER sig=se0 PEC CSC Oct 4 20:28:59 vdr-tng kernel: hub 6-0:1.0: port 1, status 0100, change 0003, 12 Mb/s Oct 4 20:28:59 vdr-tng kernel: usb 6-1: USB disconnect, address 4 Oct 4 20:28:59 vdr-tng kernel: usb 6-1: unregistering device Oct 4 20:28:59 vdr-tng kernel: usb 6-1: usb_disable_device nuking all URBs Oct 4 20:28:59 vdr-tng kernel: ehci_hcd :00:10.3: shutdown urb cb202180 pipe c0030480 ep6in-bulk Oct 4 20:28:59 vdr-tng kernel: ehci_hcd :00:10.3: shutdown urb cb202420 pipe c0030480 ep6in-bulk Oct 4 20:28:59 vdr-tng kernel: ehci_hcd :00:10.3: shutdown urb cb202480 pipe c0030480 ep6in-bulk Oct 4 20:28:59 vdr-tng kernel: ehci_hcd :00:10.3: shutdown urb cb202300 pipe c0030480 ep6in-bulk Oct 4 20:28:59 vdr-tng kernel: ehci_hcd :00:10.3: shutdown urb cb2022a0 pipe c0030480 ep6in-bulk Oct 4 20:28:59 vdr-tng kernel: ehci_hcd :00:10.3: shutdown urb cb202240 pipe c0030480 ep6in-bulk Oct 4 20:28:59 vdr-tng kernel: ehci_hcd :00:10.3: shutdown urb cb2021e0 pipe c0030480 ep6in-bulk Oct 4 20:28:59 vdr-tng kernel: dvb-usb: bulk message failed: -22 (6/2) ^- lots of this last one interspersed with blocks of similar messages with the final number replaced by -1072586294, -996626800, -863886798, -862828572, 402659331, 0, -22, 52, etc. in a variety of orders until I rebooted. (This is pretty much what I was seeing with the old driver + firmware but more often.) Cheers, Laz ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] RE : RE : RE : RE : linux-dvb and Dektec [was: DVB API update]
On Thu, 4 Oct 2007, Thierry Lelegard wrote: What do you do about devices having HW filters ? Then you will need to implement them in userland, in your view, which brings in inconsistent userspace interfaces. I addressed this in a previous mail of this thread. The device driver should report capabilities in a standard way: able to demux PIDs, able to demux PES packets, etc. The public API of the userland library offers a standard demux API to the application. Internally, the library checks if the frontend device can do hardware demux. It it can, the library invokes it. If it can't, the library reads the TS and does software demux. This is more or less what is done now, except that everything is in the kernel. There is an advantage to doing software filtering in the kernel. Often a TS has many more programs that one is interested in, and so many frames will be filter out by the demuxer. By doing demuxing in the kernel, one can filter out the uninteresting packets as soon as possible. Now, filtered packets never make it out of the device DMA buffer into the dvr buffer and are never copied out of the dvr buffer into userspace. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Technisat DVB-S2 Skystar HD
Manu Abraham wrote: Artem Makhutov wrote: Hi, On Tue, Oct 02, 2007 at 05:09:59PM +0400, Manu Abraham wrote: Artem Makhutov wrote: It is possible to tune to DVB-S and DVB-S2 channels. The driver has the same issues like the old driver on getting a LOCK on both DVB-S and DVB-S2 channels. In stb0899_drv.c. where you see SearchRange=3MHz, try increasing it to 10MHz and see whether it makes any difference ? I have the feeling that it has improved the situation, but the problem is still not solved. Can you please get the log for (with STB0899 and STB6100 with verbose=5) a) 3 Mhz 1) a complete cycle with a LOCK, including where it calls track. 2) 3 complete cycles where it fails to LOCK, including where it calls track. b) 10 Mhz 1) a complete cycle with a LOCK, including where it calls track. 2) 3 complete cycles where it fails to LOCK, including where it calls track. with both DVB-S and DVB-S2 modes, for the same frequency for each. Please be careful as not to mix up the logs. What's up ? Haven't heard after this. Btw, can you do a fresh clone and try again ? Have applied the fixes to the tree, just leave the 3 MHz to 10 MHz Search range change. I have added in a fix, which affects the Timing Recovery Loop, which was wrongly calculated, ie for a different master Clock. Can you please check whether you see any specific change for you in there ? Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Technisat DVB-S2 Skystar HD
Hi, On Fri, Oct 05, 2007 at 01:30:53AM +0400, Manu Abraham wrote: Manu Abraham wrote: On Tue, Oct 02, 2007 at 05:09:59PM +0400, Manu Abraham wrote: Can you please get the log for (with STB0899 and STB6100 with verbose=5) [...] What's up ? Haven't heard after this. Just been quite busy the last days. Tomorrow I should have some free time again. Btw, can you do a fresh clone and try again ? Have applied the fixes to the tree, just leave the 3 MHz to 10 MHz Search range change. I have added in a fix, which affects the Timing Recovery Loop, which was wrongly calculated, ie for a different master Clock. Can you please check whether you see any specific change for you in there ? Ok, thanks for the changes. I will run the tests tomorrow. Regards, Artem -- Artem Makhutov Unterort Str. 36 D-65760 Eschborn ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] UltaView DBV-T Plus
Hi, I have a UltaView DBV-T Plus TV card and am unable to get it working. This card is found in the gallery however there is no info on what parameters to pass to kernel. Presently I am using card=42 tuner=54 which is probably totally wrong. Can anyone help with the correct parameters? I am using Kubuntu 7.04 I have installed kernel 2.6.22.1 /etc/modprobe.conf alias char-major-81 videodev alias char-major-81-0 cx8800 alias /dev/radio0 cx8800 alias /dev/video0 cx8800 options cx88xx card=42 tuner=54 lspci 01:08.0 Multimedia video controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder (rev 05) Subsystem: DViCO Corporation FusionHDTV DVB-T Plus Flags: medium devsel, IRQ 21 Memory at f300 (32-bit, non-prefetchable) [size=16M] Capabilities: [44] Vital Product Data Capabilities: [4c] Power Management version 2 01:08.2 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder [MPEG Port] (rev 05) Subsystem: DViCO Corporation Unknown device db11 Flags: medium devsel, IRQ 21 Memory at f400 (32-bit, non-prefetchable) [size=16M] Capabilities: [4c] Power Management version 2 lspci -n 01:08.0 0400: 14f1:8800 (rev 05) 01:08.2 0480: 14f1:8802 (rev 05) Many thanks Grahame Jordan ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Medion Quad(ro) - first tries on DVB-S
Folks,
since yesterday I got my dirty ;) fingers on a used double saa7131e
Medion Quadro and got it up for the first PCI bridge in an MSI orange
PCI slot on some nforce3 AMD stuff.
Analog TV, noticeable worse than on my prior Asus P7131e Dual, works.
DVB-T too, also with significant loss compared to the Asus.
One can enable _some sort_ of radio, but obviously the 5.5MHz filter is
missing to get it through sound IF processing on the saa7131e.
All three known LNA configs don't improve any reception.
Now, the hybrid analog/DVB-T tda8275a tuner at 0x60 is behind the bridge
of the tda8290 analog IF demodulator, which is at 0x96 within the
saa7131e on that device(s).
I'm currently using the attached patch, since tests revealed, that the
DVB-S driver can't find anything, except on 0x60 too, for the tda826x
behind the i2c bridge of the tda10086.
I don't have _any_ DVB-S equipment, nada, also far away from caring
about any diseqc stuff right now.
The card should be able to support analog TV and DVB-S at once.
Of course DVB-T and DVB-S can only be used at once on either of the two
PCI bridges, have only one visible ...
The following happens.
DVB-S seems to be fine.
If I start an analog TV app like xawtv-3.95, I can switch analog
channels during szap is running. With szap I also seem to be able to
change DVB-S to anything at the same time.
If I quit xawtv analog during szap is running and restart it then, the
tda8290 and tda8275a get doomed/lost and only a cold reboot brings them
back.
On tvtime, even only analog channel changes have the same result within
short time, also the picture is affected on every refresh of szap.
Without any sat equipment, what is going on and why no errors
previously ...
Cheers,
Hermann
xawtv analog restart during szap running and tvtime switching channels
then also attached.
diff -r b0a3a9b43d60 linux/drivers/media/video/saa7134/saa7134-dvb.c
--- a/linux/drivers/media/video/saa7134/saa7134-dvb.c Wed Oct 03 11:23:01 2007 -0300
+++ b/linux/drivers/media/video/saa7134/saa7134-dvb.c Wed Oct 03 19:32:06 2007 +0200
@@ -973,7 +973,21 @@ static int dvb_init(struct saa7134_dev *
configure_tda827x_fe(dev, tevion_dvbt220rf_config);
break;
case SAA7134_BOARD_MEDION_MD8800_QUADRO:
- configure_tda827x_fe(dev, md8800_dvbt_config);
+ if(! use_frontend) { //terrestrial
+ configure_tda827x_fe(dev, md8800_dvbt_config);
+ } else { //satellite
+ dev-dvb.frontend = dvb_attach(tda10086_attach, flydvbs, dev-i2c_adap);
+ if (dev-dvb.frontend) {
+if (dvb_attach(tda826x_attach, dev-dvb.frontend, 0x60,
+ dev-i2c_adap, 0) == NULL) {
+ wprintk(%s: Medion Quadro, No tda826x found!\n, __FUNCTION__);
+}
+if (dvb_attach(isl6421_attach, dev-dvb.frontend, dev-i2c_adap,
+ 0x08, 0, 0) == NULL) {
+ wprintk(%s: Medion Quadro, No ISL6421 found!\n, __FUNCTION__);
+}
+ }
+ }
break;
case SAA7134_BOARD_AVERMEDIA_AVERTVHD_A180:
dev-dvb.frontend = dvb_attach(nxt200x_attach, avertvhda180,
binclHp5EqZgF.bin
Description: application/compressed-tar
binbdeNDGebuJ.bin
Description: application/compressed-tar
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Yuan Stratford PG300 DVB-T Remote
I got the card working with: options cx88xx card=43 and now I get the following in dmesg: [17179585.336000] cx2388x v4l2 driver version 0.0.5 loaded [17179585.336000] ACPI: PCI Interrupt :00:0b.0[A] - GSI 19 (level, low) - IRQ 193 [17179585.336000] CORE cx88[0]: subsystem: 12ab:2300, board: KWorld/VStream XPert DVB-T with cx22702 [card=43,insmod option] [17179585.336000] TV tuner 4 at 0x1fe, Radio tuner -1 at 0x1fe [17179585.38] cx2388x dvb driver version 0.0.5 loaded [17179585.388000] r8169: eth0: link up [17179585.552000] input: cx88 IR (KWorld/VStream XPert D as /class/input/input2 [17179585.552000] cx88[0]/0: found at :00:0b.0, rev: 5, irq: 193, latency: 32, mmio: 0xbd00 [17179585.552000] cx88[0]/0: registered device video0 [v4l2] [17179585.552000] cx88[0]/0: registered device vbi0 [17179585.552000] ACPI: PCI Interrupt :00:0b.2[A] - GSI 19 (level, low) - IRQ 193 [17179585.552000] cx88[0]/2: found at :00:0b.2, rev: 5, irq: 193, latency: 32, mmio: 0xbc00 [17179585.552000] cx88[0]/2: cx2388x based dvb card [17179585.552000] DVB: registering new adapter (cx88[0]). [17179585.552000] DVB: registering frontend 0 (Conexant CX22702 DVB-T)... However the remote doesnt even pretend to work. I have no idea on how to write a driver for it or to even see the raw input. Has anyone gotten it to work... or could you point me in the direction on how to start writing a driver for it? _ Win tix to see Crowded House live at the Greek Theatre, LA! http://ninemsn.com.au/share/redir/adTrack.asp?mode=clickclientID=800referral=windowslivehotmailtaglineURL=http://music.ninemsn.com.au/crowdedhouse ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
