Re: [linux-dvb] Warning, there seems to be a new Nova TD stick out!!
On Thu, 4 Oct 2007, Henrik Beckman wrote: 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. The current driver even in latest hg has no VHF support meaning it does not support frequencies below 470 MHz. I have a patch pending - if I will find the time, I will commit it later that day. 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] I-Frame Detection
Thank you guys. ISO 13818-2 indeed holds the solution. Section 6.2 describes the Video bitstream syntax. Just need to find the picture header(described in 6.2.3) wich contains the picture coding type. Nico Sabbi wrote: 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 mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] RE : Hauppauge Nova-T Stick (and TD)
Hi Thierry Thanks for the advice - I got there (well at least scan works now). There was one extra problem not documented on either... http://linuxtv.org/wiki/index.php/How_to_install_DVB_device_drivers ...or... e.g. http://www.mythtv.org/wiki/index.php/Hauppauge_WinTV_Nova-T_500_PCI http://www.mythtv.org/wiki/index.php/Hauppauge_WinTV_Nova-T_500_PCI The make didn't work (this is for an Ubuntu 7.04 desktop, all basic updates and a few things extra, but nearly new). Problem was that /lib/modules/2.6.20-16-generic/source didn't exist. So making that ( i.e. source in that directory) a symlink to /usr/src/linux-headers-2.6.20-16-generic/ was enough and make went about its jolly business. (Also installed kernel-package in the process but I'm not sure if it effected anything). I'm guessing this is an Ubuntu specific issue? Any idea when this build and firmware are going to come in the kernel ready-to-go? I tested it out with scan, mplayer etc and all went well. MythTV is a bit funky (couldn¹t get it to just take in the channel.conf file and it gets worse signal strength and BER than bash-shell bizarre :) Cheers, Rod. On 10/3/07 3:04 PM, ext Thierry Lelegard [EMAIL PROTECTED] wrote: 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-dib07 00-1.10.fw http://www.wi-bw.tfh-wildau.de/~pboettch/home/linux-dvb-firmware/dvb-usb-dib0 700-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 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 mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Need info about AAC in DVB
Hi, I'm trying to add support to mplayer and ffmpeg for LATM AAC as carried in DVB (LATM is a framing format very different from the usual ADTS transport), but I don't understand how LATM frames are carried: the DVB SI specs (1.7.1) don't say if LATM should be carried or not in one of the 3 LOAS framers, and if not if it has to be in the error_protected format or not. Looking at the dump of the audio stream I can't find any clue. Can anyone help or shed some light, please? Thanks, Nico ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] scanning for symbol rate [re: zig-zag thread]
Hello, Recently I've been writing a program that tries to guess the symbol rate of a carrier, assuming it is QPSK, and that the frequency is right. It's pretty basic right now, it sets the fe parameters, waits a specific period of time, drains the events, then attempts to determine whether it has a lock or not. so I originally told it to wait 5 seconds in the timeout, and in another window I ran dvbsnoop -s feinfo to determine what was goign on. To my horror, I noticed the srate was varying. I was incrementing srate by 1, and the driver was helping me. This makes the scan take a _LONG_ time, because it is scanning the same symbol rate multiple times. so if I assume the FEC is auto, and that spectral inversion is auto, what is the best method to use to hold the frequency constant and vary the symbol rate? Even if this method gets you off by one or two, you can figure it out manually, but trying to run dvbtune in a loop or writing a special program seems a bit difficult. The program would be fine, but it takes several hours to find the symbol rate depending on how far off your guess is. It's a stv0299. how long does it take to lock a carrier, and can somebody describe what it does to 'help' you? Maybe in that I can actually let it help me in a useful way. _J ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Need info about AAC in DVB
On Fri, 2007-10-05 at 12:38 +0200, Nico Sabbi wrote: ... Can anyone help or shed some light, please? Not sure if this helps anything, but this post discussed various aspects of supporting DVB-T in Norway: http://www.dvbviewer.info/forum/index.php?showtopic=17644view=findpostp=140732 The LATM formatted MPEG-4 HE AAC or HE AAC v2 elementary stream data shall be encapsulated in the LOAS transmission format according to ISO/IEC 14496-3 [17]. The AudioSyncStream() version shall be used. -- Per Thomas ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] improving the quality of DVB signal - PS
MikeW mw_phil at yahoo.co.uk writes: ngocminh_bk_nd at yahoo.com writes: Hi all I have 2 cards DVB-T DVB-S of TWINHAN but i can't use the kaffeine to watch TV channels because the level of signal approxiate 33%. when i use modules #modprobe : bttv bt878 dst dvb_core dvb-bt8xx the commands # scan asiat3 channels.conf #szap -c channels.conf bloomberg -r # cat dev/dvb/adapter0/dvr0 /home/ron/file.ts the signal of file.ts is very bad, not continuous. But when i try these card on Window the signal is good, about 88% How can I improve the signal? please help me. Thank you! Are you sure that the two numbers quoted are calculated in the same way ? Are they peak or average or windowed-average ? Or even refer to the same signal quality indicator ? Assuming you are comparing like with like, since some frontends with silicon tuners have adaptive/tracking filtering, it's possible that the Linux driver does not use the manufacturer's best algorithm for tuning. Regards, MikeW The usual signal quality 'number' for DVB is BER (bit error rate), hence you should check this figure for both your Win and Lin setups. Lower BER = better signal, it is NOT a percentage. But there might still be a difference in averaging calculations. MikeW ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] how to exactly tune a carrier
Sorry for the duplicate, I had some smtp problems and thought the first message was gone instead it was hiding. _J Jeremy Hall[EMAIL PROTECTED] 10/4/2007 9:50:41 AM Hello, I am trying to write an application that attempts to find the symbol rate of a QPSK carrier by making an intelligent guess as to the likely symbol rate, followed by a brute-force method of starting at the suggested value and incrementing or decrementing from that value by 1000, gradually making the distance from the starting point larger and larger in both directions. the problem I have set inversion to auto, FEC to auto, and the frequency to the correct value for the carrier. I want the driver to scan the values I provide within a 1khz tolerence for all FEC choices and both spectral inversions. I don't know how long that takes but I'd like it for obvious reasons to go as quickly as possible. Since I don't know how long this takes, I decided to sleep for a few seconds then read status to determine if FE_HAS_LOCK so I can stop. To my horror, I discovered, by running dvbsnoop -s feinfo in another window, that not only were my symbol rates different than my suggested values, but the frequency was different as well. In fact, I noticed that if you wait long enough, you can lock onto a neighbouring signal that isn't even the one you wanted, and the frequency reported is something in the middle but closer to what you want, yet clearly it is the other signal, for example, two DSNG carriers are located at 12116 and 12121 respectively, with a symbol rate of 3979. At first I thought my LO was wrong, but try to lock the first one, wait about 8 seconds and then the second one magically locks even though I didn't want that one. I think it's reasonable to say your frequency could be off as much as 1khz in either direction, or at least a module parameter should be enstantiated so you can tell the driver you were to cheap to buy a decent LNB. So how do I get what I want? I think the driver probably could do what I want in under a second as long as te symbol rate is not super low like 1000. I am using the stv0299 frontend. _J ___ 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] New card for http://www.bttv-gallery.de/
On 10/5/07, David Campbell [EMAIL PROTECTED] wrote: The whole XP driver kit is at http://www.aaa.net.au/campbell/driver.zip but it may support other devices so unsure what bits are actually relevant: -rw-rw-r-- 1 dcampbel dcampbel 4697 2005-08-06 15:27 EMAUDIO.INF -rw-rw-r-- 1 dcampbel dcampbel 20736 2005-07-08 17:43 emAudio.sys -rw-rw-r-- 1 dcampbel dcampbel 48335 2005-11-14 20:29 EMBDA.INF -rw-rw-r-- 1 dcampbel dcampbel 209664 2005-11-14 20:30 emBDA.sys -rw-rw-r-- 1 dcampbel dcampbel 17152 2005-11-14 20:29 emOEM.sys (strings indicates it to be an MT2060 driver) -rw-rw-r-- 1 dcampbel dcampbel 32768 2005-11-14 20:29 emPRP.ax Interesting. The driver finds it but doesn't seem to recognise one of the i2c devices:em28xx #0: found i2c device @ 0x16 [???] That's the ZL10353. I think it's the analog code that's not detecting it; it's the digital part of the driver that handles this i2c device, and it doesn't auto-detect. Actually this unrecognised device shows itself at different i2c addresses different times you plug it in. See below for what I've seen. em28xx #0: found i2c device @ 0x26 [???] em28xx #0: found i2c device @ 0xa0 [eeprom] em28xx #0: found i2c device @ 0xc2 [tuner (analog)] em28xx #0: found i2c device @ 0x16 [???] em28xx #0: found i2c device @ 0xa0 [eeprom] em28xx #0: found i2c device @ 0xc2 [tuner (analog)] em28xx #0: found i2c device @ 0x32 [???] em28xx #0: found i2c device @ 0xa0 [eeprom] em28xx #0: found i2c device @ 0xc2 [tuner (analog)] I'm guessing it's probably bogus, then. I find that if I do the following, the device gets registered, and it is saying something about an LG chip but I'm not familiar enough with the depths of the driver to know whether this output below is actually the driver detecting the tuner chipset, or something that the driver has been forced to believe. Can you comment? modprobe em28xx card=8 i2c_scan=1 device_mode=1 Table at 0x04, strings=0x226a, 0x, 0x tuner 1-0061: chip found @ 0xc2 (em28xx #0) attach inform (default): detected I2C address c2 tuner 0x61: Configuration acknowledged tuner 1-0061: type set to 37 (LG PAL (newer TAPC series)) em28xx #0: found i2c device @ 0x26 [???] em28xx #0: found i2c device @ 0xa0 [eeprom] em28xx #0: found i2c device @ 0xc2 [tuner (analog)] em28xx #0: V4L2 device registered as /dev/video0 em28xx #0: Found Pinnacle PCTV USB 2 You're basically forcing the driver to assume that your tuner is that particular one. I'm guessing the LG tuner it's set to is a can tuner, which is far too big to be in a USB device. I'd suggest that Terratec Cinergy T XS (MT2060) or Pinnacle PCTV DVB-T would be a better choice. but subsequently loading the em2880-dvb device doesn't work I don't know whether I'm doing the right thing here by attempting to load this: em2880-dvb.c: DVB Init em2880-dvb.c: unsupported device em2880-dvb.c: failed initializing zl10353 DVB-T demodulator em2880-dvb.c: retrying with mt352 DVB-T demodulator FIXME:em28xx_i2c_send_bytes(1e): write failed: === 7f mt352_read_register: readreg error (reg=127, ret==-19) em2880-dvb.c: no luck with mt352 demodulator, not attaching em2880-dvb em2880-dvb.c: DVB-T demodulator not reachable, did you try modprobe em28xx device_mode=1 Em28xx: Initialized (Em2880 DVB Extension) extension That's because you're telling the driver that your device is one that doesn't support DVB-T; I'm not sure why it even tries to load. (The fact that it doesn't do the right GPIO-twiddling doesn't help either.) Aidan Markus Rechberger wrote: This device requires a gpio setup for enabling the zl10353 on the i2c bus. Does your driver already do that for some devices? How difficult is it going to be to convince it for this one? It's not that hard (in theory); it just requires booting into Windows and running a USB sniffer to find out what the Windows driver sends. It's just that it's different for different devices. I'm sure Markus will tell you more. Aidan ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Warning, there seems to be a new Nova TD stick out!!
Eg using '/dev/dvb/adapter2/frontend0' and '/dev/dvb/adapter2/demux0' initial transponder 72200 0 2 9 3 1 2 0 initial transponder 57800 0 2 9 3 1 2 0 initial transponder 73000 0 2 9 3 1 2 0 initial transponder 76200 0 2 9 3 1 2 0 tune to: 72200:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE WARNING: tuning failed!!! tune to: 72200:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE (tuning failed) WARNING: tuning failed!!! tune to: 57800:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE WARNING: tuning failed!!! tune to: 57800:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE (tuning failed) WARNING: tuning failed!!! tune to: 73000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE WARNING: tuning failed!!! tune to: 73000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE (tuning failed) WARNING: tuning failed!!! tune to: 76200:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE WARNING: tuning failed!!! tune to: 76200:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE (tuning failed) WARNING: tuning failed!!! ERROR: initial tuning failed dumping lists (0 services) Done. On 10/5/07, Henrik Beckman [EMAIL PROTECTED] wrote: No DVB-T should be below 474MHz in Sweden, it´s more like there doesn´t exist any signal on the stick, either reception in linux is extremly bad compared to windows or something has changed on the inside of the Nova-TD stick, or the stick is quirky. w_scan doesn´t find anything, tzap with the nova-t 500 channels.confdoesn´t find anything. I´ll try with kaffeine and create and a brand new channesl.conf consisting of only auto values and see if I can find and recive something. /Henrik On 10/5/07, Patrick Boettcher [EMAIL PROTECTED] wrote: On Thu, 4 Oct 2007, Henrik Beckman wrote: 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. The current driver even in latest hg has no VHF support meaning it does not support frequencies below 470 MHz. I have a patch pending - if I will find the time, I will commit it later that day. Patrick. -- Mail: [EMAIL PROTECTED] WWW: http://www.wi-bw.tfh-wildau.de/~pboettch/http://www.wi-bw.tfh-wildau.de/%7Epboettch/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Warning, there seems to be a new Nova TD stick out!!
I´m an idiot, it never occured to me that the stick needed dual antennas in dual tuner mode, the when using the second tuner on the card I get reception /Henrik On 10/5/07, Patrick Boettcher [EMAIL PROTECTED] wrote: On Thu, 4 Oct 2007, Henrik Beckman wrote: 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. The current driver even in latest hg has no VHF support meaning it does not support frequencies below 470 MHz. I have a patch pending - if I will find the time, I will commit it later that day. 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] New card for http://www.bttv-gallery.de/
On 10/5/07, Aidan Thornton [EMAIL PROTECTED] wrote: On 10/5/07, David Campbell [EMAIL PROTECTED] wrote: The whole XP driver kit is at http://www.aaa.net.au/campbell/driver.zip but it may support other devices so unsure what bits are actually relevant: -rw-rw-r-- 1 dcampbel dcampbel 4697 2005-08-06 15:27 EMAUDIO.INF -rw-rw-r-- 1 dcampbel dcampbel 20736 2005-07-08 17:43 emAudio.sys -rw-rw-r-- 1 dcampbel dcampbel 48335 2005-11-14 20:29 EMBDA.INF -rw-rw-r-- 1 dcampbel dcampbel 209664 2005-11-14 20:30 emBDA.sys -rw-rw-r-- 1 dcampbel dcampbel 17152 2005-11-14 20:29 emOEM.sys (strings indicates it to be an MT2060 driver) -rw-rw-r-- 1 dcampbel dcampbel 32768 2005-11-14 20:29 emPRP.ax Interesting. The driver finds it but doesn't seem to recognise one of the i2c devices:em28xx #0: found i2c device @ 0x16 [???] That's the ZL10353. I think it's the analog code that's not detecting it; it's the digital part of the driver that handles this i2c device, and it doesn't auto-detect. Actually this unrecognised device shows itself at different i2c addresses different times you plug it in. See below for what I've seen. em28xx #0: found i2c device @ 0x26 [???] em28xx #0: found i2c device @ 0xa0 [eeprom] em28xx #0: found i2c device @ 0xc2 [tuner (analog)] em28xx #0: found i2c device @ 0x16 [???] em28xx #0: found i2c device @ 0xa0 [eeprom] em28xx #0: found i2c device @ 0xc2 [tuner (analog)] em28xx #0: found i2c device @ 0x32 [???] em28xx #0: found i2c device @ 0xa0 [eeprom] em28xx #0: found i2c device @ 0xc2 [tuner (analog)] I'm guessing it's probably bogus, then. it's not really bogus, toggled gpio values are capable of changing what you can see here. So either by reloading the driver or replugging the devices you can change the output. The dirtiest fallback for devicedetection is to recognize the device by those i2c addresses. If nothing works out the enduser has to fall back to the card module parameter - anyway I try to avoid that the user has to set up any module parameters.. it's just a pain if a user plugs in his device the first time and has to fiddle around with some settings for a device. Any better idea on devicedetection with same usbids is welcome. I find that if I do the following, the device gets registered, and it is saying something about an LG chip but I'm not familiar enough with the depths of the driver to know whether this output below is actually the driver detecting the tuner chipset, or something that the driver has been forced to believe. Can you comment? modprobe em28xx card=8 i2c_scan=1 device_mode=1 Table at 0x04, strings=0x226a, 0x, 0x tuner 1-0061: chip found @ 0xc2 (em28xx #0) attach inform (default): detected I2C address c2 tuner 0x61: Configuration acknowledged tuner 1-0061: type set to 37 (LG PAL (newer TAPC series)) em28xx #0: found i2c device @ 0x26 [???] em28xx #0: found i2c device @ 0xa0 [eeprom] em28xx #0: found i2c device @ 0xc2 [tuner (analog)] em28xx #0: V4L2 device registered as /dev/video0 em28xx #0: Found Pinnacle PCTV USB 2 You're basically forcing the driver to assume that your tuner is that particular one. I'm guessing the LG tuner it's set to is a can tuner, which is far too big to be in a USB device. I'd suggest that Terratec Cinergy T XS (MT2060) or Pinnacle PCTV DVB-T would be a better choice. Yes, I also think so, although as mentioned the GPIO values might differ. but subsequently loading the em2880-dvb device doesn't work I don't know whether I'm doing the right thing here by attempting to load this: em2880-dvb.c: DVB Init em2880-dvb.c: unsupported device em2880-dvb.c: failed initializing zl10353 DVB-T demodulator em2880-dvb.c: retrying with mt352 DVB-T demodulator FIXME:em28xx_i2c_send_bytes(1e): write failed: === 7f mt352_read_register: readreg error (reg=127, ret==-19) em2880-dvb.c: no luck with mt352 demodulator, not attaching em2880-dvb em2880-dvb.c: DVB-T demodulator not reachable, did you try modprobe em28xx device_mode=1 Em28xx: Initialized (Em2880 DVB Extension) extension That's because you're telling the driver that your device is one that doesn't support DVB-T; I'm not sure why it even tries to load. (The fact that it doesn't do the right GPIO-twiddling doesn't help either.) Aidan Markus Rechberger wrote: This device requires a gpio setup for enabling the zl10353 on the i2c bus. Does your driver already do that for some devices? How difficult is it going to be to convince it for this one? It's not that hard (in theory); it just requires booting into Windows and running a USB sniffer to find out what the Windows driver sends. It's just that it's different for different devices. I'm sure Markus will tell you more. There are 2 wiki sites available: http://mcentral.de/wiki/index.php/USBVideo
Re: [linux-dvb] stv0299 demod with new pll ix2476
Hi, I just added the real PLL support for the ix2476, but it still gives me the same problem. The file is in the attchmnt. Thanks in advance. Regards, -- Pedro Aguilar Hi, I have a Sharp F7VZ0194A tuner/demod metal can that contains the stv0299 demod and an ix2476 PLL that I want to make it work in an SH4 based embedded target. Some weeks ago, after an important help from Manu, I realize that there wasn't any driver for the PLL that supported it right away, so I needed to add support for it. I started adding this support modifying the file stv0299.c. I know this is not right place for doing it, but at the moment I wanted to make things easier since I'm quite new to DVB. After some modifications, I tried to make a scan but it fails. This is the output of the scan util: # ./scan -v dvb-s/Hotbird-13.0E scanning /home/dvb/dvb-s/Hotbird-13.0E using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' initial transponder 12539000 H 2750 3 tune to: 12539:h:0:27500 DiSEqC: switch pos 0, 18V, hiband (index 3) tuning status == 0x03 tuning status == 0x03 ... tuning status == 0x03 WARNING: tuning failed!!! tune to: 12539:h:0:27500 (tuning failed) DiSEqC: switch pos 0, 18V, hiband (index 3) tuning status == 0x03 tuning status == 0x03 ... tuning status == 0x03 WARNING: tuning failed!!! ERROR: initial tuning failed dumping lists (0 services) Done. I modprobe the module with debug=1 and the kernel is compiled with printk support, so the output when scanning (with some additional printk that I added) is: dvb_device_open(): Opening device... dvb_frontend_open dvb_generic_open(): Opening generic... dvb_frontend_start dvb_frontend_ioctl dvb_frontend_thread DVB: initialising frontend 0 (ST STV0299 DVB-S)... stv0299: init chip dvb_frontend_ioctl stv0299: stv0299_set_tone() dvb_frontend_ioctl stv0299: stv0299_set_voltage: SEC_VOLTAGE_18 dvb_frontend_ioctl stv0299: stv0299_send_diseqc_msg dvb_frontend_ioctl stv0299: stv0299_send_diseqc_burst dvb_frontend_ioctl stv0299: stv0299_set_tone() dvb_frontend_ioctl stv0299: stv0299_get_tune_settings() dvb_frontend_add_event dvb_frontend_swzigzag_autotune: drift:0 inversion:0 auto_step:0 auto_sub_step:0 started_auto_step:0 stv0299_set_frontend : FE_SET_FRONTEND stv0299: stv0299_enable_plli2c() stv0299: stv0299_set_FEC(): FEC = 3 stv0299: stv0299_set_symbolrate() stv0299_set_symbolrate(): Symbol rate = 5242880 stv0299: stv0299_read_status : FE_READ_STATUS : VSTATUS: 0x81, signal: 0xc0 dvb_frontend_add_event ... The whole output is in the attchmnt as well as the modified stv0299.c Doing some debug it turns out that stv0299_read_status() returns a value to the scan util of 0x03, instead of the FE_HAS_LOCK that would be the right value and this throws the tuning failed!!! msg. Any help would be really appreciated. Thanks! Regards, -- Pedro Aguilar___ 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] Hauppauge HVR-4000
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 could you say - which CPU and the graphic card do you use for HDTV watching ? what about CPU's load during it? regards Igor ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Need info about AAC in DVB
Il Friday 05 October 2007 13:25:01 hai scritto: On Fri, 2007-10-05 at 13:10 +0200, Nico Sabbi wrote: ... thanks, it's what I needed to know; ... Good :-) Do you have that PDF? the link is broken Try this link: http://www.dvb.org/technology/standards/a001r7.tm1214r30.dTS101154. v1.8.1.pdf Unfortunately the sample I can grab from your dump don't seem to comply with teh specs of LATM/LOAS I have, so the code I'm writing doesn't work. If someone has a recent spec of ISO-14496-3 please hand it to me. Thanks, Nico ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Reloading DVB drivers broken since 2.6.22, worked in 2.6.21
After a dvb card driver is unloaded and then loaded again, it is no longer possible to access the dvr device. Example: cat /dev/dvb/adapter0/dvr0 kill with ^C rmmod cx88-dvb modprobre cx88-dvb cat /dev/dvb/adapter0/dvr0 cat: /dev/dvb/adapter0/dvr0: No such device On kernel 2.6.21, this worked fine. In order to get dvb working again, it's necessary to unload and reload the dvb-core modules. I strongly suspect commit 57861b432bda77f8bfafda2fb6f5a922d5f3aef1 is somehow related to this problem. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Anysee E30C Plus (Re: DVB-C developers interested in receiving an USB adapter for hacking?)
terve
First version of the driver is attached. It does not have remote control
, nor CI support yet. I will add remote control in next few days...
I can test it only with QAM128 symbol rate 6.875 and it seems work
fine. All test reports, success and fails, are highly welcome.
Some small changes to current TDA10023 driver was needed, those are now
under the #ifdef's. We should find better solution for needed changes.
Proposals for resolving the situation are also highly welcome in this
issue too. One solution is to put needed parameters to driver config, is
there better ones? Hartmut Birr, could you investigate this?
Regards,
Antti
diff -r e95ee8dec49d linux/drivers/media/dvb/dvb-usb/Kconfig
--- a/linux/drivers/media/dvb/dvb-usb/Kconfig Sun Sep 30 10:20:18 2007 -0300
+++ b/linux/drivers/media/dvb/dvb-usb/Kconfig Mon Oct 01 05:43:04 2007 +0300
@@ -239,3 +239,10 @@ config DVB_USB_AF9005_REMOTE
Say Y here to support the default remote control decoding for the
Afatech AF9005 based receiver.
+config DVB_USB_ANYSEE
+ tristate Anysee E30C DVB-C USB2.0 support
+ depends on DVB_USB
+ select DVB_TDA10023 if !DVB_FE_CUSTOMISE
+ help
+ Say Y here to support the Anysee E30C DVB-C USB2.0 receiver.
+
diff -r e95ee8dec49d linux/drivers/media/dvb/dvb-usb/Makefile
--- a/linux/drivers/media/dvb/dvb-usb/Makefile Sun Sep 30 10:20:18 2007 -0300
+++ b/linux/drivers/media/dvb/dvb-usb/Makefile Sun Sep 30 19:58:07 2007 +0300
@@ -61,4 +61,7 @@ dvb-usb-af9005-remote-objs = af9005-remo
dvb-usb-af9005-remote-objs = af9005-remote.o
obj-$(CONFIG_DVB_USB_AF9005_REMOTE) += dvb-usb-af9005-remote.o
+dvb-usb-anysee-objs = anysee.o
+obj-$(CONFIG_DVB_USB_ANYSEE) += dvb-usb-anysee.o
+
EXTRA_CFLAGS += -Idrivers/media/dvb/dvb-core/ -Idrivers/media/dvb/frontends/
diff -r e95ee8dec49d linux/drivers/media/dvb/dvb-usb/anysee.c
--- /dev/null Thu Jan 01 00:00:00 1970 +
+++ b/linux/drivers/media/dvb/dvb-usb/anysee.c Sat Oct 06 02:21:40 2007 +0300
@@ -0,0 +1,301 @@
+/* DVB USB Linux driver for Anysee E30C DVB-C USB2.0 receiver
+ *
+ * Copyright (C) 2007 Antti Palosaari [EMAIL PROTECTED]
+ *
+ * This program is free software; you can redistribute it and/or modify it
+ * under the terms of the GNU General Public License as published by the Free
+ * Software Foundation, version 2.
+ *
+ * see Documentation/dvb/README.dvb-usb for more information
+ */
+
+#include anysee.h
+#include tda1002x.h
+
+/* debug */
+//static int dvb_usb_anysee_debug = -1;
+static int dvb_usb_anysee_debug;
+module_param_named(debug, dvb_usb_anysee_debug, int, 0644);
+MODULE_PARM_DESC(debug, set debugging level (1=rc (or-able)). DVB_USB_DEBUG_STATUS);
+
+static int anysee_usb_ctrl_msg(struct usb_device *udev, u8 *snd_buf, u8 snd_len, u8 *reply)
+{
+ int act_len, ret;
+ u8 buf[64];
+ static u8 seq; /* packet sequence number */
+
+ memcpy(buf[0], snd_buf, snd_len);
+ buf[60] = seq++;
+
+ deb_xfer( );
+ debug_dump(buf, sizeof(buf), deb_xfer);
+ /* send request */
+ ret = usb_bulk_msg(udev, usb_sndbulkpipe(udev, 0x01), buf, sizeof(buf), act_len, ANYSEE_USB_TIMEOUT);
+ if (ret)
+ err(%s: sending failed: %d (%d/%d), __FUNCTION__, ret, sizeof(buf), act_len);
+ else
+ ret = act_len != sizeof(buf) ? -1 : 0;
+
+ if (ret)
+ return ret;
+
+ /* receive 1st answer (skip, answer to previous call) */
+ ret = usb_bulk_msg(udev, usb_rcvbulkpipe(udev, 0x81), buf, sizeof(buf), act_len, ANYSEE_USB_TIMEOUT);
+ if (ret) {
+ err(%s: 1st receiving failed: %d, __FUNCTION__, ret);
+ return ret;
+ }
+// deb_xfer( );
+// debug_dump(buf, act_len, deb_xfer);
+
+ /* receive 2nd answer */
+ ret = usb_bulk_msg(udev, usb_rcvbulkpipe(udev, 0x81), buf, sizeof(buf), act_len, ANYSEE_USB_TIMEOUT);
+ if (ret) {
+ err(%s: 2nd receiving failed: %d, __FUNCTION__, ret);
+ return ret;
+ }
+ deb_xfer( );
+ debug_dump(buf, act_len, deb_xfer);
+
+ /* read request, copy return data to return buf */
+ if(reply != NULL)
+ *reply = buf[0];
+
+ return 0;
+}
+
+static int anysee_read_reg(struct dvb_usb_device *d, u16 reg, u8 *val)
+{
+ u8 buf[] = {CMD_REG_READ, (reg 0xff00) 8, reg 0x00ff, 0x01};
+ return anysee_usb_ctrl_msg(d-udev, buf, sizeof(buf), val);
+}
+
+static int anysee_write_reg(struct dvb_usb_device *d, u16 reg, u8 val)
+{
+ u8 buf[] = {CMD_REG_WRITE, (reg 0xff00) 8, reg 0x00ff, 0x01, val};
+ return anysee_usb_ctrl_msg(d-udev, buf, sizeof(buf), NULL);
+}
+
+static int anysee_streaming_ctrl(struct dvb_usb_device *d, u8 onoff)
+{
+ u8 buf[] = {CMD_STREAMING_CTRL, onoff, 0x00};
+ deb_info(%s: onoff:%02x\n, __FUNCTION__, onoff);
+ return anysee_usb_ctrl_msg(d-udev, buf, sizeof(buf), NULL);
+}
+
+static int anysee_led_ctrl(struct dvb_usb_device *d, u8 state, u8 interval)
+{
+ u8 buf[] = {CMD_LED_CTRL, 0x01, state, interval};
+ deb_info(%s: state:%02x interval:%02x\n, __FUNCTION__, state, interval);
+ return anysee_usb_ctrl_msg(d-udev, buf, sizeof(buf), NULL);
+}
+
+/* I2C */
+static int anysee_master_xfer(struct i2c_adapter* adap, struct i2c_msg *msg, int num)
+{
+ struct
