[linux-dvb] Re: IR Device - Nova-T 500
On Mon Oct 16, 2006 at 11:35:20PM +0100, Iain Macaulay wrote: First off a big thanks to everyone who worked on the Wintv Nova-T 500 Dual DVB modules ( special thanks to *Patrick Boettcher)* I am using the v4l-dvb-988fa3182bb3 cvs and it works a treat, both interfaces! Only question I have is about the 'remote in'/IR is it supported? I am not complaining at all but would just like to know if anyone has cracked it yet. Any help/advice would be really appreciated. On Ubuntu dapper (2.6.15-27) using Myth 0.20. No, the remote's not currently supported. I've got a dual boot PC set up to look into it, but I'm currently having issues with my main PC so I've not done much yet. Cheers, Robin -- ___ ( ' } | Robin Hill [EMAIL PROTECTED] | / / ) | Little Jim says | // !! | He fallen in de water !! | pgplp06zHJXJJ.pgp Description: PGP signature ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] MPE pointer field too big
Hello everybody! Some of the MPEG-TS packets I receive contain a pointer field bigger than 184 (continuity counter is correct). How to explain that? Shouldn't Pointer field be inside 0 and 184? Any comments? AnneSophie. ___ 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] MPE pointer field too big
Harnois Anne-Sophie wrote: Hello everybody! Some of the MPEG-TS packets I receive contain a pointer field bigger than 184 (continuity counter is correct). How to explain that? Shouldn't Pointer field be inside 0 and 184? Any comments? AnneSophie. maybe for some strange reason it spans over the next ts packets of the same pid; I don't remember if it's allowed in the standard ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
RE: [linux-dvb] MPE pointer field too big
I check for that, and no, it doesn't span over the next ts packets of the same PID. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nico Sabbi Sent: mardi 17 octobre 2006 11:39 To: linux-dvb Subject: Re: [linux-dvb] MPE pointer field too big Harnois Anne-Sophie wrote: Hello everybody! Some of the MPEG-TS packets I receive contain a pointer field bigger than 184 (continuity counter is correct). How to explain that? Shouldn't Pointer field be inside 0 and 184? Any comments? AnneSophie. maybe for some strange reason it spans over the next ts packets of the same pid; I don't remember if it's allowed in the standard ___ 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] Pinnacle 400e USB DVB-S something to try
Patrick Boettcher wrote:
Hi all,
I just finished something that seem to drive the Pinnacle PCTV 400e
correctly.
I encourage every owner of such a device to try the driver from:
http://linuxtv.org/hg/~pb/v4l-dvb.ttusb2
with the firmware from here:
http://thadathil.net:8000/dvb/fw/dvb-usb/dvb-usb-pctv-400e-01.fw
Good luck and don't forget to report success or failure,
hi,
i have this pctv400e and i tried today with this experimental branch.
this is just a first report; more details if needed.
no problem compiling and loading driver firmware (on my compiled
2.6.17 kernel)
usb 5-2.1: new high speed USB device using ehci_hcd and address 7
usb 5-2.1: configuration #1 chosen from 1 choice
dvb-usb: found a 'Pinnacle 400e DVB-S USB2.0' in cold state, will try to
load a firmware
dvb-usb: downloading firmware from file 'dvb-usb-pctv-400e-01.fw'
usb 5-2.1: USB disconnect, address 7
dvb-usb: generic DVB-USB module successfully deinitialized and disconnected.
usb 5-2.1: new high speed USB device using ehci_hcd and address 8
usb 5-2.1: configuration #1 chosen from 1 choice
dvb-usb: found a 'Pinnacle 400e DVB-S USB2.0' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software
demuxer.
DVB: registering new adapter (Pinnacle 400e DVB-S USB2.0).
DVB: registering frontend 0 (Philips TDA10086 DVB-S)...
dvb-usb: Pinnacle 400e DVB-S USB2.0 successfully initialized and connected.
===
now comes the problem..
when i try this dvbstream dump on BBC (eurobird1 28.5)
[EMAIL PROTECTED]:/tmp$ dvbstream -f 10847 -p V -o 8192 /dev/null
dvbstream v0.6 - (C) Dave Chapman 2001-2004
Released under the GPL.
Latest version available from http://www.linuxstb.org/
Tuning to 10847 Hz
Using DVB card Philips TDA10086 DVB-S, freq=10847
tuning DVB-S to Freq: 1097000, Pol:V Srate=0, 22kHz tone=off, LNB: 0
Setting only tone OFF and voltage 13V
DISEQC SETTING SUCCEDED
Getting frontend status
the application hangs here (of course i missed the 000 in the freq
param!), and in dmesg, i can see this error:
dvb-usb: Pinnacle 400e DVB-S USB2.0 successfully initialized and connected.
divide error: [#1]
PREEMPT
Modules linked in: lnbp21 tda826x tda10086 dvb_usb_ttusb2 dvb_usb
dvb_core dvb_pll vmnet vmmon rfco
mm l2cap bluetooth ipv6 autofs4 thermal fan button ac battery i2c_i801
speedstep_centrino freq_tabl
e processor nvidia i2c_core usbhid usb_storage 8250_pci snd_intel8x0m
snd_intel8x0 8250_pnp snd_ac9
7_codec snd_ac97_bus pcmcia snd_pcm_oss snd_mixer_oss crc32 snd_pcm
snd_timer ipw2200 snd soundcore
ieee80211 ieee80211_crypt irda ehci_hcd uhci_hcd psmouse intel_agp
agpgart snd_page_alloc yenta_so
cket rsrc_nonstatic pcspkr evdev firmware_class 8250 rtc parport_pc
parport crc_ccitt tg3 usbcore s erial_core
CPU:0
EIP:0060:[f8bd79df]Tainted: P VLI
EFLAGS: 00210246 (2.6.17 #1)
EIP is at tda10086_set_frontend+0x311/0x3f6 [tda10086]
eax: 002edfff ebx: ecx: edx:
esi: edi: 0004 ebp: db13df6c esp: db13df3c
ds: 007b es: 007b ss: 0068
Process kdvb-fe-0 (pid: 11106, threadinfo=db13c000 task=da7670f0)
Stack: 0108 f3d57a00 000176ff
04004343
0010bd28 d9d82400 f3d57a08 db13df94 f8ccb631 f3d57a08
d9d82404
0002 0010bd28 d9d82400 f3d57a08 db13dfc4 db13dfa8
f8ccbdd2
Call Trace:
c0103d58 show_stack_log_lvl+0x85/0x8f c0103ee6
show_registers+0x14f/0x1c3
c01040b7 die+0x15d/0x231 c0104205 do_trap+0x7a/0x98
c01047be do_divide_error+0x87/0x91 c010381f error_code+0x4f/0x54
f8ccb631 dvb_frontend_swzigzag_autotune+0x17d/0x1a8 [dvb_core]
f8ccbdd2 dvb_frontend_swzigzag +0x1a5/0x206 [dvb_core]
f8cccb2f dvb_frontend_thread+0x25c/0x2de [dvb_core] c0101005
kernel_thread_helper+0x5/0xb
Code: ff ff 8b 45 e4 89 d9 ba 07 00 00 00 c1 eb 08 e8 04 fb ff ff 8b 45
e4 89 d9 ba 08 00 00 00 e8 f5 fa ff ff 8d 86 ff df 2e
00 31 d2 f7 f6 ba 09 00 00 00 89 c1 8b 45 e4 e8 dc fa ff ff 0f b6 4d e
d
EIP: [f8bd79df] tda10086_set_frontend+0x311/0x3f6 [tda10086] SS:ESP
0068:db13df3c
that's all as a first report. let me know if you need more info.
bye
andrea venturi
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] DiB7000M-driver released (Nova-T Stick, AverMedia and others)
Hi, in my repository (http://linuxtv.org/hg/~pb/v4l-dvb) I just committed a first working version of the dib7000m/p-driver along with some modifications in the dib0700-driver. I tested with a first generation Nova-T stick - it works (AverMedia is identical). There is a chance that someone has the newer version of those devices - it contains a different version of the DiB7000 - I will try to release this one as soon as possible. Please load the dib7000m-driver with debug=1 in case it does not work and reply to this Email but change the subject (like: Problem (was: DiB7000M ...) - success reports (Yes I want them as well) can be replied without changing the subject. good luck, Patrick. -- Mail: [EMAIL PROTECTED] WWW: http://www.wi-bw.tfh-wildau.de/~pboettch/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Mantis VP-1027/VP-1033/VP-1034/VP-2033/VP-3033
modprobe mantis goes fine now. I'll try some more thing tomorrow. Thanx! Op dinsdag 17 oktober 2006 07:39, schreef Michel Verbraak: Joep, After the copy do not forget to do the *depmod -a* command as root. Michel. Michel Verbraak schreef: joep admiraal schreef: Hello I downloaded the code from Manu. It compiled without any problems. When I do a modprobe mantis I get the following message: Error inserting mantis (/lib/modules/2.6.16.21-0.13-default/kernel/drivers/media/dvb/mantis/man tis.ko): Unknown symbol in module, or unknown parameter (see dmesg) dmesg gives me: mantis: Unknown symbol cu1216_attach Joep, The cu1216.ko module needs to be copied by hand to the modules directory /lib/moduleskernel version/kernel/drivers/media/dvb/frontends Copy it from the directory /mantis-25021de30f36/v4l. Does anyone knows what I could be doing wrong? Thanks, Joep Admiraal ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb Regards, Michel. ___ 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] MPE pointer field too big
Hi, On Tuesday 17 October 2006 11:36, Harnois Anne-Sophie wrote: Hello everybody! Some of the MPEG-TS packets I receive contain a pointer field bigger than 184 (continuity counter is correct). How to explain that? Shouldn't Pointer field be inside 0 and 184? Any comments? Can you send a hexdump of that packet? thanks, Dominik ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Pinnacle pctv 300i - DVB is ok in france !
Hi, leaving in france, I recently managed to get my pinnacle pctv 310i card running in both analogic and numeric mode by shifting forward by 167 kHz each channel frequency in the tuning data file for dvb. I would like to report here that using the same method I coud help a french ubuntu user on the french ubuntu forum to make his pctv 300i card dvb running. So, pctv 300i is working in dvb mode in france by shifting forward by 167 kHz each channel frequency in the tuning data file. Unluckily we could not make this card running in analogic mode. The tv norm in france is secam and in v4l-dvb cards list this card appears like : Pinnacle PCTV 300i DVB-T + PAL. Does its tuner support SECAM norm ? Does issue existing for french user ? Thanks. Cabrito ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] LifeView FlyDVB-T Hybrid PCI
Hi, The kernel 2.6.18 supports the cards LifeView FlyDVB-T PCI, FlyDVB-T DUO PCI, FlyDVB-T Duo Cardbus, FlyDVB-T Hybrid Cardbus. But, will the card FlyDVB-T Hybrid PCI be supported soon? Regards. -- == | FREDERIC MASSOT | | http://www.juliana-multimedia.com | | mailto:[EMAIL PROTECTED] | ===Debian=GNU/Linux=== ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] TTUSB DEC-2000T Driver: tuning problems
Mario Rossi schrieb:
IIRC DMX_PES_OTHER is the correct pid filter, while DMX_PES_AUDIO and
_VIDEO
were used only by FF cards
... and all devices driven by the ttusb-dec driver ;)
This is the same thing I've read.
The card has a MPEG-decoder but it is not possible to use it from USB
(it works when connecting the card to television), so I am not sure
whether it is a FF card or not.
Reading the source code, in
linux/drivers/media/dvb/ttusb-dec/ttusb_dec.c I can find a lot of
support for _PES_AUDIO and _PES_VIDEO while (apparently) nothing for
_PES_OTHER.
It's not really a FF card as the MPEG-decoder is not used when connected to
a pc, as you said. However the card does the initial processing of the TS
stream,
and sends only the extracted MPEG ES stream for video and the MPEG PES stream
for audio(iirc).
It not possible to just get a part of the TS stream by setting an arbitrary PID
filter.
It is only possible to tell the device which PIDs belong to the video/audio
stream.
So using DMX_PES_OTHER is not possible.
An application can simply try DMX_PES_OTHER first and if -ENOTSUPPORTED is
returned,
as it would be the case here, it can fallback to DMX_PES_{AUDIO,VIDEO}.
Mythtv does it this way afaik.
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Pinnacle pctv 300i - DVB is ok in france !
Hi Cabrito, Am Dienstag, den 17.10.2006, 17:17 +0200 schrieb Cabrito Estrabico: Hi, leaving in france, I recently managed to get my pinnacle pctv 310i card running hmm, 300i and 310i are very different cards. in both analogic and numeric mode by shifting forward by 167 kHz each channel frequency in the tuning data file for dvb. I would like to report here that using the same method I coud help a french ubuntu user on the french ubuntu forum to make his pctv 300i card dvb running. So, pctv 300i is working in dvb mode in france by shifting forward by 167 kHz each channel frequency in the tuning data file. Unluckily we could not make this card running in analogic mode. The tv norm in france is secam and in v4l-dvb cards list this card appears like : Pinnacle PCTV 300i DVB-T + PAL. Does its tuner support SECAM norm ? Does issue existing for french user ? Yes, there is another pitfall for french users. You need option secam=l for the tuner module. Only the recent mercurial with Hartmut's latest audio fixes allows to select SECAM-L directly from an app like xawtv. Only in case it is a 310i with saa7131e, option audio_ddep=10 for saa7134 might help as well to force NICAM stereo, but isn't the best choice if you have also MONO analog broadcast. Good Luck, Hermann ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Problem: dib7000m don't know my vendor
Am Dienstag, den 17.10.2006, 14:54 +0200 schrieb Patrick Boettcher: Hi, in my repository (http://linuxtv.org/hg/~pb/v4l-dvb) I just committed a first working version of the dib7000m/p-driver along with some modifications in the dib0700-driver. I tested with a first generation Nova-T stick - it works (AverMedia is identical). There is a chance that someone has the newer version of those devices - it contains a different version of the DiB7000 - I will try to release this one as soon as possible. Please load the dib7000m-driver with debug=1 in case it does not work and reply to this Email but change the subject (like: Problem (was: DiB7000M ...) - success reports (Yes I want them as well) can be replied without changing the subject. good luck, Patrick. -- Mail: [EMAIL PROTECTED] WWW: http://www.wi-bw.tfh-wildau.de/~pboettch/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb Hi, I've just checked out Patrick's repository and give the (new) dib7000m-driver a first try. Kernel is 2.6.17-686 (ubuntu edgy). The dvb-adapter is a hauppauge wintv nova t usb2. This is what lsusb says: Bus 004 Device 003: ID 2040:7050 Hauppauge And now the syslog: [17179761.14] usb 4-2: new high speed USB device using ehci_hcd and address 3 [17179761.272000] usb 4-2: configuration #1 chosen from 1 choice [17179761.504000] dib0700: loaded with support for 2 different device-types [17179761.504000] dvb-usb: found a 'Hauppauge Nova-T Stick' in cold state, will try to load a firmware [17179761.512000] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-01.fw' [17179761.696000] dib0700: firmware started successfully. [17179761.80] dvb-usb: found a 'Hauppauge Nova-T Stick' in warm state. [17179761.80] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [17179761.80] DVB: registering new adapter (Hauppauge Nova-T Stick). [17179761.864000] DiB7000M:-E- DiB7000M: wrong Vendor ID (read=0x0) [17179761.864000] dvb-usb: no frontend was attached by 'Hauppauge Nova-T Stick' [17179761.864000] dvb-usb: Hauppauge Nova-T Stick successfully initialized and connected. [17179761.864000] usbcore: registered new driver dvb_usb_dib0700 Christian ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DiB7000M-driver released (Nova-T Stick, AverMedia and others)
On 10/17/06, Patrick Boettcher [EMAIL PROTECTED] wrote: Hi,in my repository (http://linuxtv.org/hg/~pb/v4l-dvb) I just committed afirst working version of the dib7000m/p-driver along with somemodifications in the dib0700-driver. I tested with a first generation Nova-T stick - it works (AverMedia isidentical). There is a chance that someone has the newer version of thosedevices - it contains a different version of the DiB7000 - I will try to release this one as soon as possible.Please load the dib7000m-driver with debug=1 in case it does not work andreply to this Email but change the subject (like: Problem (was: DiB7000M...) - success reports (Yes I want them as well) can be replied without changing the subject.good luck,Patrick.--Mail: [EMAIL PROTECTED]WWW:http://www.wi-bw.tfh-wildau.de/~pboettch/ ___linux-dvb mailing listlinux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvbHi,I just successfully tested your driver for dib7000p using kernel 2.6.16.21-0.25-default (opensuse 10.1).I am using Compro Videomate U500 (VID 0x185b, PID 0x1e78), I had to add pid to dvb-usb-ids.h and few lines to dib0700_devices.c so that my device was correctly detected. After that it looks like it is working. I will continue testing it.Tomi Koivulahti ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Pinnacle pctv 300i - DVB is ok in france !
Hi, all hermann pitton wrote: Hi Cabrito, Am Dienstag, den 17.10.2006, 17:17 +0200 schrieb Cabrito Estrabico: Hi, leaving in france, I recently managed to get my pinnacle pctv 310i card running hmm, 300i and 310i are very different cards. in both analogic and numeric mode by shifting forward by 167 kHz each channel frequency in the tuning data file for dvb. I would like to report here that using the same method I coud help a french ubuntu user on the french ubuntu forum to make his pctv 300i card dvb running. So, pctv 300i is working in dvb mode in france by shifting forward by 167 kHz each channel frequency in the tuning data file. Unluckily we could not make this card running in analogic mode. The tv norm in france is secam and in v4l-dvb cards list this card appears like : Pinnacle PCTV 300i DVB-T + PAL. Does its tuner support SECAM norm ? Does issue existing for french user ? Yes, there is another pitfall for french users. You need option secam=l for the tuner module. Only the recent mercurial with Hartmut's latest audio fixes allows to select SECAM-L directly from an app like xawtv. Only in case it is a 310i with saa7131e, option audio_ddep=10 for saa7134 might help as well to force NICAM stereo, but isn't the best choice if you have also MONO analog broadcast. Good Luck, Hermann Do we really talk about the 300i? As Hermann mentioned, this card is very different from the 310i. I was on the opiniton that the channel decoder of this card would find the 167kHz offset automatically... I am not sure whether the option secam=l will help. This depends on the so-called SAW filter on the card. But it is worth a try and if it works, please leave us a note. Just one additional note: If you use the recent code from the repository, you should apply the secam=l option to the saa7134.ko module. Best regards Hartmut ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] LifeView FlyDVB-T Hybrid PCI
Hi, Frédéric Massot wrote: Hi, The kernel 2.6.18 supports the cards LifeView FlyDVB-T PCI, FlyDVB-T DUO PCI, FlyDVB-T Duo Cardbus, FlyDVB-T Hybrid Cardbus. But, will the card FlyDVB-T Hybrid PCI be supported soon? Regards. We need more information to give a reply. There is a big number of slightly different cards by this vendor and they are sold aunder many different names. It is easily possible that your card already works if you force the card drive. So - which chips are on the card? - assuming it is saa7133 / saa7131 based (the chip close to the PCI connector): please load the driver with: modprobe saa7134 (good idea to add card=94) modprobe saa7134-dvb and send us the kernel log (dmesg) this produces. You should also test whether soething works. Good luck Hartmut ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] MPE pointer field too big
On Tue, Oct 17, 2006, Harnois Anne-Sophie wrote: Some of the MPEG-TS packets I receive contain a pointer field bigger than 184 (continuity counter is correct). How to explain that? Shouldn't Pointer field be inside 0 and 184? Any comments? Are you sure PUSI is set in those packets? If not, no pointer field is present. Otherwise it is a bug in the TS generator, it must be 0 = pointer = 183. HTH, Johannes ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] USB card for DVB-S/T
Does anybody know whether it exists a USB card to receive DVB from Stellite and Terrestrial at the same time. I don't really care about analogue TV. I've seen a couple of PCI of Hauppauge, FlyDVB and maybe others, but no USB. Any idea? Thanks ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] MPE pointer field too big
Could you please provide a binary stream (@100 packets), so I could have a look on this with dvbsnoop? I'm interested in the dvbsnoop output, if packets are damaged. Johannes Stezenbach schrieb: On Tue, Oct 17, 2006, Harnois Anne-Sophie wrote: Some of the MPEG-TS packets I receive contain a pointer field bigger than 184 (continuity counter is correct). How to explain that? Shouldn't Pointer field be inside 0 and 184? Any comments? Are you sure PUSI is set in those packets? If not, no pointer field is present. Otherwise it is a bug in the TS generator, it must be 0 = pointer = 183. HTH, Johannes ___ 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] MPE pointer field too big
Johannes Stezenbach wrote: On Tue, Oct 17, 2006, Harnois Anne-Sophie wrote: Some of the MPEG-TS packets I receive contain a pointer field bigger than 184 (continuity counter is correct). How to explain that? Shouldn't Pointer field be inside 0 and 184? Any comments? Are you sure PUSI is set in those packets? If not, no pointer field is present. Otherwise it is a bug in the TS generator, it must be 0 = pointer = 183. Also, make sure the transport error indicator is not set and remember to compensate for field adaption. Steve ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] kworld DVB-T 220RF - remote control
Am Dienstag, den 17.10.2006, 12:50 -0700 schrieb Henry Wong:
hermann pitton wrote:
Mike likely will need the signed-off-by Henry Wong, CCed.
Hi,
Sorry, I'm not really familiar with how the project is managed. What
does this mean?
(If you have time, I'd like to know how the development model works :)
If it means that I should test the final patch and somehow approve it,
unfortunately I no longer have my MSI TV tuner card =)
I noticed there were some comments about repeating keys. I don't
believe this is possible, at least with the MSI [EMAIL PROTECTED] Plus remote.
The remote control really only sends a signal when a key is initially
depressed. It does not send a signal when a key is released, and doesn't
do anything regardless of whether the key is held down or not.
Thanks!
Hello Henry,
thanks for your reply!
I realized after people started working with your code, we forgot to ask
you for your sign-off on your initial patch, solely our mistake.
Here is a link to it on a mail archive, which I forgot to add in my
previous mail.
http://marc.theaimsgroup.com/?l=linux-videom=113435030232464w=2
The development model is detailed on the v4l-wiki. For the case of the
sign-off needed especially here.
http://linuxtv.org/v4lwiki/index.php/SubmittingPatches
Should be enough if you reply with your
Signed-off-by: your name email
Is also already in saa7134-input.c in your comment above the keycodes.
Or send it as a followup to your original mail from Dec. 2005.
Then people can start to review and work with it.
Thanks again for your contribution!
For reference your original patch is attached.
Hope the mailer is nice to it. Usually it is.
Thanks,
Hermann
Index: linux/drivers/media/video/ir-kbd-i2c.c
===
RCS file: /cvs/video4linux/v4l-dvb/linux/drivers/media/video/ir-kbd-i2c.c,v
retrieving revision 1.30
diff -u -r1.30 ir-kbd-i2c.c
--- linux/drivers/media/video/ir-kbd-i2c.c 8 Dec 2005 21:02:56 - 1.30
+++ linux/drivers/media/video/ir-kbd-i2c.c 12 Dec 2005 01:03:52 -
@@ -95,6 +95,8 @@
#define dprintk(level, fmt, arg...) if (debug = level) \
printk(KERN_DEBUG DEVNAME : fmt , ## arg)
+static int polling_interval = 100; /* ms */
+
/* --- */
static int get_key_haup(struct IR_i2c *ir, u32 *ir_key, u32 *ir_raw)
@@ -269,7 +271,7 @@
{
struct IR_i2c *ir = data;
ir_key_poll(ir);
- mod_timer(ir-timer, jiffies+HZ/10);
+ mod_timer(ir-timer, jiffies + polling_interval*HZ/1000);
}
/* --- */
@@ -340,6 +342,9 @@
ir_codes= ir_codes_rc5_tv;
break;
case 0x30:
+ if (adap-id == I2C_HW_SAA7134) /* Handled by saa7134-input */
+ polling_interval = 50; /* ms */
+
name= KNC One;
ir-get_key = get_key_knc1;
ir_type = IR_TYPE_OTHER;
@@ -431,7 +436,7 @@
*/
static const int probe_bttv[] = { 0x1a, 0x18, 0x4b, 0x64, 0x30, -1};
- static const int probe_saa7134[] = { 0x7a, 0x47, -1 };
+ static const int probe_saa7134[] = { 0x7a, 0x47, 0x30, -1 };
static const int probe_em28XX[] = { 0x30, 0x47, -1 };
const int *probe = NULL;
struct i2c_client c;
@@ -456,7 +461,36 @@
c.adapter = adap;
for (i = 0; -1 != probe[i]; i++) {
c.addr = probe[i];
- rc = i2c_master_recv(c,buf,0);
+
+ /* Special case for MSI [EMAIL PROTECTED] Plus remote */
+ if (c.adapter-id == I2C_HW_SAA7134 probe[i] == 0x30)
+ {
+ struct i2c_client c2;
+
+ memset (c2, 0, sizeof(c2));
+ c2.adapter = c.adapter;
+
+ /* MSI [EMAIL PROTECTED] Plus' controller doesn't seem to
+ respond to probes unless we read something from an
+ existing device. Weird... */
+
+ /* Find a device that responds. If none found, oh well. */
+ for (c2.addr=127; c2.addr = 0; c2.addr--)
+ {
+if (0 == i2c_master_recv(c2,buf,0))
+ break;
+ }
+
+ /* Now do the probe. The controller does not respond
+ to 0-byte reads, so we use a 1-byte read instead. */
+ rc = i2c_master_recv(c,buf,1);
+ rc--;
+ }
+ else
+ {
+ rc = i2c_master_recv(c,buf,0);
+ }
+
dprintk(1,probe 0x%02x @ %s: %s\n,
probe[i], adap-name,
(0 == rc) ? yes : no);
Index: linux/drivers/media/video/saa7134/saa7134-cards.c
===
RCS file: /cvs/video4linux/v4l-dvb/linux/drivers/media/video/saa7134/saa7134-cards.c,v
retrieving revision 1.117
diff -u -r1.117 saa7134-cards.c
--- linux/drivers/media/video/saa7134/saa7134-cards.c 8 Dec 2005 02:46:36 - 1.117
+++ linux/drivers/media/video/saa7134/saa7134-cards.c 12 Dec 2005 01:03:53 -
@@ -2531,8 +2531,8 @@
.amux = LINE1,
}},
},
- [SAA7134_BOARD_MSI_TVATANYWHERE_PLUS] = {
- .name = MSI [EMAIL PROTECTED] plus,
+ [SAA7134_BOARD_MSI_TVANYWHERE_PLUS] = {
+ .name = MSI [EMAIL PROTECTED] Plus,
.audio_clock= 0x00187de7,
.tuner_type =
Re: [linux-dvb] TTUSB DEC-2000T Driver: tuning problems
Mario Rossi wrote:
An application can simply try DMX_PES_OTHER first and if
-ENOTSUPPORTED is returned,
as it would be the case here, it can fallback to DMX_PES_{AUDIO,VIDEO}.
Mythtv does it this way afaik.
it seems doable. I'll have a try modifying dvbstream (and mplayer
which is the same) and try to see what happens.
cheers
please, try this patch for dvbstream and report
Index: dvbstream.c
===
RCS file: /cvsroot/dvbtools/dvbstream/dvbstream.c,v
retrieving revision 1.32
diff -u -r1.32 dvbstream.c
--- dvbstream.c 5 Oct 2006 20:25:16 - 1.32
+++ dvbstream.c 17 Oct 2006 21:57:54 -
@@ -141,9 +141,17 @@
pesFilterParams.pes_type = pestype;
pesFilterParams.flags = DMX_IMMEDIATE_START;
- if (ioctl(fd, DMX_SET_PES_FILTER, pesFilterParams) 0) {
-fprintf(stderr,Failed setting filter for pid %i: ,pid);
-perror(DMX SET PES FILTER);
+ if ((ioctl(fd, DMX_SET_PES_FILTER, pesFilterParams)) 0) {
+if(pesFilterParams.pes_type==DMX_PES_OTHER) {
+ pesFilterParams.pes_type = DMX_PES_VIDEO;
+ if ((ioctl(fd, DMX_SET_PES_FILTER, pesFilterParams)) 0) {
+pesFilterParams.pes_type = DMX_PES_AUDIO;
+if((ioctl(fd, DMX_SET_PES_FILTER, pesFilterParams)) 0) {
+ fprintf(stderr,Failed setting filter for pid %i: ,pid);
+ perror(DMX SET PES FILTER);
+ }
+ }
+}
}
}
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] TTUSB DEC-2000T Driver: tuning problems
Am Dienstag, 17. Oktober 2006 18:18 schrieb Peter Beutner:
An application can simply try DMX_PES_OTHER first and if -ENOTSUPPORTED is
returned, as it would be the case here, it can fallback to
DMX_PES_{AUDIO,VIDEO}. Mythtv does it this way afaik.
With the new mythtv (0.20 or svn head) i've no luck tuning with the dec-2000t.
It just runs in a timeout.
Can someone give me some hints to get this working ?
Greets
Jan-Simon
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Close tzap and cannot lock frequency anymore?
Am Dienstag, den 17.10.2006, 02:16 +0200 schrieb hermann pitton: Am Montag, den 16.10.2006, 22:14 +0400 schrieb Manu Abraham: Chun Chung Lo wrote: Hi all, I wonder during I am capturing TS stream by using a DVB-T card (Compro Videomate T300) in a Linux PC (2.6.16-18), I followed the instructions shown in linuxtv-dvb-apps and run tzap and capture TS. Because I think all the parameters are written into the hardware of the tuner, and the tzap also shown FE_HAS_LOCKED, so I think I have no need to keep polling the tuner and I switched off tzap. But when I switched off tzap, I found that my TS capturing is stoped! (I found that some TS data is missing in the captured TS file.) But when I keep tzap running, no such problem occur. When you stop *zap, the default behavior of dvb-core is to switch off the frontend after a predefined period of time, to save power. So what you are seeing is the default behavior. If you want to turn OFF this behavior, you can use the module parameter dvb_shutdown_timeout=0 to dvb_core, such that this feature is disabled. Manu Hi Manu, it seems there has been a reason, when Johannes asked Gerd on 2.6.12 to take care for his own stuff ... That above won't work, AFAIK. Sorry for insufficient testing. Just timeout=0 didn't the expected. Setting a time interval prevents also the tuner_sleep and switching back to analog mode. Thanks, Hermann ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Close tzap and cannot lock frequency anymore?
hermann pitton wrote: Am Dienstag, den 17.10.2006, 02:16 +0200 schrieb hermann pitton: Am Montag, den 16.10.2006, 22:14 +0400 schrieb Manu Abraham: Chun Chung Lo wrote: Hi all, I wonder during I am capturing TS stream by using a DVB-T card (Compro Videomate T300) in a Linux PC (2.6.16-18), I followed the instructions shown in linuxtv-dvb-apps and run tzap and capture TS. Because I think all the parameters are written into the hardware of the tuner, and the tzap also shown FE_HAS_LOCKED, so I think I have no need to keep polling the tuner and I switched off tzap. But when I switched off tzap, I found that my TS capturing is stoped! (I found that some TS data is missing in the captured TS file.) But when I keep tzap running, no such problem occur. When you stop *zap, the default behavior of dvb-core is to switch off the frontend after a predefined period of time, to save power. So what you are seeing is the default behavior. If you want to turn OFF this behavior, you can use the module parameter dvb_shutdown_timeout=0 to dvb_core, such that this feature is disabled. Manu Hi Manu, it seems there has been a reason, when Johannes asked Gerd on 2.6.12 to take care for his own stuff ... That above won't work, AFAIK. Sorry for insufficient testing. Just timeout=0 didn't the expected. Setting a time interval prevents also the tuner_sleep and switching back to analog mode. modinfo dvb_core |grep timeout parm: dvb_shutdown_timeout:wait shutdown_timeout seconds after close() before suspending hardware parmtype: dvb_shutdown_timeout:int Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Close tzap and cannot lock frequency anymore?
Am Mittwoch, den 18.10.2006, 04:01 +0400 schrieb Manu Abraham: hermann pitton wrote: Am Dienstag, den 17.10.2006, 02:16 +0200 schrieb hermann pitton: Am Montag, den 16.10.2006, 22:14 +0400 schrieb Manu Abraham: Chun Chung Lo wrote: Hi all, I wonder during I am capturing TS stream by using a DVB-T card (Compro Videomate T300) in a Linux PC (2.6.16-18), I followed the instructions shown in linuxtv-dvb-apps and run tzap and capture TS. Because I think all the parameters are written into the hardware of the tuner, and the tzap also shown FE_HAS_LOCKED, so I think I have no need to keep polling the tuner and I switched off tzap. But when I switched off tzap, I found that my TS capturing is stoped! (I found that some TS data is missing in the captured TS file.) But when I keep tzap running, no such problem occur. When you stop *zap, the default behavior of dvb-core is to switch off the frontend after a predefined period of time, to save power. So what you are seeing is the default behavior. If you want to turn OFF this behavior, you can use the module parameter dvb_shutdown_timeout=0 to dvb_core, such that this feature is disabled. Manu Hi Manu, it seems there has been a reason, when Johannes asked Gerd on 2.6.12 to take care for his own stuff ... That above won't work, AFAIK. Sorry for insufficient testing. Just timeout=0 didn't the expected. Setting a time interval prevents also the tuner_sleep and switching back to analog mode. modinfo dvb_core |grep timeout parm: dvb_shutdown_timeout:wait shutdown_timeout seconds after close() before suspending hardware parmtype: dvb_shutdown_timeout:int Manu Thanks for the friendly reply ! Hermann ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Close tzap and cannot lock frequency anymore?
Am Mittwoch, den 18.10.2006, 02:39 +0200 schrieb hermann pitton: Am Mittwoch, den 18.10.2006, 04:01 +0400 schrieb Manu Abraham: hermann pitton wrote: Am Dienstag, den 17.10.2006, 02:16 +0200 schrieb hermann pitton: Am Montag, den 16.10.2006, 22:14 +0400 schrieb Manu Abraham: Chun Chung Lo wrote: Hi all, I wonder during I am capturing TS stream by using a DVB-T card (Compro Videomate T300) in a Linux PC (2.6.16-18), I followed the instructions shown in linuxtv-dvb-apps and run tzap and capture TS. Because I think all the parameters are written into the hardware of the tuner, and the tzap also shown FE_HAS_LOCKED, so I think I have no need to keep polling the tuner and I switched off tzap. But when I switched off tzap, I found that my TS capturing is stoped! (I found that some TS data is missing in the captured TS file.) But when I keep tzap running, no such problem occur. When you stop *zap, the default behavior of dvb-core is to switch off the frontend after a predefined period of time, to save power. So what you are seeing is the default behavior. If you want to turn OFF this behavior, you can use the module parameter dvb_shutdown_timeout=0 to dvb_core, such that this feature is disabled. Manu Hi Manu, it seems there has been a reason, when Johannes asked Gerd on 2.6.12 to take care for his own stuff ... That above won't work, AFAIK. Sorry for insufficient testing. Just timeout=0 didn't the expected. Setting a time interval prevents also the tuner_sleep and switching back to analog mode. modinfo dvb_core |grep timeout parm: dvb_shutdown_timeout:wait shutdown_timeout seconds after close() before suspending hardware parmtype: dvb_shutdown_timeout:int Manu Thanks for the friendly reply ! To make it short. The Pinnacle 300i would be broken until now, if not Hartmut finally took a step on the digital. And without excellent and patient users! Both, for analog and digital. Hermann ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] HD3000 (cx88) and GA-965P-DS3 Problem.
This is definitely looking like a hardware failure on this board. I swaped the old motherboard back in, and the device didn't show up. Is there any way to restore the EEPROM, or should I see if I can RMA this? I still have not been able to find the eeprom file to actually pull the 256 bytes of configuration data. Anyone have any idea where I should look? On 10/16/06, Joshua Prismon [EMAIL PROTECTED] wrote: It worked on a different motherboard (an ASUS A8N-SLI deluxe with a socket 939 AMD64). I replaced the motherboard with a Intel 965P, and it stopped working. It does not work with a vanilla kernel. I also noted that the device went away with this motherboard. The 965P motherboards are fairly new, and this may be a larger linux problem. Right now I am playing around with PCI addressing modes to see if there is a problem in the ACPI layer. On 10/16/06, Steven Toth [EMAIL PROTECTED] wrote: Joshua Prismon wrote: I am still getting the hang of this code, so it's very very possible that I am missing something basic here. I don't think the problem is in the request_aquire function. In fact that doesn't even appear to be every called. The DVB driver registered correctly with the cx88-mpeg driver ( cx8802_register_driver). That driver registers with the pci_driver. That PCI probe doesn't appear to be actually called. When cx8802_register_driver starts looping through devices (after the dvb driver is registered), it doesn't find any devices at all. The devlist should be (if I read the code correctly) populated by the cx8802_probe function. As a quick test, I added the following lines to the pci_register_driver to see what the system actually sees in the PCI tables: /* .vendor = 0x14f1, .device = 0x8802, */ dev = pci_find_device(0x14f1, 0x8802, dev); cut 05:00.0 0400: 14f1:8800 (rev 05) Subsystem: 7063:3000 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 32 (5000ns min, 13750ns max), Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 21 Region 0: Memory at f600 (32-bit, non-prefetchable) [size=16M] Capabilities: [44] Vital Product Data Capabilities: [4c] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 05:00.4 0480: 14f1:8804 (rev 05) Subsystem: 7063:3000 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium I don't see the mpeg PCI function enabled. In other words I don't see the 14f1:8802 device. Why is this missing? I expected to see an entire entry for this. The cx8802.ko (cx88-mpeg.c) driver registers against 14f1:8802 and so if that isn't registered then DVB is never going to work, because the kernel will never probe it. Are you completely sure the DVB device works under other kernels? Can you tell me which vanilla kernel from www.kernel.org this DVB product is working correctly with? Steve ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] HD3000 (cx88) and GA-965P-DS3 Problem.
Eeprom works now. Here is the memory: 80 08 07 0d 0a 02 40 00 04 50 60 00 82 08 00 01 |[EMAIL PROTECTED]| 0010 0e 04 08 01 02 20 00 60 70 75 75 3c 28 3c 28 40 |. .`puu((@| 0020 60 60 40 40 00 00 00 00 00 37 46 28 28 55 00 00 |``@@.7F((U..| 0030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 88 || 0040 7f 7f 9e 00 00 00 00 00 01 56 53 35 31 32 4d 42 |.VS512MB| 0050 34 30 30 20 20 20 20 20 20 20 20 00 00 00 00 00 |400.| 0060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 || * 0100 I grabbed it in octal as well: 000 004200 006407 001012 000100 050004 000140 004202 000400 010 002016 000410 020002 06 072560 036165 036050 040050 020 060140 040100 00 00 033400 024106 052450 00 030 00 00 00 00 00 00 00 104000 040 077577 000236 00 00 053001 032523 031061 041115 050 030064 020060 020040 020040 020040 40 00 00 060 00 00 00 00 00 00 00 00 * 100 On 10/17/06, Joshua Prismon [EMAIL PROTECTED] wrote: This is definitely looking like a hardware failure on this board. I swaped the old motherboard back in, and the device didn't show up. Is there any way to restore the EEPROM, or should I see if I can RMA this? I still have not been able to find the eeprom file to actually pull the 256 bytes of configuration data. Anyone have any idea where I should look? On 10/16/06, Joshua Prismon [EMAIL PROTECTED] wrote: It worked on a different motherboard (an ASUS A8N-SLI deluxe with a socket 939 AMD64). I replaced the motherboard with a Intel 965P, and it stopped working. It does not work with a vanilla kernel. I also noted that the device went away with this motherboard. The 965P motherboards are fairly new, and this may be a larger linux problem. Right now I am playing around with PCI addressing modes to see if there is a problem in the ACPI layer. On 10/16/06, Steven Toth [EMAIL PROTECTED] wrote: Joshua Prismon wrote: I am still getting the hang of this code, so it's very very possible that I am missing something basic here. I don't think the problem is in the request_aquire function. In fact that doesn't even appear to be every called. The DVB driver registered correctly with the cx88-mpeg driver ( cx8802_register_driver). That driver registers with the pci_driver. That PCI probe doesn't appear to be actually called. When cx8802_register_driver starts looping through devices (after the dvb driver is registered), it doesn't find any devices at all. The devlist should be (if I read the code correctly) populated by the cx8802_probe function. As a quick test, I added the following lines to the pci_register_driver to see what the system actually sees in the PCI tables: /* .vendor = 0x14f1, .device = 0x8802, */ dev = pci_find_device(0x14f1, 0x8802, dev); cut 05:00.0 0400: 14f1:8800 (rev 05) Subsystem: 7063:3000 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 32 (5000ns min, 13750ns max), Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 21 Region 0: Memory at f600 (32-bit, non-prefetchable) [size=16M] Capabilities: [44] Vital Product Data Capabilities: [4c] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 05:00.4 0480: 14f1:8804 (rev 05) Subsystem: 7063:3000 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium I don't see the mpeg PCI function enabled. In other words I don't see the 14f1:8802 device. Why is this missing? I expected to see an entire entry for this. The cx8802.ko (cx88-mpeg.c) driver registers against 14f1:8802 and so if that isn't registered then DVB is never going to work, because the kernel will never probe it. Are you completely sure the DVB device works under other kernels? Can you tell me which vanilla kernel from www.kernel.org this DVB product is working correctly with? Steve ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] HD3000 (cx88) and GA-965P-DS3 Problem.
Joshua Prismon wrote: Eeprom works now. Here is the memory: 80 08 07 0d 0a 02 40 00 04 50 60 00 82 08 00 01 |[EMAIL PROTECTED]| 0010 0e 04 08 01 02 20 00 60 70 75 75 3c 28 3c 28 40 |. .`puu((@| 0020 60 60 40 40 00 00 00 00 00 37 46 28 28 55 00 00 |``@@.7F((U..| 0030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 88 || 0040 7f 7f 9e 00 00 00 00 00 01 56 53 35 31 32 4d 42 |.VS512MB| 0050 34 30 30 20 20 20 20 20 20 20 20 00 00 00 00 00 |400.| 0060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 || * 0100 This isn't the right eeprom. You should expect to see 7060:3000 somewhere in the first 8 bytes. Eg. 60 70 00 30 Try modprobing cx8800 with i2c_scan = 1 See if the eeprom is found at address 0xa0 or 0x50; If it's not found, then that would explain everything. Steve ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
