Re: [linux-dvb] Video and audio pid problems with dvb-t channels in Norway
On Sun, 2007-09-30 at 22:59 +0200, Nico Sabbi wrote: If you compile dvbstream from cvs (dvbtools.sf.net) and run ./dvbstream -f FREQUENCY -bw 8 -c 0 -n 10 -prog -o:/dev/null 1 wil give you a list of the available programs, then run Yes, this works after I modified a header file to include settings for Norway. BTW: what does 1 at the end mean? ./dvbstream -f FREQUENCY -bw 8 -n 30 -c 0 -prog -o:dump.ts 'PROGRAM NAME' wil dump 30 seconds of program to dump.ts, that players such as mplayer, vlc, xine and kaffeine could be able to play. I got a large dump.ts file but none of the suggested programs could play it back. I tried f.ex. mplayer without any special options. Do you want me to upload the dump.ts to ftp://upload.mplayerhq.hu/incoming ? Thanks -- Per Thomas ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [UK Specific] Ditch Sky!
Hi, Unfortunately we are unable to receive freeview in Northampton due to a very poor signal, hence having too go the satellite route :( Will do some research as to what other satellite providers offer from other countries. Thanks all for your help :) Regards, --[ UxBoD ]-- // PGP Key: curl -s https://www.splatnix.net/uxbod.asc | gpg --import // Fingerprint: C759 8F52 1D17 B3C5 5854 36BD 1FB1 B02F 5DB5 687B // Keyserver: www.keyserver.net Key-ID: 0x5DB5687B // Phone: +44 845 869 2749 SIP Phone: [EMAIL PROTECTED] -- 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] Video and audio pid problems with dvb- t channels in Norway
Il Wednesday 03 October 2007 09:14:37 Per Thomas Jahr ha scritto: On Sun, 2007-09-30 at 22:59 +0200, Nico Sabbi wrote: If you compile dvbstream from cvs (dvbtools.sf.net) and run ./dvbstream -f FREQUENCY -bw 8 -c 0 -n 10 -prog -o:/dev/null 1 wil give you a list of the available programs, then run Yes, this works after I modified a header file to include settings for Norway. BTW: what does 1 at the end mean? just a random number to give dvbstream a program to save (even fake is enough in this case) ./dvbstream -f FREQUENCY -bw 8 -n 30 -c 0 -prog -o:dump.ts 'PROGRAM NAME' wil dump 30 seconds of program to dump.ts, that players such as mplayer, vlc, xine and kaffeine could be able to play. I got a large dump.ts file but none of the suggested programs could play it back. I tried f.ex. mplayer without any special options. Do you want me to upload the dump.ts to ftp://upload.mplayerhq.hu/incoming ? Thanks yes, please ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Video and audio pid problems with dvb-t channels in Norway
Il Wednesday 03 October 2007 08:49:54 Trygve Iversland ha scritto: You are probably right. I tried playing the output from dvbstream in mplayer, and the errors produced were FAAD errors, so th dvb part of it is probably OK. It would be nice to know if you are actually able to play it, so I uploaded NTVstream8192.ts to ftp://upload.mplayerhq.hu/MPlayer/incoming (couldn't find ftp://upload.mplayerhq.hu/incoming). Trygve bad luck: the H264 video streams are encoded with PAFF, for which there are pending patches in ffmpeg-devel (it should be a matter of few days to be committed) while the audio streams are all AAC in LATM syntax for which none of the players I know have a decoder (maybe there's some code in live555 library, I'll give it a look). ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] DiB0700 firmware problems
Sorry for the report delay, I've been without internet connection for some days. Here it goes: 1) system (uname -a) Linux mediacenter 2.6.22-sabayon #1 SMP Wed Jul 11 18:56:46 CEST 2007 i686 AMD Athlon(tm) 64 Processor 3800+ AuthenticAMD GNU/Linux Using the lastest firmware and drivers compiled from HG repository. The date of the dvb-usb-dib0700.ko module (that is, when I pulled the code from HG) is Sept. 11. I also manually added the patch that prevents the repeating of the error messages in dmesg whenever you use another IR control. No other patches were applied. 2) lspci-output 00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2) 00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2) 00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2) 00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2) 00:00.4 RAM memory: nVidia Corporation C51 Memory Controller 4 (rev a2) 00:00.5 RAM memory: nVidia Corporation C51 Host Bridge (rev a2) 00:00.6 RAM memory: nVidia Corporation C51 Memory Controller 3 (rev a2) 00:00.7 RAM memory: nVidia Corporation C51 Memory Controller 2 (rev a2) 00:05.0 VGA compatible controller: nVidia Corporation C51PV [GeForce 6150] (rev a2) 00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2) 00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge (rev a3) 00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a3) 00:0a.2 RAM memory: nVidia Corporation MCP51 Memory Controller 0 (rev a3) 00:0b.0 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3) 00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3) 00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev a1) 00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev a1) 00:10.0 PCI bridge: nVidia Corporation MCP51 PCI Bridge (rev a2) 00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio (rev a2) 00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a3) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 01:03.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev c0) 01:0e.0 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1Controller (rev 61) 01:0e.1 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1Controller (rev 61) 01:0e.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 63) 3) DiB0700 device name (USB Stick, Nova-T 500) Nova-T 500, including its remote. No other DVB or video capture devices present. 4) Application using the device (MythTV, VDR etc) MythTV exclusively (lastest stable version - 0.20.2 - from Gentoo portage). 5) Symptoms (unusable, disconnect after x days, no problem) Mostly stable up to date. I usually have good tunning from both tuners, and the IR is working pretty well. However I keep experiencing ocasional minor but annoying issues like these: - MythTV backend sometimes hang when exploring for EIT data when idle. No error messages appear on dmesg, just it hangs. The last line displayed into /var/log/mythtv/mythbackend.log reads somethink like Now looking for EIT data in multiplex for channel x Whenever this happens the MythTV backend is completely hanged so frontend is unable to connect to it. Restarting the backend usually solves the problem, so I really don't know who must I blame, the card or MythTV itself. - Occasional, isolated, mt2060 read / write errors in dmesg. No problems in MythTV when this happens, thought. - Occasional failed tunnings (yesterday, i.e.). There were no errors displayed in dmesg, but MythTV was unable to acquire a lock on the channel for LiveTV view. I needed to restart the mythbackend a couple of times before it started working fine again. 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: it was something like a total collapse of the USB subsystem, so even the keyboard was responding slowly, about 3-4 sec delay per keypress), needing a complete powercycle of the computer to render it operative again. I'd like to note that, even despite the problems mentioned before, I've had NO USB disconnects since the firmware release. I mean that for any of the problems above (MythTV backend hanging, mt2060 read / write error, etc...) there was no USB disconnect message in dmesg. So for my part this issue seems to be fixed. Anyway: as other times before, let me thank you again for the big amount of work you guys are putting into this. Best
[linux-dvb] Hauppauge Nova-T Stick (and TD)
Hi All Any idea if either the Nova-T Stick or the Nova-TD stick will work and what I should do to get them up? http://www.hauppauge.co.uk/pages/products/data_novatstick.html http://www.hauppauge.co.uk/pages/products/data_novatdstick.html They don¹t ³just work² and I wasn¹t able to find any answers from the linuxtv.org or mythtv (inc. the archive for this list until Oct¹07) I¹m aiming at Unbunt7.04. ³lsusb² shows the sticks are enumerated ok. ³grep -i dvb /var/log/messages² says there might be something amiss... Oct 3 10:12:24 ubuntu-desktop kernel: [ 15.621558] dvb-usb: found a 'Hauppauge Nova-T Stick' in cold state, will try to load a firmware Oct 3 10:12:24 ubuntu-desktop kernel: [ 15.661711] usbcore: registered new interface driver dvb_usb_dib0700 Oct 3 11:00:44 ubuntu-desktop kernel: [ 15.636419] dvb-usb: found a 'Hauppauge Nova-T Stick' in cold state, will try to load a firmware Oct 3 11:00:44 ubuntu-desktop kernel: [ 15.678397] usbcore: registered new interface driver dvb_usb_dib0700 Oct 3 12:10:17 ubuntu-desktop kernel: [ 15.693031] dvb-usb: found a 'Hauppauge Nova-T Stick' in cold state, will try to load a firmware Oct 3 12:10:17 ubuntu-desktop kernel: [ 15.728283] usbcore: registered new interface driver dvb_usb_dib0700 Also ³scan /usr/share/doc/dvb-utils/examples/scan/dvb-t/fi-Tampere /root/.tzap/channels.conf²... ...according to ³http://parker1.co.uk/mythtv_dvb.php further² implies it just ain¹t working... scanning /usr/share/doc/dvb-utils/examples/scan/dvb-t/fi-Tampere using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' main:2247: FATAL: failed to open '/dev/dvb/adapter0/frontend0': 2 No such file or directory I don¹t fear a bit of hard work, but naturally any clues the above gives to a quick solution would be ever so nice. Thanks in advance, Rod. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] RE : Hauppauge Nova-T Stick (and TD)
Have a look at: http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-Stick Get the latest dvb drivers to replace those of your kernel: http://www.linuxtv.org/wiki/index.php/How_to_install_DVB_device_drivers This is as simple as: hg clone http://linuxtv.org/hg/v4l-dvb http://linuxtv.org/hg/v4l-dvbcd cd v4l-dvb make sudo make install after installing mercurial (depends on your distro). Get firmware http://www.wi-bw.tfh-wildau.de/~pboettch/home/linux-dvb-firmware/dvb-usb-dib0700-1.10.fw http://www.wi-bw.tfh-wildau.de/~pboettch/home/linux-dvb-firmware/dvb-usb-dib0700-1.10.fw and rename it as /lib/firmware/dvb-usb-dib0700-03-pre1.fw That's it -Thierry -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Walsh Rod (Nokia-NRC/Tampere) Envoyé : mercredi 3 octobre 2007 11:36 À : linux-dvb@linuxtv.org Objet : [linux-dvb] Hauppauge Nova-T Stick (and TD) Hi All Any idea if either the Nova-T Stick or the Nova-TD stick will work and what I should do to get them up? http://www.hauppauge.co.uk/pages/products/data_novatstick.html http://www.hauppauge.co.uk/pages/products/data_novatdstick.html They dont just work and I wasnt able to find any answers from the linuxtv.org or mythtv (inc. the archive for this list until Oct07) Im aiming at Unbunt7.04. lsusb shows the sticks are enumerated ok. grep -i dvb /var/log/messages says there might be something amiss... Oct 3 10:12:24 ubuntu-desktop kernel: [ 15.621558] dvb-usb: found a 'Hauppauge Nova-T Stick' in cold state, will try to load a firmware Oct 3 10:12:24 ubuntu-desktop kernel: [ 15.661711] usbcore: registered new interface driver dvb_usb_dib0700 Oct 3 11:00:44 ubuntu-desktop kernel: [ 15.636419] dvb-usb: found a 'Hauppauge Nova-T Stick' in cold state, will try to load a firmware Oct 3 11:00:44 ubuntu-desktop kernel: [ 15.678397] usbcore: registered new interface driver dvb_usb_dib0700 Oct 3 12:10:17 ubuntu-desktop kernel: [ 15.693031] dvb-usb: found a 'Hauppauge Nova-T Stick' in cold state, will try to load a firmware Oct 3 12:10:17 ubuntu-desktop kernel: [ 15.728283] usbcore: registered new interface driver dvb_usb_dib0700 Also scan /usr/share/doc/dvb-utils/examples/scan/dvb-t/fi-Tampere /root/.tzap/channels.conf... ...according to http://parker1.co.uk/mythtv_dvb.php further implies it just aint working... scanning /usr/share/doc/dvb-utils/examples/scan/dvb-t/fi-Tampere using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' main:2247: FATAL: failed to open '/dev/dvb/adapter0/frontend0': 2 No such file or directory I dont fear a bit of hard work, but naturally any clues the above gives to a quick solution would be ever so nice. Thanks in advance, Rod. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
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! ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DVB API update
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. Regards, Manu Best Regards, Simon Hailstone On 16/09/2007, *Wolfgang Wegner* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi Manu, On Sun, Sep 16, 2007 at 02:17:55AM +0400, Manu Abraham wrote: Please don't remove the CC's. The CC'd people generally don't bother about mails from the ML, probably. sorry, it was definitely not my intention and I hope to include all previous CC here. [have to read about the multiproto changes myself...] Can you please point me to some ASI specs if you don't mind ? I was once supposed to work on such a device, but then that company itself got scrapped, hence never had to figure out on ASI. Well, AFAIK the ASI specification is not open, so I unfortunately I can not point to it. To be honest, the only thing about ASI comes from a fronted we use at the company in professional equipment, so I am not sure if the things I can tell from there are really valid for all ASI equipment. However, as from time to time questions come up concerning DekTec and other boards, at least some basic support for ASI seems to be desirable. So, coming to the facts, our ASI frontend gives these as statistics: - BER - sync status - 204 or 188 byte/packet mode [...] Since it is an IOCTL call straight away within the V3 API, i would like to push this into the frontend thread where it is submitted as a job kind of thing, where the userapplication can be notified in what timeframe, or via GET_EVENTS, final details can be left out for the last stage. This sounds very reasonable for me. I have no idea yet how this frontend thread is handled now, but after all all necessary information should be present there (e.g. lock state, to do a proper reset of averaging etc.). Scale for BER is one thing that is still open ended, which i am off hook. I need to still check on this, but if you have some ideas would be nice. Hmm... I am not sure what is needed by others, so my voice should not be given too much weight here. We always use 10^-8 as the base, but for some equipment this might already be too rough. On the other hand, IIRC some demodulators do not return more accurate values anyways. Signal Strength SNR: In reality we can provide 2 ways for the same, 1) Relative scale 2) a scale in a decibels Even with Reverse Engineered drivers we can do 1) but for 2) we might need more info. The user could probably select what he needs using an IOCTL, relative or an absolute scale. For the relative one we can just define a floor and ceiling and a relative value is extracted out. That is what I was thinking of, for most applications this would be sufficient. I do not know what is the better solution here. Following your proposal of two different styles of return values makes life easier for the application (which could request the scale type and just take this value). Even knowing the exact decibel value would make it necessary to interpret it differently for different transmission schemes, i.e. 8 dB SNR in DVB-S is no problem while there would be no reception in DVB-C... On the other hand it might be confusing to get different values for the same thing, which I treat as an argument for my proposal of always (if possible) returning the dB value and giving the application (and user) the demod min and max values for drawing a nice percentage scale. For a few demods I could provide the dB calculation (namely STV0299, STV0288, TDA10046, TDA1002x), but probably these are those with fewest problems anyways. For others (e.g. STV0297) there seems to be no calculation possible, I know of other implementations using a look-up-table. If needed, I could do some measurements and see if we manage to get good results with a look-up-table, too. know anything. In some cases people would like to get the absolute value for some instrumentation reasons. It makes comparison of different frontends/setups easier, too. At least in some forums people try to compare their dish and stuff with this, so not only addicts like us might want to see these values. ;-) [Sorry for deleting your most interesting part about silicon tuners - I have not had my hands on one yet, so cannot comment] I understand floating-point is not possible in the kernel, but what other possibilities are
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 IOCTL.. it should be not a tough task to implement a simple LinuxDvb driver, at least for the inbound card (but there's an outgoing path too..), but is this feature valuable? the best usage i can think of, is the dvbsnoop utility for analysis purposes.. anyway i surely can test this driver, if it will spring out! bye andrea venturi Regards, Manu Best Regards, Simon Hailstone On 16/09/2007, *Wolfgang Wegner* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi Manu, On Sun, Sep 16, 2007 at 02:17:55AM +0400, Manu Abraham wrote: Please don't remove the CC's. The CC'd people generally don't bother about mails from the ML, probably. sorry, it was definitely not my intention and I hope to include all previous CC here. [have to read about the multiproto changes myself...] Can you please point me to some ASI specs if you don't mind ? I was once supposed to work on such a device, but then that company itself got scrapped, hence never had to figure out on ASI. Well, AFAIK the ASI specification is not open, so I unfortunately I can not point to it. To be honest, the only thing about ASI comes from a fronted we use at the company in professional equipment, so I am not sure if the things I can tell from there are really valid for all ASI equipment. However, as from time to time questions come up concerning DekTec and other boards, at least some basic support for ASI seems to be desirable. So, coming to the facts, our ASI frontend gives these as statistics: - BER - sync status - 204 or 188 byte/packet mode [...] Since it is an IOCTL call straight away within the V3 API, i would like to push this into the frontend thread where it is submitted as a job kind of thing, where the userapplication can be notified in what timeframe, or via GET_EVENTS, final details can be left out for the last stage. This sounds very reasonable for me. I have no idea yet how this frontend thread is handled now, but after all all necessary information should be present there (e.g. lock state, to do a proper reset of averaging etc.). Scale for BER is one thing that is still open ended, which i am off hook. I need to still check on this, but if you have some ideas would be nice. Hmm... I am not sure what is needed by others, so my voice should not be given too much weight here. We always use 10^-8 as the base, but for some equipment this might already be too rough. On the other hand, IIRC some demodulators do not return more accurate values anyways. Signal Strength SNR: In reality we can provide 2 ways for the same, 1) Relative scale 2) a scale in a decibels Even with Reverse Engineered drivers we can do 1) but for 2) we might need more info. The user could probably select what he needs using an IOCTL, relative or an absolute scale. For the relative one we can just define a floor and ceiling and a relative value is extracted out. That is what I was thinking of, for most applications this would be sufficient. I do not know what is the better solution here. Following your proposal of two different styles of return values makes life easier for the application (which could request the scale type and just take this value). Even knowing the exact decibel value would make it necessary to interpret it differently for different transmission schemes, i.e. 8 dB SNR in DVB-S is no problem while there would be no reception in DVB-C... On the other hand it might be confusing to get different values for the same thing, which I treat as an argument for my proposal of always (if possible) returning the dB value and giving the application (and user) the demod min and max values for drawing a nice percentage scale. For a few demods I could provide the dB calculation (namely STV0299, STV0288, TDA10046, TDA1002x), but probably these are those with fewest problems anyways.
[linux-dvb] RE : linux-dvb and Dektec [was: DVB API update]
IMHO, the Linux DVB framework serves two main purposes: - Common API for the zillions of DVB-S/C/T adapters - Common frontend for TV watching programs such as Myth et al. Dektec products address the market of professional test lab applications using ASI input/output, QPSK/QAM/OFDM modulators output. They address separate needs, separate usage. I have been using both linux-dvb and Dektec products for years and found no real use in integrating both. 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). I develop and use test lab applications for my own usage. I need to receive and send transport streams. I have my own TS processing framework in userland, with input and output plugins (such a trendy term ;-). I have separate input plugins for linux-dvb and Dektec. I have a Dektec output plugin, but none for linux-dvb of course. This is of course a specific professional usage, not a home TV-watching program. Who's going to watch TV at home from an ASI feed ? I think that remaining in userland is better approach for that. At the beginning, before I really understood I went the wrong way, I developed a loopback linux-dvb frontend. It was a kernel driver which integrated with linux-dvb and that was fed by userland applications. The TS coming from these userland applications was presented as coming from a linux-dvb device. Since there is no generic frontend class, my driver pretended to be a QPSK frontend and silently ignored tuning requests. So, a userland application could read a TS from anywhere (a Dektec device, a file, IP multicast, whatever) and feed the dvb loopback driver. Then, any linux-dvb application was able to play with this TS. But, apart from the useless pride of being a kernel code developer, this was totally useless and I gave up this driver. There are simpler userland alternatives for that. Going further, I think (no flame please ;-) that having the full linux-dvb in kernel space has become a conceptual mistake nowadays. The amount of kernel code should remain as small as possible and limited to hardware device access. A software demux has nothing to do in kernel space. IMHO, there should be a userland API that does this. The kernel drivers should report the capabilities of the hardware devices, such as demux. If the device has demux capabilities, the userland code sends the PID filter to the device. Otherwise, the complete TS is passed in userland and demux is done in the API. Demuxing is just one example, all non-hardware related features of linux-dvb should be moved out of the kernel. This is a common disease of open-source developers who are sometimes too much ego-driven: they want to be part of the small kernel coders community and add features in the kernel for fun. It is a well-known debate about the Linux kernel being to bloated. Anyway, coming back to linux-dvb and Dektec, kernel drivers exist for both, just write userland code to access the one you want. -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 IOCTL.. it should be not a tough task to implement a simple LinuxDvb driver, at least for the inbound card (but there's an outgoing path too..), but is this feature valuable? the best usage i can think of, is the dvbsnoop utility for analysis purposes.. anyway i surely can test this driver, if it will spring out! bye andrea venturi Regards, Manu Best Regards, Simon Hailstone On 16/09/2007, *Wolfgang Wegner* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi Manu, On Sun, Sep 16, 2007 at 02:17:55AM +0400, Manu Abraham wrote: Please don't remove the CC's. The CC'd people generally don't bother about mails from the ML, probably. sorry, it was definitely not my intention and I hope to include
[linux-dvb] Problem with Terratec Cinergy HT PCI
Hi, I'm new to linux-tv and i hope this is the right place to find a solution for my troubles ;) I recently bought a Terratec Cinergy HT PCI (hybrid analog/digital card, http://www.linuxtv.org/v4lwiki/index.php/TerraTec_Cinergy_HT_PCI), knowing that it is supported with a recent Linux Kernel (it uses a Philips SAA7133 chipset for analog, but you know that ;)). What I did not know is that i bought a card with an updated chipset, obviously they're building their boards based on a Conexant CX23880 chipset from now on... whatever. This is the output of dmesg: snip cx2388x cx88-mpeg Driver Manager version 0.0.6 loaded cx88[0]: Your board isn't known (yet) to the driver. You can cx88[0]: try to pick one of the existing card configs via cx88[0]: card=n insmod option. Updating to the latest cx88[0]: version might help as well. cx88[0]: Here is a list of valid choices for the card=n insmod option: cx88[0]:card=0 - UNKNOWN/GENERIC cx88[0]:card=1 - Hauppauge WinTV 34xxx models cx88[0]:card=2 - GDI Black Gold cx88[0]:card=3 - PixelView cx88[0]:card=4 - ATI TV Wonder Pro cx88[0]:card=5 - Leadtek Winfast 2000XP Expert cx88[0]:card=6 - AverTV Studio 303 (M126) cx88[0]:card=7 - MSI [EMAIL PROTECTED] Master cx88[0]:card=8 - Leadtek Winfast DV2000 cx88[0]:card=9 - Leadtek PVR 2000 cx88[0]:card=10 - IODATA GV-VCP3/PCI cx88[0]:card=11 - Prolink PlayTV PVR cx88[0]:card=12 - ASUS PVR-416 cx88[0]:card=13 - MSI [EMAIL PROTECTED] cx88[0]:card=14 - KWorld/VStream XPert DVB-T cx88[0]:card=15 - DViCO FusionHDTV DVB-T1 cx88[0]:card=16 - KWorld LTV883RF cx88[0]:card=17 - DViCO FusionHDTV 3 Gold-Q cx88[0]:card=18 - Hauppauge Nova-T DVB-T cx88[0]:card=19 - Conexant DVB-T reference design cx88[0]:card=20 - Provideo PV259 cx88[0]:card=21 - DViCO FusionHDTV DVB-T Plus cx88[0]:card=22 - pcHDTV HD3000 HDTV cx88[0]:card=23 - digitalnow DNTV Live! DVB-T cx88[0]:card=24 - Hauppauge WinTV 28xxx (Roslyn) models cx88[0]:card=25 - Digital-Logic MICROSPACE Entertainment Center (MEC) cx88[0]:card=26 - IODATA GV/BCTV7E cx88[0]:card=27 - PixelView PlayTV Ultra Pro (Stereo) cx88[0]:card=28 - DViCO FusionHDTV 3 Gold-T cx88[0]:card=29 - ADS Tech Instant TV DVB-T PCI cx88[0]:card=30 - TerraTec Cinergy 1400 DVB-T cx88[0]:card=31 - DViCO FusionHDTV 5 Gold cx88[0]:card=32 - AverMedia UltraTV Media Center PCI 550 cx88[0]:card=33 - Kworld V-Stream Xpert DVD cx88[0]:card=34 - ATI HDTV Wonder cx88[0]:card=35 - WinFast DTV1000-T cx88[0]:card=36 - AVerTV 303 (M126) cx88[0]:card=37 - Hauppauge Nova-S-Plus DVB-S cx88[0]:card=38 - Hauppauge Nova-SE2 DVB-S cx88[0]:card=39 - KWorld DVB-S 100 cx88[0]:card=40 - Hauppauge WinTV-HVR1100 DVB-T/Hybrid cx88[0]:card=41 - Hauppauge WinTV-HVR1100 DVB-T/Hybrid (Low Profile) cx88[0]:card=42 - digitalnow DNTV Live! DVB-T Pro cx88[0]:card=43 - KWorld/VStream XPert DVB-T with cx22702 cx88[0]:card=44 - DViCO FusionHDTV DVB-T Dual Digital cx88[0]:card=45 - KWorld HardwareMpegTV XPert cx88[0]:card=46 - DViCO FusionHDTV DVB-T Hybrid cx88[0]:card=47 - pcHDTV HD5500 HDTV cx88[0]:card=48 - Kworld MCE 200 Deluxe cx88[0]:card=49 - PixelView PlayTV P7000 cx88[0]:card=50 - NPG Tech Real TV FM Top 10 cx88[0]:card=51 - WinFast DTV2000 H cx88[0]:card=52 - Geniatech DVB-S cx88[0]:card=53 - Hauppauge WinTV-HVR3000 TriMode Analog/DVB-S/DVB-T cx88[0]:card=54 - Norwood Micro TV Tuner cx88[0]:card=55 - Shenzhen Tungsten Ages Tech TE-DTV-250 / Swann OEM cx88[0]:card=56 - Hauppauge WinTV-HVR1300 DVB-T/Hybrid MPEG Encoder CORE cx88[0]: subsystem: 153b:1177, board: UNKNOWN/GENERIC [card=0,autodetected] TV tuner -1 at 0x1fe, Radio tuner -1 at 0x1fe cx2388x v4l2 driver version 0.0.6 loaded cx88[0]/2: cx2388x 8802 Driver Manager ACPI: PCI Interrupt :03:02.0[A] - GSI 18 (level, low) - IRQ 18 cx88[0]: Your board isn't known (yet) to the driver. You can cx88[0]: try to pick one of the existing card configs via cx88[0]: card=n insmod option. Updating to the latest cx88[0]: version might help as well. cx88[0]: Here is a list of valid choices for the card=n insmod option: cx88[0]:card=0 - UNKNOWN/GENERIC cx88[0]:card=1 - Hauppauge WinTV 34xxx models cx88[0]:card=2 - GDI Black Gold cx88[0]:card=3 - PixelView cx88[0]:card=4 - ATI TV Wonder Pro cx88[0]:card=5 - Leadtek Winfast 2000XP Expert cx88[0]:card=6 - AverTV Studio 303 (M126) cx88[0]:card=7 - MSI [EMAIL PROTECTED] Master cx88[0]:card=8 - Leadtek Winfast DV2000 cx88[0]:card=9 - Leadtek PVR 2000 cx88[0]:card=10 - IODATA GV-VCP3/PCI cx88[0]:card=11 - Prolink PlayTV PVR cx88[0]:card=12 - ASUS PVR-416 cx88[0]:card=13 - MSI [EMAIL PROTECTED] cx88[0]:card=14 - KWorld/VStream XPert DVB-T cx88[0]:card=15 - DViCO FusionHDTV DVB-T1 cx88[0]:card=16 - KWorld LTV883RF cx88[0]:card=17 - DViCO FusionHDTV 3 Gold-Q
[linux-dvb] compiling is broken
Hi, this changset: Fix Kconfig dependency author Mauro Carvalho Chehab [EMAIL PROTECTED] Tue Oct 02 11:16:16 2007 -0300 (30 hours ago) changeset 6260 48badb1df2ed manifest48badb1df2ed parent 6259 6129aac33d3e child 6261 8e7bc314eb82 Fix Kconfig dependency breaks compiling. I get the following error: make -C /lib/modules/2.6.23-rc8-up-64-test/build SUBDIRS=/usr/src/v4l-dvb/v4l modules make[2]: Entering directory `/usr/src/linux-2.6.23-rc8' CC [M] /usr/src/v4l-dvb/v4l/saa7134-dvb.o /usr/src/v4l-dvb/v4l/saa7134-dvb.c: In function 'philips_europa_demod_sleep': /usr/src/v4l-dvb/v4l/saa7134-dvb.c:415: error: 'struct saa7134_dev' has no member named 'original_demod_sleep' /usr/src/v4l-dvb/v4l/saa7134-dvb.c:416: error: 'struct saa7134_dev' has no member named 'original_demod_sleep' /usr/src/v4l-dvb/v4l/saa7134-dvb.c: In function 'configure_tda827x_fe': /usr/src/v4l-dvb/v4l/saa7134-dvb.c:557: error: 'struct saa7134_dev' has no member named 'dvb' ... make[3]: *** [/usr/src/v4l-dvb/v4l/saa7134-dvb.o] Error 1 make[2]: *** [_module_/usr/src/v4l-dvb/v4l] Error 2 make[2]: Leaving directory `/usr/src/linux-2.6.23-rc8' make[1]: *** [default] Fehler 2 make[1]: Leaving directory `/usr/src/v4l-dvb/v4l' make: *** [all] Fehler 2 - Hartmut ___ 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, On Wed, Oct 03, 2007 at 04:42:20PM +0200, Thierry Lelegard wrote: IMHO, the Linux DVB framework serves two main purposes: - Common API for the zillions of DVB-S/C/T adapters - Common frontend for TV watching programs such as Myth et al. Dektec products address the market of professional test lab applications using ASI input/output, QPSK/QAM/OFDM modulators output. They address separate needs, separate usage. it depends. 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. Best regards, Wolfgang ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] compiling is broken
Am Mittwoch, den 03.10.2007, 22:59 +0200 schrieb e9hack: Hi, this changset: Fix Kconfig dependency authorMauro Carvalho Chehab [EMAIL PROTECTED] Tue Oct 02 11:16:16 2007 -0300 (30 hours ago) changeset 626048badb1df2ed manifest 48badb1df2ed parent 6259 6129aac33d3e child 62618e7bc314eb82 Fix Kconfig dependency breaks compiling. I get the following error: make -C /lib/modules/2.6.23-rc8-up-64-test/build SUBDIRS=/usr/src/v4l-dvb/v4l modules make[2]: Entering directory `/usr/src/linux-2.6.23-rc8' CC [M] /usr/src/v4l-dvb/v4l/saa7134-dvb.o /usr/src/v4l-dvb/v4l/saa7134-dvb.c: In function 'philips_europa_demod_sleep': /usr/src/v4l-dvb/v4l/saa7134-dvb.c:415: error: 'struct saa7134_dev' has no member named 'original_demod_sleep' /usr/src/v4l-dvb/v4l/saa7134-dvb.c:416: error: 'struct saa7134_dev' has no member named 'original_demod_sleep' /usr/src/v4l-dvb/v4l/saa7134-dvb.c: In function 'configure_tda827x_fe': /usr/src/v4l-dvb/v4l/saa7134-dvb.c:557: error: 'struct saa7134_dev' has no member named 'dvb' ... make[3]: *** [/usr/src/v4l-dvb/v4l/saa7134-dvb.o] Error 1 make[2]: *** [_module_/usr/src/v4l-dvb/v4l] Error 2 make[2]: Leaving directory `/usr/src/linux-2.6.23-rc8' make[1]: *** [default] Fehler 2 make[1]: Leaving directory `/usr/src/v4l-dvb/v4l' make: *** [all] Fehler 2 - Hartmut What a sad story. ;) Any fixes? Cheers, Hermann ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] compiling is broken
Am Donnerstag, den 04.10.2007, 03:16 +0200 schrieb hermann pitton: Am Mittwoch, den 03.10.2007, 22:59 +0200 schrieb e9hack: Hi, this changset: Fix Kconfig dependency author Mauro Carvalho Chehab [EMAIL PROTECTED] Tue Oct 02 11:16:16 2007 -0300 (30 hours ago) changeset 6260 48badb1df2ed manifest48badb1df2ed parent 6259 6129aac33d3e child 6261 8e7bc314eb82 Fix Kconfig dependency breaks compiling. I get the following error: make -C /lib/modules/2.6.23-rc8-up-64-test/build SUBDIRS=/usr/src/v4l-dvb/v4l modules make[2]: Entering directory `/usr/src/linux-2.6.23-rc8' CC [M] /usr/src/v4l-dvb/v4l/saa7134-dvb.o /usr/src/v4l-dvb/v4l/saa7134-dvb.c: In function 'philips_europa_demod_sleep': /usr/src/v4l-dvb/v4l/saa7134-dvb.c:415: error: 'struct saa7134_dev' has no member named 'original_demod_sleep' /usr/src/v4l-dvb/v4l/saa7134-dvb.c:416: error: 'struct saa7134_dev' has no member named 'original_demod_sleep' /usr/src/v4l-dvb/v4l/saa7134-dvb.c: In function 'configure_tda827x_fe': /usr/src/v4l-dvb/v4l/saa7134-dvb.c:557: error: 'struct saa7134_dev' has no member named 'dvb' ... make[3]: *** [/usr/src/v4l-dvb/v4l/saa7134-dvb.o] Error 1 make[2]: *** [_module_/usr/src/v4l-dvb/v4l] Error 2 make[2]: Leaving directory `/usr/src/linux-2.6.23-rc8' make[1]: *** [default] Fehler 2 make[1]: Leaving directory `/usr/src/v4l-dvb/v4l' make: *** [all] Fehler 2 - Hartmut What a sad story. ;) Any fixes? without jokes now, the _current_ v4l-dvb master repo builds without problems here. 2.6.23-rc6-git3 #1 PREEMPT Fri Sep 14 20:44:27 CEST 2007 i686 athlon i386 GNU/Linux gcc (GCC) 4.1.2 20070626 (Red Hat 4.1.2-13) Can't be much left in between. Cheers, Hermann ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] compiling is broken
On Thu, 4 Oct 2007, hermann pitton wrote: Am Mittwoch, den 03.10.2007, 22:59 +0200 schrieb e9hack: this changset: Fix Kconfig dependency author Mauro Carvalho Chehab [EMAIL PROTECTED] Tue Oct 02 11:16:16 2007 -0300 (30 hours ago) changeset 6260 48badb1df2ed breaks compiling. I get the following error: /usr/src/v4l-dvb/v4l/saa7134-dvb.c:415: error: 'struct saa7134_dev' has no member named 'original_demod_sleep' That patch (in combination with some others) renamed the config variable VIDEO_BUF_DVB to VIDEOBUF_DVB. Some code, like saa7134.h, was not updated and is still looking at CONFIG_VIDEO_BUF_DVB. There is a script I wrote called check_config_defines.pl that should find stuff like this, but in this case it misses it. The kernel source defines CONFIG_VIDEO_BUF_DVB since it has all the old code in it, so it doesn't appear to be missing. I fixed the script so it uses the v4l-dvb Kconfig replace the corresponding kernel files, as opposed to be combined when them. Now it finds the errors: Unknown config CONFIG_VIDEO_BUF_DVB in linux/drivers/media/video/cx23885/cx23885.h:31 Unknown config CONFIG_VIDEO_BUF_DVB in linux/drivers/media/video/cx88/cx88-i2c.c:156 Unknown config CONFIG_VIDEO_BUF_DVB in linux/drivers/media/video/cx88/cx88.h:34 Unknown config CONFIG_VIDEO_BUF_DVB in linux/drivers/media/video/cx88/cx88.h:320 Unknown config CONFIG_VIDEO_BUF_DVB in linux/drivers/media/video/cx88/cx88.h:494 Unknown config CONFIG_VIDEO_BUF_DVB in linux/drivers/media/video/saa7134/saa7134.h:51 Unknown config CONFIG_VIDEO_BUF_DVB in linux/drivers/media/video/saa7134/saa7134.h:562 I wonder if instead of changing these to CONFIG_VIDEOBUF_DVB, it would be better to use CONFIG_VIDEO_SAA7134_DVB, CONFIG_VIDEO_CX88_DVB, etc. One could always have a cx88 card with DVB and a saa7134 card without dvb. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] help for better support of Creatix CTX953 card
Hello, I am trying to switch to Linux (Ubuntu 7.04 64bits). I have a Medion MD 6426 (PC Medion SYS 6426.01 (FR)) CPU : Intel Code 2 Duo E6600 Under windows : Hybrid Card : Creatix SAA7131, Hybrid Capture Device (PCI\VEN_1131DEV_7133SUBSYS_001016BEREV_D1 = model CTX 953) lspci -v 02:00.0 Multimedia controller: Philips Semiconductors SAA7133/SAA7135 Video Broadcast Decoder (rev d1) Subsystem: Creatix Polymedia GmbH Unknown device 0010 Flags: bus master, medium devsel, latency 84, IRQ 16 Memory at fddff000 (32-bit, non-prefetchable) [size=2K] Capabilities: [40] Power Management version 2 lspci -nv 02:03.0 0c00: 1106:3044 (rev c0) (prog-if 10 [OHCI]) Subsystem: 1462:324d Flags: bus master, medium devsel, latency 64, IRQ 20 Memory at fddfe000 (32-bit, non-prefetchable) [size=2K] I/O ports at ef00 [size=128] Capabilities: [50] Power Management version 2 According to http://www.creatix.com/produkte/multimedia/ctx953.htm (data sheet) CTX953_V.1.3.1 TV/DVB-T-Tuner Card CTX953_V.1.3.1 supports analog TV, DVB-T, FM and S-Video/ Composite Video-In/Audio-In internal and at the bracket side. - PCI 2.2 compliant RoHS compliant Philips SAA7131E, TDA8275A, TDA10046 Philips SAA7131E Features: The SAA7131E combines a digital global standard low IF demodulator for analog TV with a PCI audio and video decoder. The IF demodulator is an alignment-free digital multi standard vision and sound low IF signal PLL demodulator for positive and negative video modulation. It can be used worldwide for M/N, B/G/H, I, D/K and L/L' standards. Analog/DVB-T section (Philips TDA8275A) Features: - 3 Stand-by mode functions - 1 Sleep mode function - Low symmetrical IF output (centered at 4MHz, 4.5MHz or 5MHz) for a direct connection to the TDA8290 (IF demodulator) or the SAA7131 or SAA7171 (IF demodulator and video decoder) or channel decoder - Fully integrated oscillators with no external components - Fully integrated selectivity - Crystal oscillator output buffer (16MHz) to drive the IF demodulator and digital decoder and occasionally another tuner - Operating range from an ambient temperature of -20°C to a max ambient temperature compatible with Tjmax TDA10046AHT: - 2K and 8K COFDM demodulator (Fully DVB-T compliant: ETS 300- 744). - All modes supported including hierarchical modes. - Fully automatic Transmission Parameters detection (including FFT size and Guard Interval). - DSP based synchronization - No extra-host software required. - UHF/VHF Band Fast Scan. - Digital Frequency correction (± 90 KHz) - Frequency offset (from ± 1/6 to ± 3/6 MHz) automatic detection. - Simultaneous Parallel and Serial Transport stream interfaces. - I2C Bus interface I can use the DVB-T card following this procedure : 1) boot under Vista and use the DVB-T card under Windows Media Center 2) reboot under Ubuntu 7.04 64b 3) rmmod saa7134-dvb ; rmmod saa7134 modprobe saa7134 card=96 modprobe saa7134-dvb 4) launch kdeTV to watch an analogic TV (Secam-L) and quit (the first time, I had to search for the channels) 5) vlc dvb:// --dvb-frequency=586166000 --dvb-adapter=0 --dvb-bandwidth=8 --program=261 remark : I tried klear, mplayer, kaffeine, with success using fr-Paris : # Paris - France (DVB-T transmitter of the Eiffel tower) # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy # /home/moi/.kde/share/apps/kaffeine/dvb-t/fr-Paris T 474166000 8MHz 2/3 NONE QAM64 8k 1/32 NONE T 498166000 8MHz 2/3 NONE QAM64 8k 1/32 NONE T 522166000 8MHz 2/3 NONE QAM64 8k 1/32 NONE T 538166000 8MHz 2/3 NONE QAM64 8k 1/32 NONE T 562166000 8MHz 2/3 NONE QAM64 8k 1/32 NONE T 586166000 8MHz 3/4 NONE QAM64 8k 1/8 NONE here is the dmesg : [ 529.313023] saa7130/34: v4l2 driver version 0.2.14 loaded [ 529.313152] saa7133[0]: found at :02:00.0, rev: 209, irq: 16, latency: 84, mmio: 0xfddff000 [ 529.313160] saa7133[0]: subsystem: 16be:0010, board: Medion Md8800 Quadro [card=96,insmod option] [ 529.313392] saa7133[0]: board init: gpio is 0 [ 529.489067] tuner 0-004b: chip found @ 0x96 (saa7133[0]) [ 529.536965] tuner 0-004b: setting tuner address to 60 [ 529.576942] tuner 0-004b: type set to tda8290+75a [ 529.688701] tuner 0-004b: setting tuner address to 60 [ 529.728631] tuner 0-004b: type set to tda8290+75a [ 529.828458] saa7133[0]: i2c eeprom 00: be 16 10 00 54 20 1c 00 43 43 a9 1c 55 d2 b2 92 [ 529.828468] saa7133[0]: i2c eeprom 10: 00 ff 86 0f ff 20 ff 00 01 50 32 79 01 3c ca 50 [ 529.828476] saa7133[0]: i2c eeprom 20: 01 40 01 02 02 03 01 00 06 ff 00 2c 02 51 96 2b [ 529.828484] saa7133[0]: i2c eeprom 30: a7 58 7a 1f 03 8e 84 5e da 7a 04 b3 05 87 b2 3c [ 529.828493] saa7133[0]: i2c eeprom 40: ff 21 00 c0 96 10 03 22 15 00 fd 79 44 9f c2 8f [ 529.828501] saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 529.828509] saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [
