[linux-dvb] DVB driver for WinTV-D card
Olin Atkinson wrote > Has anyone done any work on getting the > digital side working? I would love to help. I am an electrical engineer > who has worked as a java programmer for the last 11 years. I have some free > time and would like to play with this for the fun of it. > Stemming from an IRC discussion, held a couple of months ago, about the FCV1236 tuner, Mike Krufky (who is also a WinTV-D owner...or at least was) and I looked at the WinTV-D, and, as far as what we could see from the archives, no work ever went in towards the digital side. It would likely not be an easy task at that -- one of the difficulties right out of the gate would be in obtaining documentation for the LG decoder -- there is none to be found via google, so other means will likely be necessary. I don't know if LG or Hauppauge would be interested in furnishing you with a data sheet (Mike had inquired with Hauppauge previously, but there apparently wasn't much interest ... but he would be able to comment better now, given a change in circumstances). ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] ATI Theatre 650 card support?
Baha Baydar wrote > I've searched through the archives looking for any updates for support > for the ATI theatre 650 chipset/cards and haven't found much. > > Has the recent release of video card documentation from AMD/ATI given > any indication that other chipset support is in the works? > I don't think anyone is working on support -- there are three missing pieces of documentation: that for the tuner in the Samsung module, the 31x demod, & the 650 IC > Has the recent release of video card documentation from AMD/ATI given > any indication that other chipset support is in the works? > No idea. > Also, this page > http://www.linuxtv.org/wiki/index.php/ATI/AMD_TV_Wonder_650 asks what > the two chips next to the PCI connector are. On my card (P/N: > 102A6980111 01) the two chips are labelled: > > P15C > 16211AE > Thanks for the ID and update to the wiki page! ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Can the em28xx based tv cards still work under kernel 2.6.24?
Hi, Markus. I got the news the em28xx codes was removed from the v4l-dvb repo, but can the em28xx based tv cards still work under Linux kernel? And does libtuner.so support both the em28xx based cards demod and tuner in the future? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] tt s2-3200
hello, is dvbscan or scandvb working with tt s2-3200? i could not get it working using latest multiproto or stb0899 (not -c5)... i'll get a lot of kernel messages and finally get stb0899 get tired (in dmesg) ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] mantis branch on jusst.de - vp1034 can't tune to vertical channels
Gernot Pansy wrote: > On Sunday 14 October 2007 23:40:22 you wrote: >> Gernot Pansy wrote: > i have to verify, but it seems that these channels have all a low symbol rate. 22Msps is not a low rate. I guess something else is wrong. Have you looped the cables in between multiple tuners ? such as (i can't imagine all the cases) >> Maybe too much attenuation at that frequency due to cable and or >> other larger capacitive reactance lumped, probably ? (in case such >> a frequency exists, wild guesses ) >> >> Trying to guess why the demodulator thinks, no signal ... >> >> >> [ 1022.316000] mb86a16_set_fe: freq=2062 Mhz, symbrt=22000 Ksps >> [ 1022.316000] mb86a16_write: writing to [0x08],Reg[0x32],Data[0x02] >> [ 1022.316000] mb86a16_write: writing to [0x08],Reg[0x06],Data[0xdf] >> [ 1022.32] mantis start feed & dma >> [ 1022.32] mb86a16_write: writing to [0x08],Reg[0x0a],Data[0x3d] >> >> --- Snip --- >> >> [ 1022.416000] mb86a16_write: writing to [0x08],Reg[0x25],Data[0x01] >> [ 1022.416000] mb86a16_write: writing to [0x08],Reg[0x2b],Data[0xd4] >> [ 1022.416000] mb86a16_write: writing to [0x08],Reg[0x2c],Data[0x0f] >> [ 1022.416000] mb86a16_write: writing to [0x08],Reg[0x0c],Data[0x04] >> [ 1022.424000] mb86a16_set_fe: NO -- SIGNAL >> [ 1022.424000] sync_chk: Status = 00, Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DVB-S2 Multiple logical TS on the same frequency
Johannes Stezenbach wrote: > On Sun, Oct 14, 2007, Manu Abraham wrote: >> You can have MIS in 2 cases again: >> >> 1) Transport Streams >> >> a) When it is SIS, it is similar to our normal DVB-S transmissions >> b) When it is flagged MIS in the Baseband Header, we have Multiple Streams. >> When it is MIS, if the logical streams are scrambled, we will need to >> route the relevant >> stream to the CA module, which means we have some additional job at the >> demuxer level. >> (this will be a bit of headache, coupled with a CA device) >> >> 2) Generic Streams (note this need not be a MPEG2 stream at all) >> This at least we can pipe everything to userspace at least as a last >> resort. >> >> Temporarily, we do not need to worry about Generic streams (Single or >> Multiple), since they >> aren't basically used in the broadcast profiles, _but_ MTS might be. > > ACK -- see old posting: > http://article.gmane.org/gmane.linux.drivers.dvb/26040 > > However, contrary to what is written there I believe the demod > recognizes SIS vs. MIS and dis/enables the stream filter automatically. > I guess if you fail to set the correct ISI for MIS, you get no > output (or the wrong one). For SIS the stream id filter is irrelevant, > you can set it to any value. If the demod was to filter Multiple streams automatically, it will mean something like choosing all the options in a multiple choice question, where you are supposed to choose one. I can't see anyway how the demod can select the streams that which you are interested in, without the user telling it what you want. > > IMHO all you need is to add an u8 input_stream_identifier > to struct dvbs2_params. You take the value and write it > in a demod register -- done. > > You can get the input_stream_identifier (ISI) from the > S2 satellite delivery system descriptor, see EN 300 468. yep > > (In the worst case the demod wouldn't en/disable the stream id > filter automatically, so you'd need to read SIS/MIS flags > from a register after tuning and do it manually -- but that's > all internal to the driver and not in the API. I think.) > > (BTW, ARIB has a similar feature, transport_stream_id, see > http://linuxtv.org/cgi-bin/viewcvs.cgi/dvb-kernel-v4/linux/include/linux/dvb/frontend.h?rev=1.20.2.2&only_with_tag=ARIB_extension&view=auto > ) > > I'm very confident the output of the demod is a single TS in all > cases, and this has nothing to do with the demux. Maybe, not very sure on that. Also the specifications additionally adds this: 5.2 SDTV and HDTV broadcasting with differentiated channel protection The DVB-S2 system may deliver broadcasting services over multiple Transport Streams, providing differentiated error protection per multiplex (VCM mode) (see note). A typical application is broadcasting of a highly protected multiplex for SDTV, and of a less protected multiplex for HDTV. Figure 17 shows an example configuration at the transmitting side. Assuming to transmit 27,5 Mbaud and to use 8PSK 3/4 and QPSK 2/3, 40 Mbit/s would be available for two HDTV programmes and 12 Mbit/s for two-three SDTV programmes. Regards, Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DVB-S2 Multiple logical TS on the same frequency
On Sun, Oct 14, 2007, Manu Abraham wrote: > > You can have MIS in 2 cases again: > > 1) Transport Streams > > a) When it is SIS, it is similar to our normal DVB-S transmissions > b) When it is flagged MIS in the Baseband Header, we have Multiple Streams. > When it is MIS, if the logical streams are scrambled, we will need to > route the relevant > stream to the CA module, which means we have some additional job at the > demuxer level. > (this will be a bit of headache, coupled with a CA device) > > 2) Generic Streams (note this need not be a MPEG2 stream at all) > This at least we can pipe everything to userspace at least as a last > resort. > > Temporarily, we do not need to worry about Generic streams (Single or > Multiple), since they > aren't basically used in the broadcast profiles, _but_ MTS might be. ACK -- see old posting: http://article.gmane.org/gmane.linux.drivers.dvb/26040 However, contrary to what is written there I believe the demod recognizes SIS vs. MIS and dis/enables the stream filter automatically. I guess if you fail to set the correct ISI for MIS, you get no output (or the wrong one). For SIS the stream id filter is irrelevant, you can set it to any value. IMHO all you need is to add an u8 input_stream_identifier to struct dvbs2_params. You take the value and write it in a demod register -- done. You can get the input_stream_identifier (ISI) from the S2 satellite delivery system descriptor, see EN 300 468. (In the worst case the demod wouldn't en/disable the stream id filter automatically, so you'd need to read SIS/MIS flags from a register after tuning and do it manually -- but that's all internal to the driver and not in the API. I think.) (BTW, ARIB has a similar feature, transport_stream_id, see http://linuxtv.org/cgi-bin/viewcvs.cgi/dvb-kernel-v4/linux/include/linux/dvb/frontend.h?rev=1.20.2.2&only_with_tag=ARIB_extension&view=auto ) I'm very confident the output of the demod is a single TS in all cases, and this has nothing to do with the demux. Regards, Johannes ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Tuner not detected on second Kworld card
Am Sonntag, den 14.10.2007, 15:34 -0400 schrieb CityK: > David Engel wrote: > > The minor problem I mentioned earlier has to do with using the > > saa7134-alsa module to capture sound directly from the card. A quick > > glance at the driver source code looks like it shold support 32 and 48 > > kHz sampling rates. I've only been able to get 32 kHz working well so > > far with MythTV. Trying 48 kHz results in some sort of rate mismatch. > > Is 48 kHz supposed to work? > ... > > I tried using mplayer with 48 kHz audio and got the same results. > > Regardless of the requested audio rate, the cx88-alsa driver or > > hardware only supplies 32 kHz audio. The result is audio underruns > > and chipmunk audio because the samples that are received are being > > played too fast. Can anyone confirm the Kworld card can only do 32 > > kHz? > > I could have sworn I just wrote about this -- email? wiki? But alas, I > can't find a thing. In any regard ... > > Yes, you can only use 32KHz from the tuner with the saa713x. This is a > hardware limitation of the chip in regards to handling of SIF sources. > For further information, search through the V4L achieves using various > "saa7134" or "saa713x" and "32KHz" and "alsa" combinations. There should > be plenty of good info. (Example: > http://marc.info/?l=linux-video&w=2&r=1&s=32KHz+saa7134&q=b) > > However, that said, I'm just thinking aloud here about this case, as > this actually presents a curious question. Here goes: > > The NIM on these boards (TUV1236D) contains a TDA9887, which is capable > of SIF demodulation, and hence, if utilised, would be feeding the > saa713x a baseband audio signal for ADC. Yet, given that in field > testing shows the 32KHz limitation, it would seem to indicate that the > SIF capability of the TDA9887 is being ignored and that, instead, the > broadcast audio is being sent straight to the saa713x for processing > (ie. tuner -> saa713x for SIF demod & then ADC). > > I'm wondering if this is a case of: > (1) hard wiring from the TUV1236D module (broadcast audio output) to the > saa713x > or > (2) if there exist alternate pathways/routes in the TUV1236D for the > audio signal i.e.: > (i) tuner -> TDA9887 for SIF demodulation -> baseband audio to saa713x > for ADC > (ii) tuner -> saa713x for SIF demod & then ADC > > If it is a case of 2), then it is obvious that the later route (ii) is > being utilized ... and, if it is a case of 2), then the obvious follow > up question is: How do you enable the more desirable pathway (i) ? ... > i.e. make use of the TDA9887 for SIF demodulation and feed the resultant > baseband signal to the saa713x, which, consequently, would allow for the > selection of sampling rates other then 32KHz during the ADC phase. Limitation is, that there is no direct stereo TV sound output from those tuners. The saa7130 chip uses always baseband audio from the tuner and has no audio ADCs. That,s why no dma sound is supported and always a loopthrough connection to the sound card is needed and why it has only mono TV sound. Radio and other analog inputs can be stereo. DVB just gets pumped through the TS interface and the dma engines. The saa7134 chip has no stereo audio support for System M and the saa7133 has no support for dual FM (A2) stereo. Currently only saa7135 and saa7131e support all kind of TV sound. The two others could utilize additional SIF/MPX sound decoding chips, then your scenario would become true. Suggested as a solution in such case, but not yet seen. How to make use of which audio coming from the tuner also depends of the audio system in use. For example think about mono on the first sound carrier and NICAM on the second. You will need the saa713x NICAM decoder to get stereo sound. On the Philips MultiEurope MK3s with tda9887 only radio comes stereo separated by the tda7040 to either the LINE1 or LINE2 pair of analog inputs. If switched back to TV mode, you get from those two lines equal TV mono audio, also about 6 db lower as otherwise, IIRC. Some cards still use a TV mono section with vmux TV and same amux than used for radio exactly for that reason, as workaround for having problems with stereo sound in the beginnings. That is also what you see on the saa7130 chips. If needed, we might continue on the video4linux-list ... The other issue sounds a bit weired or my poor English fails. Multiple identical cards should be auto detected like they are found walking down the PCI devices and lining up minors. Cheers, Hermann ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] mantis branch on jusst.de - vp1034 can't tune to vertical channels
On Sunday 14 October 2007 23:40:22 you wrote: > Gernot Pansy wrote: > > hmm, i see now there are other channels i can't tune to. like this one: > > You really have a signal ? The frequency also seems quite a bit high > (although still in the spectrum) But the demodulator seems to think > that there is no signal at all. there have to be a signal, because i never had any troubles to tune to one of these channel with the vp1030 and vp1041. i have to verify, but it seems that these channels have all a low symbol rate. notz > > Maybe too much attenuation at that frequency due to cable and or > other larger capacitive reactance lumped, probably ? (in case such > a frequency exists, wild guesses ) > > Trying to guess why the demodulator thinks, no signal ... > > > [ 1022.316000] mb86a16_set_fe: freq=2062 Mhz, symbrt=22000 Ksps > [ 1022.316000] mb86a16_write: writing to [0x08],Reg[0x32],Data[0x02] > [ 1022.316000] mb86a16_write: writing to [0x08],Reg[0x06],Data[0xdf] > [ 1022.32] mantis start feed & dma > [ 1022.32] mb86a16_write: writing to [0x08],Reg[0x0a],Data[0x3d] > > --- Snip --- > > [ 1022.416000] mb86a16_write: writing to [0x08],Reg[0x25],Data[0x01] > [ 1022.416000] mb86a16_write: writing to [0x08],Reg[0x2b],Data[0xd4] > [ 1022.416000] mb86a16_write: writing to [0x08],Reg[0x2c],Data[0x0f] > [ 1022.416000] mb86a16_write: writing to [0x08],Reg[0x0c],Data[0x04] > [ 1022.424000] mb86a16_set_fe: NO -- SIGNAL > [ 1022.424000] sync_chk: Status = 00, > > > Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [Bulk] Re: Off Topic: questioning Btty Gallery's operations
chazim wrote: > Is there any reason he's apparently been posting V4L list boards, and, > not boards listed through Linux-dvb list? No idea. I don't know when he last updated his website, though, I don't think he has any bias against info from either list > Again, hoping Gunther saw that, and, would start maintaining his site > again. I mean, the list has to find the units it writes support for > from somewhere, what motivates them to choose to write support for one > unit over another is a mystery. So, maybe his site acts as a visual > aid, for both lists. As much as for the end result, which should > useful to aid end user ability to choose boards that aren't factor-x. > But, in the long run, since this units information has been available > all this time, why does this units status remain as an unsupported > device status? Gunther's site, I can assure you, is not a catalyst for device driver development. In addition, I think perhaps you have a misconception about the number of people providing development. To be clear, there are very few. Consequently, there should be no mystery surrounding the motivation to write device support --- as such motivation could probably be summarized as follows: - having an interest in doing so ... perhaps based upon personal ownership of the device or just the general enjoyment/challenge of the coding - ease of adding support both in terms of coding complexity and the time required - and occasionally through contract By in large, "interest in doing so" stands out amongst the others. If there were a greater pool of developers, it stands to chance that there would be a wider base of interest and, hence, a greater amount of devices that end up being supported. > since this units information has been available all this time, why > does this units status remain as an unsupported device status? I can > plug my Technisat SS2 PCI into my Linux machine, and Myth, VDR or, > Kaffiene can pick it up, and, I can play with it (and it too has the > stb0299 tuner). While the fact that two devices (one supported, the other not) have the same components can be of great assistance to the development of support for the latter device, it still does not guarantee that such support is easily obtained. There may be factors which are dissimilar between the devices (i.e. firmware, GPIO etc). Second, developing support for a device not in personal personal possession can be rather difficult. You'll have to find a developer who is willing to work with you under such conditionsor, take that initiative yourself. > It starts to look like the lists politics, is steering end users > towards a narrow range of chipsets, or, products from one geographical > location. By what's being supported and what's not, it looks like > political bias or graff. Euro stuff gets support, Asian stuff gets > very little. There is no bias. What you are observing is solely a consequence of what I discussed earlier: - There are few developers. - these few developers work on things which interest them personally Find Asian developers with interest in such devices, and you'll likely find support will follow. Otherwise, it isn't going to appear on its own ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] mantis branch on jusst.de - vp1034 can't tune to vertical channels
Gernot Pansy wrote: > hmm, i see now there are other channels i can't tune to. like this one: > You really have a signal ? The frequency also seems quite a bit high (although still in the spectrum) But the demodulator seems to think that there is no signal at all. Maybe too much attenuation at that frequency due to cable and or other larger capacitive reactance lumped, probably ? (in case such a frequency exists, wild guesses ) Trying to guess why the demodulator thinks, no signal ... [ 1022.316000] mb86a16_set_fe: freq=2062 Mhz, symbrt=22000 Ksps [ 1022.316000] mb86a16_write: writing to [0x08],Reg[0x32],Data[0x02] [ 1022.316000] mb86a16_write: writing to [0x08],Reg[0x06],Data[0xdf] [ 1022.32] mantis start feed & dma [ 1022.32] mb86a16_write: writing to [0x08],Reg[0x0a],Data[0x3d] --- Snip --- [ 1022.416000] mb86a16_write: writing to [0x08],Reg[0x25],Data[0x01] [ 1022.416000] mb86a16_write: writing to [0x08],Reg[0x2b],Data[0xd4] [ 1022.416000] mb86a16_write: writing to [0x08],Reg[0x2c],Data[0x0f] [ 1022.416000] mb86a16_write: writing to [0x08],Reg[0x0c],Data[0x04] [ 1022.424000] mb86a16_set_fe: NO -- SIGNAL [ 1022.424000] sync_chk: Status = 00, Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] v4l/scripts/make_config_compat.pl
Hi,
the script doesn't work properly when the KDIR given is outside the
kernel source tree, like it is for most distros which build differently
configured kernel images from the same source tree.
I've therefore hacked it like that:
diff -r 5b19ac1cddb5 v4l/scripts/make_config_compat.pl
--- a/v4l/scripts/make_config_compat.pl Wed Oct 10 13:12:13 2007 +0400
+++ b/v4l/scripts/make_config_compat.pl Sun Oct 14 22:05:22 2007 +0200
@@ -6,6 +6,9 @@ my $outfile=shift or die "should specify
my $outfile=shift or die "should specify an output config file";
my $out;
+
+print STDERR "kdir: $kdir\n";
+$kdir='/usr/src/linux-2.6.21-3';
sub check_spin_lock()
{
After that, the build succeeds. The attached output shows the first few
lines after typing make. As you can see, I do build the dvb tree outside
of the kernel tree. This is on a openSUSE 10.2 system which uses a
kernel of openSUSE 10.3 alpha, due to some debugging issues.
Bye.
--
Dipl.-Inform. (FH) Reinhard Nissl
mailto:[EMAIL PROTECTED]
video:/soft/src/multiproto # make
make -C /store/soft/src/multiproto/v4l
make[1]: Entering directory `/store/soft/src/multiproto/v4l'
perl scripts/make_config_compat.pl /lib/modules/2.6.21-3-default/build
./.myconfig ./config-compat.h
kdir: /lib/modules/2.6.21-3-default/build
creating symbolic links...
make -C /lib/modules/2.6.21-3-default/build
SUBDIRS=/store/soft/src/multiproto/v4l modules
make[2]: Entering directory `/usr/src/linux-2.6.21-3-obj/i386/default'
make -C ../../../linux-2.6.21-3 O=../linux-2.6.21-3-obj/i386/default modules
CC [M] /store/soft/src/multiproto/v4l/flexcop-pci.o
CC [M] /store/soft/src/multiproto/v4l/flexcop-usb.o
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] mantis branch on jusst.de - vp1034 can't tune to vertical channels
hmm, i see now there are other channels i can't tune to. like this one: zapping to 9 'TW1': sat 0, frequency = 12662 MHz H, symbolrate 2200, vpid = 0x03f2, apid = 0x03f3 using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' status 00 | signal ff9c | snr ff02 | ber 016c | unc 00fe | status 00 | signal ff9d | snr ff02 | ber 0166 | unc 00fc | status 00 | signal ff9d | snr ff02 | ber 0111 | unc 00fd | notz On Sunday 14 October 2007 21:27:11 Manu Abraham wrote: > Gernot Pansy wrote: > > thank you, the patch is working for me. > > > > the time from starting initalizaiton until i get a lock is about > > ~400msec. > > In the ideal case according to the vendor, it should have been 300 - 350 mS > max. But i guess 50 - 100mS deviation is peanuts compared to most other > demods. Well, looks quite ok. > > Also would like to know how much time it takes to LOCK on Low symbol rates. > > > Manu > > > notz > > > > On Sunday 14 October 2007 19:18:18 Manu Abraham wrote: > >> Gernot Pansy wrote: > >>> hy, > >>> > >>> i got trough warranty issues for my old vp1030 a new vp1034. i tried > >>> this card now with this branch but the card can only tune to vertical > >>> channels (horizontal are working in less than a second). > >> > >> Uh. I forgot the GPIO bit flip from Marco, will apply it later, but to > >> get you going at the earliest Michel Verbraak has a cached copy, it > >> should apply cleanly still. You should be going ahead quite fine. > >> > >> http://www.verbraak.org/mantis_gpio_set_bits_fix.patch > >> > >> After the same, can you pleas clock the LOCK 'ing time please ? I am > >> currently checking how much deviation i am having from the actual device > >> specifications in terms of LOCK 'ing time. > >> > >> Thanks for reporting. > >> > >> Manu > > > > ___ > > linux-dvb mailing list > > linux-dvb@linuxtv.org > > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb dmesg.txt.gz Description: GNU Zip compressed data ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Important note to em28xx/xc3028 users
On 10/14/07, Richard (MQ) <[EMAIL PROTECTED]> wrote: > Aidan Thornton wrote: > > Hi, > > > > Unfortunately, Markus has pulled offline all his repositories > > containing Linux drivers. (You can see > > http://kerneltrap.org/mailarchive/linux-kernel/2007/10/14/337446 for > > the reason). This mainly affects users of em28xx-based and > > xc3028-based devices. I suggest those of you with local copies make > > sure you keep them backed up; you may not be able to get another copy. > > :-( missed the boat ... > > > > > Users of em28xx-based devices can use my > > http://www.makomk.com/hg/v4l-dvb-makomk repository, which is still > > maintained and should remain so for as long as necessary. In theory, > > it should support all the em28xx-based devices that Markus' > > v4l-dvb-experimental driver does, but it hasn't been tested with > > anything other than the device I use (and one obscure device not > > supported by Markus' driver). > > Please can someone with write access update the wiki, esp. at > http://mcentral.de/wiki/index.php/AVerMedia_AverTV_Hybrid_FM_PCI_A16D > - I just went to get this code but of course hg fails: > > > $ hg clone http://mcentral.de/hg/~mrec/v4l-dvb-experimental/ > > abort: 'http://mcentral.de/hg/~mrec/v4l-dvb-experimental/' does not appear > > to be an hg repository! > > I will try again with your repository & hope it includes the A16D patch? Nope, sorry - my repository is only for em28xx-based devices, and the A16D is saa7135-based. I do have, however, a relatively recent copy of v4l-dvb-experimental, which you can download as a tarball from http://www.makomk.com/~aidan/v4l-dvb-experimental.tar.bz2 (I don't have the space to offer it unzipped). I think it may be a revision or two out of date, but the last log entry is: changeset: 5886:55d60e988b89 tag: tip user:Markus Rechberger <[EMAIL PROTECTED]> date:Fri Oct 12 01:03:30 2007 +0200 summary: Aver TV Hybrid A16D add DVB support (received from Miroslav Bobal bobal at mbfun dot net) which might be what you're looking for. Aidan ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] [PATCH] Spezial Lifeview DVB-S Card without eeprom
The patch has already been posted in May by Michael Möhle without getting
attention: http://linuxtv.org/pipermail/linux-dvb/2007-May/018007.html
Several users in the german vdrportal forum use this card, therefore the patch
is included in my LinVDR kernel package since months.
To patch should really be included into the hg.
I attach a diff against hg from today. It is still the same patch originally
written by Ralph Metzler.
Greets,
Martin Dauskardt
diff -ur v4l-dvb-ea93c93f1547-orig/linux/drivers/media/video/saa7134/saa7134-cards.c v4l-dvb-ea93c93f1547/linux/drivers/media/video/saa7134/saa7134-cards.c
--- v4l-dvb-ea93c93f1547-orig/linux/drivers/media/video/saa7134/saa7134-cards.c 2007-10-11 14:09:06.0 +0200
+++ v4l-dvb-ea93c93f1547/linux/drivers/media/video/saa7134/saa7134-cards.c 2007-10-14 17:48:49.0 +0200
@@ -3591,6 +3591,26 @@
.tv = 1,
}},
},
+ [SAA7134_BOARD_LIFEVIEW_DVBS] = {
+ /* LifeView FlyDVB-s */
+ /* Ralph Metzler <[EMAIL PROTECTED]> */
+ .name = "LifeView FlyDVB-S",
+ .audio_clock= 0x0020,
+ .tuner_type = TUNER_ABSENT,
+ .radio_type = UNSET,
+ .tuner_addr = ADDR_UNSET,
+ .radio_addr = ADDR_UNSET,
+ .mpeg = SAA7134_MPEG_DVB,
+ .inputs = {{
+ .name = name_comp1, /* Composite input */
+ .vmux = 3,
+ .amux = LINE1,
+ },{
+ .name = name_svideo, /* S-Video signal on S-Video input */
+ .vmux = 8,
+ .amux = LINE1,
+ }},
+ },
};
const unsigned int saa7134_bcount = ARRAY_SIZE(saa7134_boards);
Nur in v4l-dvb-ea93c93f1547/linux/drivers/media/video/saa7134: saa7134-cards.c.orig.
diff -ur v4l-dvb-ea93c93f1547-orig/linux/drivers/media/video/saa7134/saa7134-dvb.c v4l-dvb-ea93c93f1547/linux/drivers/media/video/saa7134/saa7134-dvb.c
--- v4l-dvb-ea93c93f1547-orig/linux/drivers/media/video/saa7134/saa7134-dvb.c 2007-10-11 14:09:06.0 +0200
+++ v4l-dvb-ea93c93f1547/linux/drivers/media/video/saa7134/saa7134-dvb.c 2007-10-14 17:48:49.0 +0200
@@ -43,6 +43,8 @@
#include "tda826x.h"
#include "tda827x.h"
#include "isl6421.h"
+#include "tua6100.h"
+#include "stv0299.h"
MODULE_AUTHOR("Gerd Knorr <[EMAIL PROTECTED]> [SuSE Labs]");
MODULE_LICENSE("GPL");
@@ -839,6 +841,130 @@
.demod_address= 0x0a,
};
+/* -- */
+
+static int philips_su1278_ty_ci_tuner_set_params(struct dvb_frontend *fe,
+ struct dvb_frontend_parameters *params)
+{
+ u32 div;
+ u8 buf[4];
+ struct saa7134_dev *dev = fe->dvb->priv;
+ struct i2c_msg msg = {.addr = 0x61,.flags = 0,.buf = buf,.len = sizeof(buf) };
+
+ if ((params->frequency < 95) || (params->frequency > 215))
+ return -EINVAL;
+
+ div = (params->frequency + (125 - 1)) / 125; // round correctly
+ buf[0] = (div >> 8) & 0x7f;
+ buf[1] = div & 0xff;
+ buf[2] = 0x80 | ((div & 0x18000) >> 10) | 4;
+ buf[3] = 0x20;
+
+ if (params->u.qpsk.symbol_rate < 400)
+ buf[3] |= 1;
+
+ if (params->frequency < 125)
+ buf[3] |= 0;
+ else if (params->frequency < 155)
+ buf[3] |= 0x40;
+ else if (params->frequency < 205)
+ buf[3] |= 0x80;
+ else if (params->frequency < 215)
+ buf[3] |= 0xC0;
+
+ if (fe->ops.i2c_gate_ctrl)
+ fe->ops.i2c_gate_ctrl(fe, 1);
+ if (i2c_transfer(&dev->i2c_adap, &msg, 1) != 1)
+ return -EIO;
+ return 0;
+}
+
+static int lifeview_set_symbol_rate(struct dvb_frontend *fe, u32 srate, u32 ratio)
+{
+ u8 aclk = 0;
+ u8 bclk = 0;
+ u8 m1;
+
+ aclk = 0xb5;
+ if (srate < 200)
+ bclk = 0x86;
+ else if (srate < 500)
+ bclk = 0x89;
+ else if (srate < 1500)
+ bclk = 0x8f;
+ else if (srate < 4500)
+ bclk = 0x95;
+
+ m1 = 0x14;
+ if (srate < 400)
+ m1 = 0x10;
+
+ stv0299_writereg(fe, 0x13, aclk);
+ stv0299_writereg(fe, 0x14, bclk);
+ stv0299_writereg(fe, 0x1f, (ratio >> 16) & 0xff);
+ stv0299_writereg(fe, 0x20, (ratio >> 8) & 0xff);
+ stv0299_writereg(fe, 0x21, (ratio) & 0xf0);
+ stv0299_writereg(fe, 0x0f, 0x80 | m1);
+
+ return 0;
+}
+
+static u8 lifeview_inittab[] = {
+ 0x01, 0x15,
+ 0x02, 0x30,
+ 0x03, 0x00,
+ 0x04, 0x7d, /* F22FR = 0x7d, F22 = f_VCO / 128 / 0x7d = 22 kHz */
+ 0x05, 0x35, /* I2CT = 0, SCLT = 1, SDAT = 1 */
+ 0x06, 0x40, /* DAC not used, set to high impendance mode */
+ 0x07, 0x00, /* DAC LSB */
+ 0x08, 0x40, /* DiSEqC off */
+ 0x09, 0x00, /* FIFO */
+ 0x0c, 0x51, /* OP1 ctl = Normal, OP1 val = 1 (LNB Power ON) */
+ 0x0d, 0x82, /* DC offset compensation = ON, beta_agc1 = 2 */
+ 0x0e, 0x23, /* alpha_tmg = 2, beta_tmg = 3 */
+ 0x10, 0x3f, // AGC2 0x3d
+ 0x11, 0x84,
+ 0x12, 0xb9,
+ 0x15, 0xc9, // lock detector threshold
+ 0x16, 0x00,
+ 0x17, 0x00,
+ 0x18, 0x00,
+ 0x19, 0x00,
+ 0x1a, 0x00,
+ 0x1f, 0x50,
+ 0x20, 0x00,
+ 0x21, 0x00,
+ 0x22, 0x00,
+ 0x23, 0x00,
+ 0x28, 0x00, // out imp: normal out type: parallel FEC mode:0
+ 0x29, 0x1e, // 1/2 threshold
+ 0x2a, 0x14, // 2/3 threshold
+ 0x2b, 0x0f, // 3/4 threshold
+ 0x2c, 0x09, // 5/6 threshold
+ 0x2d, 0x05, // 7/8 threshold
+ 0x2e, 0x01,
+ 0x31, 0x1f, // te
Re: [linux-dvb] Anysee E30C Plus (Re: DVB-C developers interested in receiving an USB adapter for hacking?)]
Morjens,
There is now Anysee E30 DVB-T driver with ZL10353 support added, based
information got from Heikki and Risto. I changed also method of
selecting hardware configuration from "board id" to trial and error
method as suggested. Please test and give feedback!
http://linuxtv.org/hg/~anttip/anysee/
It would be nice to add support for Anysee DVB-S devices also...
Regards,
Antti Palosaari
Michael Krufky wrote:
> Antti Palosaari wrote:
>> heips,
>> hmm, now I am a little bit confused because there is this same id as MT352
>> board. Maybe this is not just board id, but some other value that differs
>> from design to design. Could it be firmware version...
>>
>> There is matrix I have now:
>> board id model demodtuner module PCB version
>> 0a 01 00 E30C Plus TDA10023 DTOS403IH102A 507DC (REV 0.2) Timo
>> 02 02 01 E30 ZL10353 ? PCB509T REV 1.61 Heikki
>> 06 01 00 E30 Plus ZL10353 DNOS404ZH103A ?Risto
>> 02 02 01 E30 MT352DNOS4D4ZH102A ?Mika (not sure
>> if 02 02 02 because sniff is from other dev)
>>
>> CI board seems to be same design in both Plus models mentioned: 507_SM
>> BOARD (V1.2).
>>
>> More reports needed.
>
> Antti,
>
> This wouldn't be the first time that a vendor released a device without
> changing the product id, whose earlier revisions used an mt352, and later
> revisions used a zl10353.
>
> I recommend that you handle it in the following way:
>
> static int anysee_zl35x_frontend_attach(struct dvb_usb_adapter *adap)
> {
> /* any device-specific stuff may go here */
>
> if (((adap->fe = dvb_attach(mt352_attach, &anysee_mt352_config,
> &adap->dev->i2c_adap)) != NULL) ||
> ((adap->fe = dvb_attach(zl10353_attach,
> &anysee_zl353_config,
> &adap->dev->i2c_adap)) != NULL))
> return 0;
>
> return -EIO;
> }
>
> The _attach functions of each module tests the id register to ensure that the
> proper demod is actually present -- a few drivers are already doing this,
> such as dvb-usb-cxusb and dvb-bt8xx. I think there are others as well...
>
> HTH,
>
> Mike
--
|||
(0-0)
-oOO--(_)--OOo-
http://palosaari.fi/
-"Kahta asiaa en ymmärrä.. C-kielen syntaksi ja naisten logiikka.."
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Terratec Cinergy T USB XE, Rev. 2?
En/na [EMAIL PROTECTED] ha escrit: > Luca Olivetti says on his page that rev. 2 of the terratec cinergy t usb > xe does not use a af9005, and thus will not work with the af9005 > firmware, of course; so I suspect I got one of these... What driver > should I try next? Well, I don't know if the term "rev.2" is actually correct, I was told that there are two models, one with the af9005 and one without. I don't have any of those, so I cannot say if is there some external identification to tell the difference. Anyway, I don't know the answer to your question :-( Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] stb0899_track: Demodulator LOST LOCK !
Reinhard Nissl wrote: > Hi, > > what does this message mean? > > It appears multiple times per second while watching a channel (not a > specific one) with VDR. > It shouldn't matter. It's a bug. The LOCK LOSS register is valid only in DVB-S2 mode. It's a simple thing, just need to move the read of that LOCK LOSS register into the DVB-S2 delivery system case block. 1935 lock_lost = STB0899_READ_S2REG(STB0899_S2DEMOD, LOCK_LOST); 1936 dprintk(verbose, FE_DEBUG, 1, "Lock Lost=[0x%02x]\n", lock_lost); Will fix that alongwith the not so reliable LOCK 's on the Technisat cards. Not a hindrance though, that being there. Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Tuner not detected on second Kworld card
David Engel wrote: > The minor problem I mentioned earlier has to do with using the > saa7134-alsa module to capture sound directly from the card. A quick > glance at the driver source code looks like it shold support 32 and 48 > kHz sampling rates. I've only been able to get 32 kHz working well so > far with MythTV. Trying 48 kHz results in some sort of rate mismatch. > Is 48 kHz supposed to work? ... > I tried using mplayer with 48 kHz audio and got the same results. > Regardless of the requested audio rate, the cx88-alsa driver or > hardware only supplies 32 kHz audio. The result is audio underruns > and chipmunk audio because the samples that are received are being > played too fast. Can anyone confirm the Kworld card can only do 32 > kHz? I could have sworn I just wrote about this -- email? wiki? But alas, I can't find a thing. In any regard ... Yes, you can only use 32KHz from the tuner with the saa713x. This is a hardware limitation of the chip in regards to handling of SIF sources. For further information, search through the V4L achieves using various "saa7134" or "saa713x" and "32KHz" and "alsa" combinations. There should be plenty of good info. (Example: http://marc.info/?l=linux-video&w=2&r=1&s=32KHz+saa7134&q=b) However, that said, I'm just thinking aloud here about this case, as this actually presents a curious question. Here goes: The NIM on these boards (TUV1236D) contains a TDA9887, which is capable of SIF demodulation, and hence, if utilised, would be feeding the saa713x a baseband audio signal for ADC. Yet, given that in field testing shows the 32KHz limitation, it would seem to indicate that the SIF capability of the TDA9887 is being ignored and that, instead, the broadcast audio is being sent straight to the saa713x for processing (ie. tuner -> saa713x for SIF demod & then ADC). I'm wondering if this is a case of: (1) hard wiring from the TUV1236D module (broadcast audio output) to the saa713x or (2) if there exist alternate pathways/routes in the TUV1236D for the audio signal i.e.: (i) tuner -> TDA9887 for SIF demodulation -> baseband audio to saa713x for ADC (ii) tuner -> saa713x for SIF demod & then ADC If it is a case of 2), then it is obvious that the later route (ii) is being utilized ... and, if it is a case of 2), then the obvious follow up question is: How do you enable the more desirable pathway (i) ? ... i.e. make use of the TDA9887 for SIF demodulation and feed the resultant baseband signal to the saa713x, which, consequently, would allow for the selection of sampling rates other then 32KHz during the ADC phase. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] stb0899_track: Demodulator LOST LOCK !
Hi, what does this message mean? It appears multiple times per second while watching a channel (not a specific one) with VDR. Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:[EMAIL PROTECTED] Oct 14 21:28:19 video kernel: Oct 14 21:28:19 video kernel: stb0899_read_status: Delivery system DVB-S/DSS Oct 14 21:28:19 video kernel: _stb0899_read_reg: Reg=[0xf50d], data=18 Oct 14 21:28:19 video kernel: stb0899_read_status: > FE_HAS_CARRIER | FE_HAS_LOCK Oct 14 21:28:19 video kernel: _stb0899_read_reg: Reg=[0xf58c], data=15 Oct 14 21:28:19 video kernel: stb0899_read_status: > FE_HAS_VITERBI | FE_HAS_SYNC Oct 14 21:28:19 video kernel: stb0899_get_params: Get DVB-S params Oct 14 21:28:19 video kernel: _stb0899_read_s2reg Device=[0xf3fc], Base address=[0x0400], Offset=[0xf370], Data=[0x27272727] Oct 14 21:28:19 video kernel: stb0899_track: Lock Lost=[0x27272727] Oct 14 21:28:19 video kernel: Oct 14 21:28:19 video kernel: stb0899_track: Demodulator LOST LOCK ! Oct 14 21:28:19 video kernel: Oct 14 21:28:19 video kernel: stb0899_read_status: Delivery system DVB-S/DSS Oct 14 21:28:19 video kernel: _stb0899_read_reg: Reg=[0xf50d], data=18 Oct 14 21:28:19 video kernel: stb0899_read_status: > FE_HAS_CARRIER | FE_HAS_LOCK Oct 14 21:28:19 video kernel: _stb0899_read_reg: Reg=[0xf58c], data=15 Oct 14 21:28:19 video kernel: stb0899_read_status: > FE_HAS_VITERBI | FE_HAS_SYNC Oct 14 21:28:19 video kernel: stb0899_read_status: Delivery system DVB-S/DSS Oct 14 21:28:19 video kernel: _stb0899_read_reg: Reg=[0xf50d], data=18 Oct 14 21:28:19 video kernel: stb0899_read_status: > FE_HAS_CARRIER | FE_HAS_LOCK Oct 14 21:28:19 video kernel: _stb0899_read_reg: Reg=[0xf58c], data=15 Oct 14 21:28:19 video kernel: stb0899_read_status: > FE_HAS_VITERBI | FE_HAS_SYNC Oct 14 21:28:19 video kernel: stb0899_get_params: Get DVB-S params Oct 14 21:28:19 video kernel: _stb0899_read_s2reg Device=[0xf3fc], Base address=[0x0400], Offset=[0xf370], Data=[0x27272727] Oct 14 21:28:19 video kernel: stb0899_track: Lock Lost=[0x27272727] Oct 14 21:28:19 video kernel: Oct 14 21:28:19 video kernel: stb0899_track: Demodulator LOST LOCK ! Oct 14 21:28:19 video kernel: Oct 14 21:28:19 video kernel: stb0899_read_status: Delivery system DVB-S/DSS Oct 14 21:28:19 video kernel: _stb0899_read_reg: Reg=[0xf50d], data=18 Oct 14 21:28:19 video kernel: stb0899_read_status: > FE_HAS_CARRIER | FE_HAS_LOCK Oct 14 21:28:19 video kernel: _stb0899_read_reg: Reg=[0xf58c], data=15 Oct 14 21:28:19 video kernel: stb0899_read_status: > FE_HAS_VITERBI | FE_HAS_SYNC Oct 14 21:28:19 video kernel: stb0899_get_params: Get DVB-S params Oct 14 21:28:19 video kernel: _stb0899_read_s2reg Device=[0xf3fc], Base address=[0x0400], Offset=[0xf370], Data=[0x27272727] Oct 14 21:28:19 video kernel: stb0899_track: Lock Lost=[0x27272727] Oct 14 21:28:19 video kernel: Oct 14 21:28:19 video kernel: stb0899_track: Demodulator LOST LOCK ! Oct 14 21:28:19 video kernel: Oct 14 21:28:19 video kernel: stb0899_read_status: Delivery system DVB-S/DSS Oct 14 21:28:19 video kernel: _stb0899_read_reg: Reg=[0xf50d], data=18 Oct 14 21:28:19 video kernel: stb0899_read_status: > FE_HAS_CARRIER | FE_HAS_LOCK Oct 14 21:28:19 video kernel: _stb0899_read_reg: Reg=[0xf58c], data=15 Oct 14 21:28:19 video kernel: stb0899_read_status: > FE_HAS_VITERBI | FE_HAS_SYNC Oct 14 21:28:19 video kernel: stb0899_get_params: Get DVB-S params Oct 14 21:28:19 video kernel: _stb0899_read_s2reg Device=[0xf3fc], Base address=[0x0400], Offset=[0xf370], Data=[0x27272727] Oct 14 21:28:19 video kernel: stb0899_track: Lock Lost=[0x27272727] Oct 14 21:28:19 video kernel: Oct 14 21:28:19 video kernel: stb0899_track: Demodulator LOST LOCK ! Oct 14 21:28:19 video kernel: Oct 14 21:28:19 video kernel: stb0899_read_status: Delivery system DVB-S/DSS Oct 14 21:28:19 video kernel: _stb0899_read_reg: Reg=[0xf50d], data=18 Oct 14 21:28:19 video kernel: stb0899_read_status: > FE_HAS_CARRIER | FE_HAS_LOCK Oct 14 21:28:19 video kernel: _stb0899_read_reg: Reg=[0xf58c], data=15 Oct 14 21:28:19 video kernel: stb0899_read_status: > FE_HAS_VITERBI | FE_HAS_SYNC Oct 14 21:28:19 video kernel: stb0899_get_params: Get DVB-S params Oct 14 21:28:19 video kernel: _stb0899_read_s2reg Device=[0xf3fc], Base address=[0x0400], Offset=[0xf370], Data=[0x27272727] Oct 14 21:28:19 video kernel: stb0899_track: Lock Lost=[0x27272727] Oct 14 21:28:19 video kernel: Oct 14 21:28:19 video kernel: stb0899_track: Demodulator LOST LOCK ! Oct 14 21:28:19 video kernel: Oct 14 21:28:19 video kernel: stb0899_read_status: Delivery system DVB-S/DSS Oct 14 21:28:19 video kernel: _stb0899_read_reg: Reg=[0xf50d], data=18 Oct 14 21:28:19 video kernel: stb0899_read_status: > FE_HAS_CARRIER | FE_HAS_LOCK Oct 14 21:28:19 video kernel: _stb0899_read_reg: Reg=[0xf58c], data=15 Oct 14 21:28:19 video kernel: stb0899_read_status: > FE_HAS_VITERBI
Re: [linux-dvb] mantis branch on jusst.de - vp1034 can't tune to vertical channels
Gernot Pansy wrote: > thank you, the patch is working for me. > > the time from starting initalizaiton until i get a lock is about ~400msec. In the ideal case according to the vendor, it should have been 300 - 350 mS max. But i guess 50 - 100mS deviation is peanuts compared to most other demods. Well, looks quite ok. Also would like to know how much time it takes to LOCK on Low symbol rates. Manu > > notz > > On Sunday 14 October 2007 19:18:18 Manu Abraham wrote: >> Gernot Pansy wrote: >>> hy, >>> >>> i got trough warranty issues for my old vp1030 a new vp1034. i tried this >>> card now with this branch but the card can only tune to vertical channels >>> (horizontal are working in less than a second). >> Uh. I forgot the GPIO bit flip from Marco, will apply it later, but to get >> you going at the earliest Michel Verbraak has a cached copy, it should >> apply cleanly still. You should be going ahead quite fine. >> >> http://www.verbraak.org/mantis_gpio_set_bits_fix.patch >> >> After the same, can you pleas clock the LOCK 'ing time please ? I am >> currently checking how much deviation i am having from the actual device >> specifications in terms of LOCK 'ing time. >> >> Thanks for reporting. >> >> Manu > > > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] mantis branch on jusst.de - vp1034 can't tune to vertical channels
thank you, the patch is working for me. the time from starting initalizaiton until i get a lock is about ~400msec. notz On Sunday 14 October 2007 19:18:18 Manu Abraham wrote: > Gernot Pansy wrote: > > hy, > > > > i got trough warranty issues for my old vp1030 a new vp1034. i tried this > > card now with this branch but the card can only tune to vertical channels > > (horizontal are working in less than a second). > > Uh. I forgot the GPIO bit flip from Marco, will apply it later, but to get > you going at the earliest Michel Verbraak has a cached copy, it should > apply cleanly still. You should be going ahead quite fine. > > http://www.verbraak.org/mantis_gpio_set_bits_fix.patch > > After the same, can you pleas clock the LOCK 'ing time please ? I am > currently checking how much deviation i am having from the actual device > specifications in terms of LOCK 'ing time. > > Thanks for reporting. > > Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Terratec Cinergy T USB XE, Rev. 2?
Hi Manu! Thanks for your reply! > > I opened the device and the two most prominent chips read: > > > > TERRATEC > > CUCME > > S260274K > > CINERGY > > > > TERRATEC > > U2TV-23x > > 0734573a > > CINERGY > > > > The USB ID is 0ccd:0069. Any chance that this device will be > supported?> Or should I try to return it to the store? > > Are you sure that the USB id's are the same that you have mentioned > ? If it > is so, the chips have been reprinted by Terratec. Do you have a > picture of > the device, in the dismantled state ? I uploaded some pictures here: http://fluchthelfer.com/terratec-cinergy-t-usb-xe/front.jpg http://fluchthelfer.com/terratec-cinergy-t-usb-xe/back.jpg Luca Olivetti says on his page that rev. 2 of the terratec cinergy t usb xe does not use a af9005, and thus will not work with the af9005 firmware, of course; so I suspect I got one of these... What driver should I try next? Regards, Anselm ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Important note to em28xx/xc3028 users
Aidan Thornton wrote: > Hi, > > Unfortunately, Markus has pulled offline all his repositories > containing Linux drivers. (You can see > http://kerneltrap.org/mailarchive/linux-kernel/2007/10/14/337446 for > the reason). This mainly affects users of em28xx-based and > xc3028-based devices. I suggest those of you with local copies make > sure you keep them backed up; you may not be able to get another copy. :-( missed the boat ... > > Users of em28xx-based devices can use my > http://www.makomk.com/hg/v4l-dvb-makomk repository, which is still > maintained and should remain so for as long as necessary. In theory, > it should support all the em28xx-based devices that Markus' > v4l-dvb-experimental driver does, but it hasn't been tested with > anything other than the device I use (and one obscure device not > supported by Markus' driver). Please can someone with write access update the wiki, esp. at http://mcentral.de/wiki/index.php/AVerMedia_AverTV_Hybrid_FM_PCI_A16D - I just went to get this code but of course hg fails: > $ hg clone http://mcentral.de/hg/~mrec/v4l-dvb-experimental/ > abort: 'http://mcentral.de/hg/~mrec/v4l-dvb-experimental/' does not appear to > be an hg repository! I will try again with your repository & hope it includes the A16D patch? > > Users of other devices supported by Markus' drivers are currently > stuck. If this continues, I may see what I can do about it myself, > though I can't promise anything. There may also be other developers > who are willing to work on the code. I wish my coding skills were up to it. -- Cheers, Richard (MQ) ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Common interface on Technotrend S-1500 broken in v4l-dvb?
Oliver Endriss wrote:
> P. van Gaans wrote:
> > On 10/14/2007 12:11 AM, Oliver Endriss wrote:
> > > P. van Gaans wrote:
> > >> Today I was testing some stuff and downloaded and installed the newest
> > >> v4l-dvb from hg. After a while I figured out that FTA channels on my TT
> > >> S-1500 still worked, but the CAM would not respond. I checked all
> > >> connections, re-inserted the CAM, reboot the computer but nothing would
> > >> help. My CI daughterboard version is 1.1 and I bought this S-1500 end of
> > >> august 2007. I use Ubuntu 7.04 with kernel 2.6.20-16-generic.
> > >>
> > >> After installing a somewhat older version of v4l-dvb I luckily had left
> > >> on my harddisk, the common interface directly came back to life.
> > >
> > > Could you please try to find out which changeset broke the code?
> > >
> > > If you have a current HG checkout, you can update the driver to a given
> > > version using 'hg update '.
> > >
> > >> Maybe I just did something wrong somewhere, but would it be possible
> > >> some big change was made to the way the S-1500 handles the CI that could
> > >> have broken it?
> > >
> > > It's probably a change in budget-ci.c or dvb_ca_en50221.c
> > >
> > > Just an educated guess:
> > > Did http://linuxtv.org/hg/v4l-dvb/rev/b0a3a9b43d60
> > > break the code? -> 'hg update 6279'
> > >
> > > CU
> > > Oliver
> > >
> >
> > 6279 does not compile.
> >
> > make -C /home/wn/v4l-dvb/v4l
> > make[1]: Entering directory `/home/wn/v4l-dvb/v4l'
> > perl scripts/make_config_compat.pl /lib/modules/2.6.20-16-generic/source
> > ./.myconfig ./config-compat.h
> > File not found:
> > /lib/modules/2.6.20-16-generic/source/include/linux/netdevice.h at
> > scripts/make_config_compat.pl line 15.
> > make[1]: *** [config-compat.h] Error 2
> > make[1]: Leaving directory `/home/wn/v4l-dvb/v4l'
> > make: *** [all] Error 2
> >
> > After trying a bit I figured out 6266 does compile. Everything between
> > 6279 and 6266 does not. I can tell you that with 6266, the common
> > interface works, I hope that's enough info.
>
> Now I have a confirmation from Marco Schluessler that changeset
> http://linuxtv.org/hg/v4l-dvb/raw-rev/b0a3a9b43d60
> broke CI support.
>
> For now simply revert this changeset.
> Save http://linuxtv.org/hg/v4l-dvb/raw-rev/b0a3a9b43d60 to a file.
> Then use 'patch -p1 -R < file' to revert the changeset.
Marco sent me the attached patch which should fix the problem.
Please test.
CU
Oliver
--
VDR Remote Plugin 0.4.0: http://www.escape-edv.de/endriss/vdr/
- "while (!ca->wakeup)" breaks the CAM initialisation
Signed-off-by: Marco Schluessler <[EMAIL PROTECTED]>
diff -bur v4l-dvb-ea93c93f1547_orig/linux/drivers/media/dvb/dvb-core/dvb_ca_en50221.c v4l-dvb-ea93c93f1547/linux/drivers/media/dvb/dvb-core/dvb_ca_en50221.c
--- v4l-dvb-ea93c93f1547_orig/linux/drivers/media/dvb/dvb-core/dvb_ca_en50221.c 2007-10-14 13:19:25.0 +0200
+++ v4l-dvb-ea93c93f1547/linux/drivers/media/dvb/dvb-core/dvb_ca_en50221.c 2007-10-14 18:37:15.0 +0200
@@ -973,7 +973,7 @@
/* main loop */
while (!kthread_should_stop()) {
/* sleep for a bit */
- while (!ca->wakeup) {
+ if (!ca->wakeup) {
set_current_state(TASK_INTERRUPTIBLE);
schedule_timeout(ca->delay);
if (kthread_should_stop())
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Future of Multiproto
Oliver Endriss wrote: > Manu Abraham wrote: >> Oliver Endriss wrote: >>> @all, >>> I suggest the following: >>> >>> 1a Review the API extensions (dvb_frontend.h). >>> 1b Commit them. >>> >>> 2a Review dvb_core modifications. >>> 2b Commit them. >>> >>> 3 Commit drivers when they are ready for inclusion. >>> >> Will appreciate if you will do a review on this tree. >> >> http://jusst.de/hg/multiproto/ >> >> The tree is not very clean though, with regards to CodingStyle etc. >> If it looks fine, i will do the cleanups. > > I'll try to find some time this week. > Thanks Regards, Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Future of Multiproto
Manu Abraham wrote: > Oliver Endriss wrote: > > @all, > > I suggest the following: > > > > 1a Review the API extensions (dvb_frontend.h). > > 1b Commit them. > > > > 2a Review dvb_core modifications. > > 2b Commit them. > > > > 3 Commit drivers when they are ready for inclusion. > > > > Will appreciate if you will do a review on this tree. > > http://jusst.de/hg/multiproto/ > > The tree is not very clean though, with regards to CodingStyle etc. > If it looks fine, i will do the cleanups. I'll try to find some time this week. CU Oliver -- VDR Remote Plugin 0.4.0: http://www.escape-edv.de/endriss/vdr/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] random memory corruptions with asus p7131 (Re: asus p7131 vs ZDF?)
Soeren Sonnenburg wrote: > On Fri, 2007-10-12 at 02:24 +0200, Oliver Endriss wrote: > > Soeren Sonnenburg wrote: > > > I am unfortunately 100% sure that it is caused by the saa7146 driver, as > > > I have an uptime of over a week now that it is not loaded (but the card > > > is still in the slot, yeah and I did memory tests for 18 passes - > > > nothing). > > > > Could you please try the patch posted in > > http://linuxtv.org/pipermail/linux-dvb/2007-October/021042.html > > > > and report whether it fixes your problem? > > Hmmhh, reading what it changes > > "Two fixes for the 'saa7146_wait_for_debi_done' code: > (a) Timeout did not work when the routine was called with interrupts > disabled. > (b) Reduce PCI I/O load caused by saa7146_wait_for_debi_done. > Seems to be very important on fast machines!" > > I am not sure why this could fix the problems I am seeing. I can give it > a try if you are quite confident that it could help High load on the PCI bus might trigger a bug somewhere else. Btw, I'm not aware of any reports that the saa7146 driver caused memory corruption or something like that. > , but I get > > - gcc compile failures > - filesystem corruptions > - database corruptions Hm. Very often these symptoms are caused by broken hardware. > when the card's driver is loaded and is in use for a few days (and then > finally a hang/crash+reboot). I have the *feeling* that the situation > improved slightly by improving reception via F-connectors, so I thing > there is some kind of buffer overflow or so occurring... > > Anyway thanks for your work, I will happily try it if you think it may > fix this problem. I would try. ;-) CU Oliver -- VDR Remote Plugin 0.4.0: http://www.escape-edv.de/endriss/vdr/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] mantis branch on jusst.de - vp1034 can't tune to vertical channels
Gernot Pansy wrote: > hy, > > i got trough warranty issues for my old vp1030 a new vp1034. i tried this > card > now with this branch but the card can only tune to vertical channels > (horizontal are working in less than a second). Uh. I forgot the GPIO bit flip from Marco, will apply it later, but to get you going at the earliest Michel Verbraak has a cached copy, it should apply cleanly still. You should be going ahead quite fine. http://www.verbraak.org/mantis_gpio_set_bits_fix.patch After the same, can you pleas clock the LOCK 'ing time please ? I am currently checking how much deviation i am having from the actual device specifications in terms of LOCK 'ing time. Thanks for reporting. Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Technotrend DVB-T 1200 rev 1.2 does not tune/work
Soeren Sonnenburg wrote: > On Sun, 2007-10-14 at 16:03 +0200, Oliver Endriss wrote: > > Soeren Sonnenburg wrote: > > > On Sat, 2007-10-13 at 23:52 +0200, Oliver Endriss wrote: > > > > Soeren Sonnenburg wrote: > > > > > Dear all, > > > > > [...] > > > > Did this card ever work before? > > > > > > I just purchased it, so I cannot tell whether it ever worked with linux. > > > However the guy from whom I got the card claimed that it works w/ > > > windows. > > > > Please try it with windows. Then we will know whether it is ok or not. > > The problem is that I do not easily have access to a windows machine. Is > there anything I can do to test whether it is OK without windows? > > ... > > I mean the problem is, that the frontend registers and loads the sp8870 > firmware, but I have no idea whether that is the right one or not (it > does not want the grundig frontend however)... Afaik there are only those two frontends for DVB-T FF cards. > When I scan it does not find any channel and using a channel list > obtained via a budget tt card, it still does not want to tune to any > channel there... > > Any ideas? I mean not that because the card is considered dvb-s some > potentially wrong dvb-s settings are set somewhere?! Afaics you did everything which could be done. The frontend was detected. Basically the card should work. (I assume that there are no tuning-related error messages in the log.) Next you have to find out whether the card is broken or not. >From your results I guess something is broken, but you can only be sure if you test it with the windows driver. (There is a small chance that it is a card variant which is not supported yet.) CU Oliver -- VDR Remote Plugin 0.4.0: http://www.escape-edv.de/endriss/vdr/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] mantis branch on jusst.de - vp1034 can't tune to vertical channels
hy, i got trough warranty issues for my old vp1030 a new vp1034. i tried this card now with this branch but the card can only tune to vertical channels (horizontal are working in less than a second). zapping to 5 'Pro7': sat 0, frequency = 12051 MHz V, symbolrate 2750, vpid = 0x00a1, apid = 0x0054 using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' status 00 | signal ff95 | snr ff03 | ber 014a | unc 00ff | status 01 | signal ff96 | snr ff02 | ber 012a | unc 0002 | status 01 | signal ff95 | snr ff02 | ber 0155 | unc | status 01 | signal ff97 | snr ff02 | ber 00fa | unc 0001 | status 01 | signal ff95 | snr ff02 | ber 0119 | unc | status 01 | signal ff96 | snr ff02 | ber 014b | unc 0002 | status 01 | signal ff95 | snr ff02 | ber 00fd | unc 00ff | status 01 | signal ff96 | snr ff02 | ber 0111 | unc 0001 | attached is my dmesg output. in the same situation the vp1041 has no troubles to tune. notz dmesg.txt.gz Description: GNU Zip compressed data ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Future of Multiproto
Oliver Endriss wrote: > Marcel Siegert wrote: >> can everybody _please_ stop this unnessessary discussion? > > Full ack! I'm really tired reading these garbage threads. > > @all, > I suggest the following: > > 1a Review the API extensions (dvb_frontend.h). > 1b Commit them. > > 2a Review dvb_core modifications. > 2b Commit them. > > 3 Commit drivers when they are ready for inclusion. > Will appreciate if you will do a review on this tree. http://jusst.de/hg/multiproto/ The tree is not very clean though, with regards to CodingStyle etc. If it looks fine, i will do the cleanups. Regards, Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Terratec Cinergy T USB XE, Rev. 2?
[EMAIL PROTECTED] wrote: > Hello List! > > I just bought a Terratec Cinergy T USB XE, in good faith it would be > supported under Linux. Alas, the af9005 driver would not recognize it, > and bravely changing the USB ID in dvb-usb-ids.h didn't help, I got this > instead: > > af9005: boot bad config header. > dvb_usb_af9005: probe of 2-5:1.0 failed with error -5 > > Now I suppose I have a "Rev. 2"-device, if I understand correctly what > is said on > > http://ventoso.org/luca/af9005/ > > I opened the device and the two most prominent chips read: > > TERRATEC > CUCME > S260274K > CINERGY > > TERRATEC > U2TV-23x > 0734573a > CINERGY > > The USB ID is 0ccd:0069. Any chance that this device will be supported? > Or should I try to return it to the store? Are you sure that the USB id's are the same that you have mentioned ? If it is so, the chips have been reprinted by Terratec. Do you have a picture of the device, in the dismantled state ? Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Strage SkyStar HD modprobe
Artem Makhutov wrote: > Hi, > > On Fri, Oct 12, 2007 at 06:24:05PM +0400, Manu Abraham wrote: >> Hi, >> >> Reinhard Nissl wrote: >>> Hi, >>> >>> Manu Abraham wrote: >>> >> this Logfile looks a bit strange, and I can't tune to DVB-S2 channels. >> DVB-S works fine. >> I really have the feeling that this card is demaged > I experience a similar behaviour. There are days (like to today) when I > have to completely power off my machine to get the card working. > Sometimes tuning DVB-S channels works, but DVB-S2 doesn't work. After a > power off, it most likely works. Today I had to power off the machine > for more than one times. That's really strange. >> >> Can you please check whether pin 18 of the stb0899 on your card is at GND >> level ? >> You can check the continuity with a meter. > > Pin 18 is connected to GND. > PLL not bypassed either .. argh! .. Give me a little while, need to think. Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DVB-S2 Multiple logical TS on the same frequency
Francesco Schiavarelli wrote: > I own a TT-3200 and I'm interested in receiving those kind of signal. > I understand that ATM is not possbile, but will it be in the future? > In other words it's an hardware or software/firmware limitation? > STB0899, STV090x, SkyPhy (Viasat's demod, iirc) based can do MTS. (The ones that i know) But the current limitation i wrote in the previous post comes from the demuxer (API implementation) and some others. I heard from 2 sources, that there is some momentum for MTS, I would like to know, based on what criteria your question originated. Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DVB-S2 Multiple logical TS on the same frequency
Nico Sabbi wrote: > Il Sunday 14 October 2007 17:06:38 Francesco Schiavarelli ha scritto: >> I own a TT-3200 and I'm interested in receiving those kind of >> signal. I understand that ATM is not possbile, but will it be in >> the future? In other words it's an hardware or software/firmware >> limitation? >> >> thanks, >> Francesco >> > > aren't they transmitted on the two hyerarchical streams (that have > been supported for years now) ? Nope. DVB-S2 is a bit complex, additional to all that it carries the overhead of backward compatibility. The specification is more like the EN50221 specification, where you need to read it over and over again many times, in conjunction to an actual device specification. That said: 1) Hierarchial modulation is used only for one of the backward compatibility methods. Here there is a HP/LP stream. Ref: EN302 307 v 1.1.2 Appendix F Page 55 2) This has nothing to do with MTS aka Multiple Transport Streams. This is in fact to simply state is: SIS (Single Input Stream) /MIS (Multiple Input Streams) according to the ETSI specifications Ref: EN302 307 v 1.1.2 Page 49 Not all demodulators are capable of doing this (1) and (2) 1) is not a big concern, but 2) might be when broadcasters do MTS similarly to the DVB-T HP/LP streams. (stated as an example, this has nothing to do with Hierarchial modulation HP/LP itself, in fact) You can have MIS in 2 cases again: 1) Transport Streams a) When it is SIS, it is similar to our normal DVB-S transmissions b) When it is flagged MIS in the Baseband Header, we have Multiple Streams. When it is MIS, if the logical streams are scrambled, we will need to route the relevant stream to the CA module, which means we have some additional job at the demuxer level. (this will be a bit of headache, coupled with a CA device) 2) Generic Streams (note this need not be a MPEG2 stream at all) This at least we can pipe everything to userspace at least as a last resort. Temporarily, we do not need to worry about Generic streams (Single or Multiple), since they aren't basically used in the broadcast profiles, _but_ MTS might be. Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] random memory corruptions with asus p7131 (Re: asus p7131 vs ZDF?)
On Fri, 2007-10-12 at 02:49 +0200, hermann pitton wrote: > Hi, > > Am Freitag, den 12.10.2007, 02:24 +0200 schrieb Oliver Endriss: > > Soeren Sonnenburg wrote: > > > I am unfortunately 100% sure that it is caused by the saa7146 driver, as > > > I have an uptime of over a week now that it is not loaded (but the card > > > is still in the slot, yeah and I did memory tests for 18 passes - > > > nothing). > > > > Could you please try the patch posted in > > http://linuxtv.org/pipermail/linux-dvb/2007-October/021042.html > > > > and report whether it fixes your problem? > > > > CU > > Oliver > > > > Mauro also discovered a problem with SMP machines and the saa7134 driver > i did never hit on UP stuff. > > Soeren, in case of dual processors or hyperthreading you might try what > Mauro used to come around it, not sure if it is in latest v4l-dvb. The problem is, that this is a rather old UP machine machine, no fancy dual/quad core nor anything special at all... Soeren ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] random memory corruptions with asus p7131 (Re: asus p7131 vs ZDF?)
On Fri, 2007-10-12 at 02:24 +0200, Oliver Endriss wrote: > Soeren Sonnenburg wrote: > > I am unfortunately 100% sure that it is caused by the saa7146 driver, as > > I have an uptime of over a week now that it is not loaded (but the card > > is still in the slot, yeah and I did memory tests for 18 passes - > > nothing). > > Could you please try the patch posted in > http://linuxtv.org/pipermail/linux-dvb/2007-October/021042.html > > and report whether it fixes your problem? Hmmhh, reading what it changes "Two fixes for the 'saa7146_wait_for_debi_done' code: (a) Timeout did not work when the routine was called with interrupts disabled. (b) Reduce PCI I/O load caused by saa7146_wait_for_debi_done. Seems to be very important on fast machines!" I am not sure why this could fix the problems I am seeing. I can give it a try if you are quite confident that it could help, but I get - gcc compile failures - filesystem corruptions - database corruptions when the card's driver is loaded and is in use for a few days (and then finally a hang/crash+reboot). I have the *feeling* that the situation improved slightly by improving reception via F-connectors, so I thing there is some kind of buffer overflow or so occurring... Anyway thanks for your work, I will happily try it if you think it may fix this problem. Best, Soeren ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Streams recognized by dvbnet
Michael Harpe schrieb: > I have been working on debugging reception of a datacast for a while now. > > I have determined that the data I am interested in is in PID 0x1af3. Here's > what I get from a dvbsnoop pidscan... > > [...] > > The section ID is 0x3F (decimal 63) and as you can see it's ISO/IEC 13818-6 > reserved. The data is mostly ASCII text files and I can see them clearly in > dvbsnoop dumps. The data is IP/UDP data. > > Is this why I get no packets from dvbnet? > > Hello Michael! This section ID refers to so-called "DSM-CC Addressable Sections", which are used in ATSC systems for carrying (asynchronous) datagrams such as IP. Essentially, the section format is the same as in Multiprotocol Encapsulation (MPE) commonly used for IP-over-DVB, and implemented by dvbnet. However, MPE datagram sections have a table id of 0x3e, and the MPE dvbnet implementation filters on that (among other things), which means that it will (silently) discard other DSM-CC sections, like the one mentioned above. So without patching the code, you won't be able to receive the network traffic with dvbnet. Cheers, Christian. -- Christian Praehauser <[EMAIL PROTECTED]> || //\\//\\ || Multimedia Communications Group, ||// \/ \\|| Department of Computer Sciences, University of Salzburg http://student.cosy.sbg.ac.at/~cpraehaus/ http://www.network-research.org/ http://www.uni-salzburg.at/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DVB-S2 Multiple logical TS on the same frequency
Nico Sabbi wrote: > Il Sunday 14 October 2007 17:06:38 Francesco Schiavarelli ha scritto: >> I own a TT-3200 and I'm interested in receiving those kind of >> signal. I understand that ATM is not possbile, but will it be in >> the future? In other words it's an hardware or software/firmware >> limitation? >> >> thanks, >> Francesco >> > > aren't they transmitted on the two hyerarchical streams (that have > been supported for years now) ? No it's not hyerarchical modulation, it's a DVB-S2 specific feature. You can have on the same transponder two different transport streams with the same channel protection. I don't know how is called by the ETSI standard, though. Francesco ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Technotrend DVB-T 1200 rev 1.2 does not tune/work
On Sun, 2007-10-14 at 16:03 +0200, Oliver Endriss wrote: > Soeren Sonnenburg wrote: > > On Sat, 2007-10-13 at 23:52 +0200, Oliver Endriss wrote: > > > Soeren Sonnenburg wrote: > > > > Dear all, > > > > [...] > > > Did this card ever work before? > > > > I just purchased it, so I cannot tell whether it ever worked with linux. > > However the guy from whom I got the card claimed that it works w/ > > windows. > > Please try it with windows. Then we will know whether it is ok or not. The problem is that I do not easily have access to a windows machine. Is there anything I can do to test whether it is OK without windows? [...] > > Yes, but VHF is only 30 MHz to 300 MHz and according to > > http://www.telesat-info.de/sat/dvbt/dvbthome.html > > this affects only channel 5 & 7 (FAB/arte). > > > > So it should not be a problem to tune to 'Das Erste' or so > > True. I mean the problem is, that the frontend registers and loads the sp8870 firmware, but I have no idea whether that is the right one or not (it does not want the grundig frontend however)... When I scan it does not find any channel and using a channel list obtained via a budget tt card, it still does not want to tune to any channel there... Any ideas? I mean not that because the card is considered dvb-s some potentially wrong dvb-s settings are set somewhere?! Soeren ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Tuner not detected on second Kworld card
On Thu, Oct 11, 2007 at 01:46:32PM -0500, David Engel wrote: > Notice the absence of an equivalent "tuner 1-0061: chip found" line > for saa7133[1]. This occurs with both the 2.6.21 and 2.6.22.* > kernels. I briefly tested analog and digital capture on both cards in > a separate system before installing them in the MythTV backend so I > don't suspect a hardware problem. > > Not being able to tune could explain not being able to to an analog > capture. Could this be another case of probing being done by the > various drivers causing problems? If so, has any of it been fixed in > the recently released 2.6.23 kernel? I've already had to go back to > the 2.6.21 series on this system because the probing caused a minor > problem with the Hauppauge cards. I tried moving the Kworld ATSC 115 cards around and also removing one at a time to see what would happen. I confirmed the tuner could be detected on each Kworld card in some configurations so I don't think it's a hardware problem with the Kworld cards themselves. I also found a case where the tuner on a Kworld card would only be detected if I blacklisted the ivtv driver to make the system ignore the Hauppauge cards. Both Kworld cards are now in slots where the tuner was detected individually in one form or another, but the driver still won't detect the tuner on both Kworld cards. It always only detects the first one. While I can't completely rule out a motherboard or BIOS problem, it does look like a probing/detection problem with the cx88 and/or ivtv drivers. Are any of the fixes for that in the 2.6.23 kernel yet? > The minor problem I mentioned earlier has to do with using the > saa7134-alsa module to capture sound directly from the card. A quick > glance at the driver source code looks like it shold support 32 and 48 > kHz sampling rates. I've only been able to get 32 kHz working well so > far with MythTV. Trying 48 kHz results in some sort of rate mismatch. > Is 48 kHz supposed to work? I tried using mplayer with 48 kHz audio and got the same results. Regardless of the requested audio rate, the cx88-alsa driver or hardware only supplies 32 kHz audio. The result is audio underruns and chipmunk audio because the samples that are received are being played too fast. Can anyone confirm the Kworld card can only do 32 kHz? David -- David Engel [EMAIL PROTECTED] ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DVB-S2 Multiple logical TS on the same frequency
Il Sunday 14 October 2007 17:06:38 Francesco Schiavarelli ha scritto: > I own a TT-3200 and I'm interested in receiving those kind of > signal. I understand that ATM is not possbile, but will it be in > the future? In other words it's an hardware or software/firmware > limitation? > > thanks, > Francesco > aren't they transmitted on the two hyerarchical streams (that have been supported for years now) ? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] DVB-S2 Multiple logical TS on the same frequency
I own a TT-3200 and I'm interested in receiving those kind of signal. I understand that ATM is not possbile, but will it be in the future? In other words it's an hardware or software/firmware limitation? thanks, Francesco ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Compiling is broken for kernel 2.6.18
Hi,
changset 6293 (V4L: convert struct class_device to struct device) breaks
compiling for kernel 2.6.18.
--- a/linux/drivers/media/video/pvrusb2/pvrusb2-sysfs.c Mon Oct 08 12:20:02
2007 -0300
+++ b/linux/drivers/media/video/pvrusb2/pvrusb2-sysfs.c Mon Oct 08 16:26:13
2007 -0300
...
@@ -903,11 +919,15 @@ struct pvr2_sysfs_class *pvr2_sysfs_clas
pvr2_sysfs_trace("Creating pvr2_sysfs_class id=%p",clp);
clp->class.name = "pvrusb2";
clp->class.class_release = pvr2_sysfs_class_release;
+#if LINUX_VERSION_CODE < KERNEL_VERSION(2,6,13)
clp->class.release = pvr2_sysfs_release;
+#else
+ clp->class.dev_release = pvr2_sysfs_release;
+#endif
#if LINUX_VERSION_CODE < KERNEL_VERSION(2,6,16)
clp->class.hotplug = pvr2_sysfs_hotplug;
#else
- clp->class.uevent = pvr2_sysfs_hotplug;
+ clp->class.dev_uevent = pvr2_sysfs_hotplug;
#endif
if (class_register(&clp->class)) {
pvr2_sysfs_trace(
...
In kernel 2.6.18, the structure 'class' doesn't contain a member 'dev_release'
or 'dev_uevent'.
Possible kernel 2.6.13 to 2.6.19 are affected from this problem.
- Hartmut
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] UDP encapsulated MPEG{2,4} TS into dvbsnoop?
Alexander E. Patrakov wrote: > Local news sites mention that > DVB-H is being tested, but these packets don't look like DVB-H payload, > because they are IPv4. > DVB-H can be with IPv4. In Italy we have three different DVB-H providers, each is using IPv4. Francesco ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Common interface on Technotrend S-1500 broken in v4l-dvb?
P. van Gaans wrote: > On 10/14/2007 12:11 AM, Oliver Endriss wrote: > > P. van Gaans wrote: > >> Today I was testing some stuff and downloaded and installed the newest > >> v4l-dvb from hg. After a while I figured out that FTA channels on my TT > >> S-1500 still worked, but the CAM would not respond. I checked all > >> connections, re-inserted the CAM, reboot the computer but nothing would > >> help. My CI daughterboard version is 1.1 and I bought this S-1500 end of > >> august 2007. I use Ubuntu 7.04 with kernel 2.6.20-16-generic. > >> > >> After installing a somewhat older version of v4l-dvb I luckily had left > >> on my harddisk, the common interface directly came back to life. > > > > Could you please try to find out which changeset broke the code? > > > > If you have a current HG checkout, you can update the driver to a given > > version using 'hg update '. > > > >> Maybe I just did something wrong somewhere, but would it be possible > >> some big change was made to the way the S-1500 handles the CI that could > >> have broken it? > > > > It's probably a change in budget-ci.c or dvb_ca_en50221.c > > > > Just an educated guess: > > Did http://linuxtv.org/hg/v4l-dvb/rev/b0a3a9b43d60 > > break the code? -> 'hg update 6279' > > > > CU > > Oliver > > > > 6279 does not compile. > > make -C /home/wn/v4l-dvb/v4l > make[1]: Entering directory `/home/wn/v4l-dvb/v4l' > perl scripts/make_config_compat.pl /lib/modules/2.6.20-16-generic/source > ./.myconfig ./config-compat.h > File not found: > /lib/modules/2.6.20-16-generic/source/include/linux/netdevice.h at > scripts/make_config_compat.pl line 15. > make[1]: *** [config-compat.h] Error 2 > make[1]: Leaving directory `/home/wn/v4l-dvb/v4l' > make: *** [all] Error 2 > > After trying a bit I figured out 6266 does compile. Everything between > 6279 and 6266 does not. I can tell you that with 6266, the common > interface works, I hope that's enough info. Now I have a confirmation from Marco Schluessler that changeset http://linuxtv.org/hg/v4l-dvb/raw-rev/b0a3a9b43d60 broke CI support. For now simply revert this changeset. Save http://linuxtv.org/hg/v4l-dvb/raw-rev/b0a3a9b43d60 to a file. Then use 'patch -p1 -R < file' to revert the changeset. @Mauro, Has this changeset ever been tested? CU Oliver -- VDR Remote Plugin 0.4.0: http://www.escape-edv.de/endriss/vdr/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] TT-2300 with IR on CI - not work??
Simon Baxter wrote: > >> It always registers, no matter whether there is an ir receiver or not. > > > > oh, ok! > > > >>> ...and I've added the little jumper on the CI - but it won't work. > >>> > >>> I do a 'tail -f /dev/input/event3' and get nothing when pointing the > >>> remote > >>> at it. > >> > >> This will only work if you have loaded a keymap. > > > > This isn't something I've done before - always used serial homebrew and > > LIRC > > OK - works. Thanks. > > Some buttons dont work - will work on this If you use the remote plugin, let the plugin load its built-in keymap. Then you don't have to bother about keymaps. For details have a look into the plugin docs. CU Oliver -- VDR Remote Plugin 0.4.0: http://www.escape-edv.de/endriss/vdr/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Technotrend DVB-T 1200 rev 1.2 does not tune/work
Soeren Sonnenburg wrote: > On Sat, 2007-10-13 at 23:52 +0200, Oliver Endriss wrote: > > Soeren Sonnenburg wrote: > > > Dear all, > > > > > > I am having problems with a full featured TT-1200 dvb-t (sometimes also > > > called technotrend dvb-t premium) card. > > > > > > It does not find the frontend and if I manually fiddle with the code (I > > > simply had to remove the break in line 2176 of av7110.c in hg to allow > > > > There is no 'break' on line 2176, should be 2167. (?) > > yes, sorry. > > > > fallthrough) to make it load the Spase SP8870 DVB-T it successfully > > > registers this frontend and loads the sp8870 firmware but then it still > > > refuses to tune to any channel... > > > > Did this card ever work before? > > I just purchased it, so I cannot tell whether it ever worked with linux. > However the guy from whom I got the card claimed that it works w/ > windows. Please try it with windows. Then we will know whether it is ok or not. > > > As the card is listed as supported I am a bit confused what is going on > > > - any ideas? > > > > > > Soeren > > > > > > Details follow: > > > > > > kernel is 2.6.23.1 > > > > > > #lspci > > > 00:0b.0 0480: 1131:7146 (rev 01) > > > Subsystem: 13c2: > > > > This sub-system id is normally used by DVB-S cards. > > Apparently there is one more exception. :-( > > Yes... looks like it is yet another extremely old prototypical variant > of this card. I'll add this variant to the driver if (and only if) the card works. > > > # dmesg > > > > > > dvb-ttpci: info @ card 2: firm f0240009, rtsl b0250018, vid 71010068, app > > > 80f12623 > > > dvb-ttpci: firmware @ card 2 supports CI link layer interface > > > dvb-ttpci: Crystal audio DAC @ card 2 detected > > > saa7146_vv: saa7146 (2): registered device video1 [v4l2] > > > saa7146_vv: saa7146 (2): registered device vbi1 [v4l2] > > > ves1820: ves1820_readreg(): readreg error (reg == 0x1a,ret == -121) > > > DVB: registering frontend 2 (Spase SP8870 DVB-T)... > > > input: DVB on-card IR receiver as > > > /devices/pci:00/:00:0b.0/input/input9 > > > dvb-ttpci: found av7110-1. > > > > > > hires photo taken of the card or further info on request... > > > > Is this your card? > > http://vdr-wiki.de/wiki/index.php/DVB-T_full-featured-Karten > > yes, except that the stickers are different, the one on the metal box > says TDLB7X257A 991006 ALPS and instead of the bar code I have > TT-DVB-1.2 Ve0034/00 > > > Please note that this card is not able to tune to VHF channels! > > Yes, but VHF is only 30 MHz to 300 MHz and according to > http://www.telesat-info.de/sat/dvbt/dvbthome.html > this affects only channel 5 & 7 (FAB/arte). > > So it should not be a problem to tune to 'Das Erste' or so True. CU Oliver -- VDR Remote Plugin 0.4.0: http://www.escape-edv.de/endriss/vdr/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Important note to em28xx/xc3028 users
Hi, Unfortunately, Markus has pulled offline all his repositories containing Linux drivers. (You can see http://kerneltrap.org/mailarchive/linux-kernel/2007/10/14/337446 for the reason). This mainly affects users of em28xx-based and xc3028-based devices. I suggest those of you with local copies make sure you keep them backed up; you may not be able to get another copy. Users of em28xx-based devices can use my http://www.makomk.com/hg/v4l-dvb-makomk repository, which is still maintained and should remain so for as long as necessary. In theory, it should support all the em28xx-based devices that Markus' v4l-dvb-experimental driver does, but it hasn't been tested with anything other than the device I use (and one obscure device not supported by Markus' driver). Users of other devices supported by Markus' drivers are currently stuck. If this continues, I may see what I can do about it myself, though I can't promise anything. There may also be other developers who are willing to work on the code. Aidan ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] support from cx23885 driver and Xc3028 tuner for HP/Hauppauge WinTv885 mod 77001
Dear linux-dvb developers,
owning an HP rebranded Hauppauge Express Card shipped with several mid-high end
HP laptops I would like to give you some support in further improving cx23885
driver for it to support those tuners.
here are my card specs:
HP Hauppauge WinTv 885
model 77001 rev d4c0 (Model 77xxx Analog/ATSC Hybrid, Xc3028)
tuner: Xceive xc3028 http://www.xceive.com/technology_XC3028.htm
audio tuner: stereo cx23885
decoder: cx23885 http://www.conexant.com/products/entry.jsp?id=393
- insmod cx23885 manages to create a /dev/dvb device folder only if arguments
card=3 or card=4 are supplied
- despite the card being recognized with such arguments I cannot manage to use
Kaffeine DVB support as although kaffeine -w recognises the card, it cannot
scan for any available channels ('scan on' dropdown menu is empty, clicking
'Start Scan' button does not list anything)
- also with Klear, provided a channel.conf, the program cannot tune to any
channel and outputs the same error as the scan command from dvb-utils:
"WARNING: frontend type (ATSC) is not compatible with requested tuning type
(OFDM) ERROR: initial tuning failed"
- the device is not hot-plug recognized, I had to reboot before the system can
actually recognize it (however both express card specs and windows support
plung&play).
Any other help I could provide you with debugging/testing these cards I would
be pleased to, just ask.
Thank you very very much for pioneering dvb video support for gnu/linux, I
really appreciate your efforts.
here is my lspci -vvv -nn - output
04:00.0 Multimedia video controller [0400]: Conexant Unknown device [14f1:8852]
(rev 02)
Subsystem: Hauppauge computer works Inc. Unknown device [0070:7717]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- ___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Skystar HD test results and some questions
now it works, when i'm using -p switch, i missed that, thank you, Arthem! about Q1 from my previous mail: - what is the revision of STB0899 on your card? - could you please run the same tests i described and report the results for comparison. thanks! On 10/14/07, Artem Makhutov <[EMAIL PROTECTED]> wrote: > Hi, > > On Sun, Oct 14, 2007 at 06:12:11AM -0400, Konstantin Dimitrov wrote: > > Q2) when i run "cat /dev/dvb/adapter0/dvr0 > ~/dvbs.ts" and the card > > is tuned to DVB-S channel with MPEG-2 video then i got playable (with > > mplayer) TS file, but when i do the same for DVB-S2 channel with H.264 > > video mplayer plays only the audio and reports: > > > > TS file format detected. > > VIDEO MPEG2(pid=767) AUDIO MPA(pid=768) NO SUBS (yet)! PROGRAM N. 0 > > MPEG: FATAL: EOF while searching for sequence header. > > Video: Cannot read properties. > > > > so how to dump correct TS file with H.264 video ? > > I think that you forgot the -p paramter for szap. > > Try to tune it with: > > $ szap -p -r -t 2 ProSiebenHD > $ cat /dev/dvb/adapter0/dvr0 > HDMovie.ts > > Regards, Artem > > -- > Artem Makhutov > Unterort Str. 36 > D-65760 Eschborn > ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Common interface on Technotrend S-1500 broken in v4l-dvb?
On 10/14/2007 12:11 AM, Oliver Endriss wrote: > P. van Gaans wrote: >> Today I was testing some stuff and downloaded and installed the newest >> v4l-dvb from hg. After a while I figured out that FTA channels on my TT >> S-1500 still worked, but the CAM would not respond. I checked all >> connections, re-inserted the CAM, reboot the computer but nothing would >> help. My CI daughterboard version is 1.1 and I bought this S-1500 end of >> august 2007. I use Ubuntu 7.04 with kernel 2.6.20-16-generic. >> >> After installing a somewhat older version of v4l-dvb I luckily had left >> on my harddisk, the common interface directly came back to life. > > Could you please try to find out which changeset broke the code? > > If you have a current HG checkout, you can update the driver to a given > version using 'hg update '. > >> Maybe I just did something wrong somewhere, but would it be possible >> some big change was made to the way the S-1500 handles the CI that could >> have broken it? > > It's probably a change in budget-ci.c or dvb_ca_en50221.c > > Just an educated guess: > Did http://linuxtv.org/hg/v4l-dvb/rev/b0a3a9b43d60 > break the code? -> 'hg update 6279' > > CU > Oliver > 6279 does not compile. make -C /home/wn/v4l-dvb/v4l make[1]: Entering directory `/home/wn/v4l-dvb/v4l' perl scripts/make_config_compat.pl /lib/modules/2.6.20-16-generic/source ./.myconfig ./config-compat.h File not found: /lib/modules/2.6.20-16-generic/source/include/linux/netdevice.h at scripts/make_config_compat.pl line 15. make[1]: *** [config-compat.h] Error 2 make[1]: Leaving directory `/home/wn/v4l-dvb/v4l' make: *** [all] Error 2 After trying a bit I figured out 6266 does compile. Everything between 6279 and 6266 does not. I can tell you that with 6266, the common interface works, I hope that's enough info. P. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Skystar HD test results and some questions
Hi, On Sun, Oct 14, 2007 at 06:12:11AM -0400, Konstantin Dimitrov wrote: > Q2) when i run "cat /dev/dvb/adapter0/dvr0 > ~/dvbs.ts" and the card > is tuned to DVB-S channel with MPEG-2 video then i got playable (with > mplayer) TS file, but when i do the same for DVB-S2 channel with H.264 > video mplayer plays only the audio and reports: > > TS file format detected. > VIDEO MPEG2(pid=767) AUDIO MPA(pid=768) NO SUBS (yet)! PROGRAM N. 0 > MPEG: FATAL: EOF while searching for sequence header. > Video: Cannot read properties. > > so how to dump correct TS file with H.264 video ? I think that you forgot the -p paramter for szap. Try to tune it with: $ szap -p -r -t 2 ProSiebenHD $ cat /dev/dvb/adapter0/dvr0 > HDMovie.ts Regards, Artem -- Artem Makhutov Unterort Str. 36 D-65760 Eschborn ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Testers wanted for alternative version of Terratec Cinergy T2 driver
Hi,
Attached is a latest version of "alternative" driver for the Terratec
Cinergy T2 USB device. The driver is heavily based on existing Cinergy T2
driver but it has been modified to fit more or less into the DVB-USB
driver framework like most of the other USB-based device drivers currently
included in kernel.
This version also has the remote control support merged back into the driver.
I'm very interested in hearing any kinds of comments about the driver.
The RC support has been implemented differently compared to the standard
DVB-USB-framework way, as the Cinergy T2 is capable of delivering multiple
RC key event codes on a single USB-message and the standard
rc_query-callback system didn't seem to be able to handle this. Therefore
I was forced to copy & modify the RC support from the DVB-USB frameowork
to better suit the Cinergy T2 needs.
If you have better ideas how to implement the support more standard way,
I'd be interested to hear about you.
The patch below applies to reasonably current HG V4L-DVB repository tree.
Regards,
Tomi Orava
diff -r 1236114ff6a9 linux/drivers/media/dvb/dvb-usb/Kconfig
--- a/linux/drivers/media/dvb/dvb-usb/Kconfig Sun Oct 07 02:17:09 2007 -0300
+++ b/linux/drivers/media/dvb/dvb-usb/Kconfig Thu Oct 11 22:05:07 2007 +0300
@@ -239,3 +239,11 @@ config DVB_USB_AF9005_REMOTE
Say Y here to support the default remote control decoding for the
Afatech AF9005 based receiver.
+config DVB_USB_CINERGY_T2
+ tristate "Alternative driver for Terratec CinergyT2/qanu USB2 DVB-T
receiver"
+ depends on DVB_USB
+ help
+ Support for "TerraTec CinergyT2" USB2.0 Highspeed DVB Receivers
+
+ Say Y if you own such a device and want to use it.
+
diff -r 1236114ff6a9 linux/drivers/media/dvb/dvb-usb/Makefile
--- a/linux/drivers/media/dvb/dvb-usb/Makefile Sun Oct 07 02:17:09 2007 -0300
+++ b/linux/drivers/media/dvb/dvb-usb/Makefile Thu Oct 11 22:05:07 2007 +0300
@@ -61,4 +61,8 @@ 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-cinergyT2-objs = cinergyT2-core.o cinergyT2-fe.o cinergyT2-remote.o
+obj-$(CONFIG_DVB_USB_CINERGY_T2) += dvb-usb-cinergyT2.o
+
+
EXTRA_CFLAGS += -Idrivers/media/dvb/dvb-core/ -Idrivers/media/dvb/frontends/
diff -r 1236114ff6a9 linux/drivers/media/dvb/dvb-usb/cinergyT2-core.c
--- /dev/null Thu Jan 01 00:00:00 1970 +
+++ b/linux/drivers/media/dvb/dvb-usb/cinergyT2-core.c Sun Oct 14 11:25:16
2007 +0300
@@ -0,0 +1,224 @@
+/*
+ * TerraTec Cinergy T�/qanu USB2 DVB-T adapter.
+ *
+ * Copyright (C) 2007 Tomi Orava ([EMAIL PROTECTED])
+ *
+ * Based on the dvb-usb-framework code and the
+ * original Terratec Cinergy T2 driver by:
+ *
+ * Copyright (C) 2004 Daniel Mack <[EMAIL PROTECTED]> and
+ * Holger Waechtler <[EMAIL PROTECTED]>
+ *
+ * Protocol Spec published on http://qanu.de/specs/terratec_cinergyT2.pdf
+ *
+ * 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; either version 2 of the License, or
+ * (at your option) any later version.
+ *
+ * This program is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ * GNU General Public License for more details.
+ *
+ * You should have received a copy of the GNU General Public License
+ * along with this program; if not, write to the Free Software
+ * Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
+ *
+ */
+
+#include "cinergyT2.h"
+
+
+/* debug */
+int dvb_usb_cinergyt2_debug;
+int disable_remote;
+
+module_param_named(debug,dvb_usb_cinergyt2_debug, int, 0644);
+MODULE_PARM_DESC(debug, "set debugging level (1=info,xfer=2,rc=4
(or-able)).");
+
+module_param_named(disable_remote,disable_remote, int, 0644);
+MODULE_PARM_DESC(disable_remote, "Disable remote controller support (int)");
+
+
+/* We are missing a release hook with usb_device data */
+struct dvb_usb_device *cinergyt2_usb_device;
+
+static struct dvb_usb_device_properties cinergyt2_properties;
+
+
+/* slightly modified version of dvb_usb_generic_rw -function */
+
+int cinergyt2_cmd(struct dvb_usb_device *d, char *wbuf, int wlen, char
*rbuf, int rlen, int delay_ms)
+{
+ int actlen,ret = -ENOMEM;
+
+ if (d->props.generic_bulk_ctrl_endpoint == 0) {
+ err("endpoint for generic control not specified.");
+ return -EINVAL;
+ }
+
+ if (wbuf == NULL || wlen == 0)
+ return -EINVAL;
+
+ if ((ret = mutex_lock_interruptible(&d->usb_mutex)))
+ return ret;
+
+ deb_xfer(">>> ");
+ debug_dump(wbuf,wlen,deb_xfer);
+
+ ret = usb_bulk_msg(d->udev,usb_sndbulkpipe(d->udev,
+ d->props.generic_bulk_ctrl_endpoint),
Re: [linux-dvb] Skystar HD test results and some questions
because otherwise the mail is too big and needs moderator approval i put the previously attached files here: http://xkodi.svobodno.com/stb0899/nrjhits.tar.gz http://xkodi.svobodno.com/stb0899/nrjhits_diseqc.tar.gz http://xkodi.svobodno.com/stb0899/pro7hd.tar.gz and cancel the posting of my earlier mail ... On 10/14/07, Konstantin Dimitrov <[EMAIL PROTECTED]> wrote: > Q2) when i run "cat /dev/dvb/adapter0/dvr0 > ~/dvbs.ts" and the card > is tuned to DVB-S channel with MPEG-2 video then i got playable (with > mplayer) TS file, but when i do the same for DVB-S2 channel with H.264 > video mplayer plays only the audio and reports: > > TS file format detected. > VIDEO MPEG2(pid=767) AUDIO MPA(pid=768) NO SUBS (yet)! PROGRAM N. 0 > MPEG: FATAL: EOF while searching for sequence header. > Video: Cannot read properties. > > so how to dump correct TS file with H.264 video ? > > thank you! > > best wishes, > konstantin > > On 10/14/07, Konstantin Dimitrov <[EMAIL PROTECTED]> wrote: > > hello Manu, > > > > i have Technisat Skystar HD card with STB0899 revision C2L, so early > > today i got your code from http://jusst.de/hg/multiproto and run some > > tests. > > > > i'm using hacked szap from http://abraham.manu.googlepages.com/szap.c > > with the patch from here: > > > > http://www.linuxtv.org/pipermail/linux-dvb/2007-October/021054.html > > > > and the following locktest.sh shell script: > > > > #!/bin/sh > > i=0 > > j=0 > > while [[ $i -lt $4 ]] > > do > > i=$((i + 1)) > > ./szap -t $3 -x $1 > > if [[ $? -eq 1 ]] > > then > > echo "fail: $i" > > j=$((j + 1)) > > fi > > sleep $2 > > done > > echo "succ: $((i - j)) | fail: $j" > > > > i run all tests on Astra 19.2E satellite with the following channels.conf: > > > > Pro7HD:12722:h:0:22000:255:259:10200 > > NRJ:11538:v:0:22000:608:628:6908 > > > > for every test i do the following steps: > > > > 1. trim /var/log/debug, /var/log/syslog, /var/log/messages > > 2. modprobe stb6100 verbose=5; modprobe stb0899 verbose=5; modprobe > > budget_ci > > 3. run locktest.sh, e.g. for the DVB-S channel i run "locktest.sh NRJ > > 5 0 20 > szap.out.nrj", which means: tune to channel NRJ, sleep for 5 > > seconds between two consecutive tune tries, use DVB-S and do 20 tune > > tries; for DVB-S2 i run "locktest.sh Pro7HD 5 2 20 > szap.out.pro7hd" > > 4. rmmod budget_ci; rmmod stb0899; rmmod stb6100 > > 5. save /var/log/debug, /var/log/syslog, /var/log/messages and > > szap.out.$chan_name > > 6. go to 1. > > > > i repeated the test many times and the results are similar. > > > > the attached "nrjhits.tar.gz" contains the logs for one of the DVB-S > > tests, 16 successful locks out of 20, try 7, 8, 9 and 17 fail to lock, > > some interesting things that i've noticed during the DVB-S test are: > > - in 3 out of 5 runs of "locktest.sh NRJ 5 0 20" always exactly try 7, > > 8, 9 and 17 fails to lock, so seems like same kind of pattern > > - when run "locktest.sh NRJ 5 0 100", i got around 80 successful locks > > out of 100, but when run "locktest.sh NRJ 45 0 100", i got around 95 > > successful locks out of 100, so seems that increasing the sleep time > > between two consecutive tune tries significantly increase the > > successful lock rate > > > > during one of the DVB-S tests with "locktest.sh NRJ 5 0 20" i received > > the following message "FE_DISEQC_SEND_BURST failed: Connection timed > > out" and that test have only 9 successful locks out of 20, try 2, 3, > > 4, 6, 7, 8, 9, 15, 16, 17 and 19 fails to lock, the attached > > "nrjhits_diseqc.tar.gz" contains the logs from that test, because > > maybe "FE_DISEQC_SEND_BURST failed: Connection timed out" is somehow > > connected to the (un)successful lock rate. > > > > the attached "pro7hd.tar.gz" contains the logs for one of the DVB-S2 > > tests, 18 successful locks out of 20, try 12 and 14 fail to lock, > > increasing the sleep time between two consecutive tune tries with > > DVB-S2 doesn't help and i always have around 90% successful locks. > > > > so, to summarize i got about 80% successful lock with DVB-S and 90% > > successful locks with DVB-S2. > > > > i am open to help you with what i can, e.g. running more tests under > > your instructions, etc. > > > > also i have some questions: > > > > Q1) here: > > > > http://linuxtv.org/pipermail/linux-dvb/2007-January/015585.html > > > > you are saying that revision C1L of STB0899 is faulty, fails to lock a > > lot and we shouldn't buy cards with STB0899 revision C1L, but here: > > > > http://linuxtv.org/pipermail/linux-dvb/2007-October/021133.html > > > > you are saying that cards with C1L tune quiet fine and the lock > > problems are only with revision C2L, so that confuses me a lot, could > > you please clarify the situation with different revisions of STB0899 ? > > > > Q2) when i run " > > > > > ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Skystar HD test results and some questions
Q2) when i run "cat /dev/dvb/adapter0/dvr0 > ~/dvbs.ts" and the card is tuned to DVB-S channel with MPEG-2 video then i got playable (with mplayer) TS file, but when i do the same for DVB-S2 channel with H.264 video mplayer plays only the audio and reports: TS file format detected. VIDEO MPEG2(pid=767) AUDIO MPA(pid=768) NO SUBS (yet)! PROGRAM N. 0 MPEG: FATAL: EOF while searching for sequence header. Video: Cannot read properties. so how to dump correct TS file with H.264 video ? thank you! best wishes, konstantin On 10/14/07, Konstantin Dimitrov <[EMAIL PROTECTED]> wrote: > hello Manu, > > i have Technisat Skystar HD card with STB0899 revision C2L, so early > today i got your code from http://jusst.de/hg/multiproto and run some > tests. > > i'm using hacked szap from http://abraham.manu.googlepages.com/szap.c > with the patch from here: > > http://www.linuxtv.org/pipermail/linux-dvb/2007-October/021054.html > > and the following locktest.sh shell script: > > #!/bin/sh > i=0 > j=0 > while [[ $i -lt $4 ]] > do > i=$((i + 1)) > ./szap -t $3 -x $1 > if [[ $? -eq 1 ]] > then > echo "fail: $i" > j=$((j + 1)) > fi > sleep $2 > done > echo "succ: $((i - j)) | fail: $j" > > i run all tests on Astra 19.2E satellite with the following channels.conf: > > Pro7HD:12722:h:0:22000:255:259:10200 > NRJ:11538:v:0:22000:608:628:6908 > > for every test i do the following steps: > > 1. trim /var/log/debug, /var/log/syslog, /var/log/messages > 2. modprobe stb6100 verbose=5; modprobe stb0899 verbose=5; modprobe budget_ci > 3. run locktest.sh, e.g. for the DVB-S channel i run "locktest.sh NRJ > 5 0 20 > szap.out.nrj", which means: tune to channel NRJ, sleep for 5 > seconds between two consecutive tune tries, use DVB-S and do 20 tune > tries; for DVB-S2 i run "locktest.sh Pro7HD 5 2 20 > szap.out.pro7hd" > 4. rmmod budget_ci; rmmod stb0899; rmmod stb6100 > 5. save /var/log/debug, /var/log/syslog, /var/log/messages and > szap.out.$chan_name > 6. go to 1. > > i repeated the test many times and the results are similar. > > the attached "nrjhits.tar.gz" contains the logs for one of the DVB-S > tests, 16 successful locks out of 20, try 7, 8, 9 and 17 fail to lock, > some interesting things that i've noticed during the DVB-S test are: > - in 3 out of 5 runs of "locktest.sh NRJ 5 0 20" always exactly try 7, > 8, 9 and 17 fails to lock, so seems like same kind of pattern > - when run "locktest.sh NRJ 5 0 100", i got around 80 successful locks > out of 100, but when run "locktest.sh NRJ 45 0 100", i got around 95 > successful locks out of 100, so seems that increasing the sleep time > between two consecutive tune tries significantly increase the > successful lock rate > > during one of the DVB-S tests with "locktest.sh NRJ 5 0 20" i received > the following message "FE_DISEQC_SEND_BURST failed: Connection timed > out" and that test have only 9 successful locks out of 20, try 2, 3, > 4, 6, 7, 8, 9, 15, 16, 17 and 19 fails to lock, the attached > "nrjhits_diseqc.tar.gz" contains the logs from that test, because > maybe "FE_DISEQC_SEND_BURST failed: Connection timed out" is somehow > connected to the (un)successful lock rate. > > the attached "pro7hd.tar.gz" contains the logs for one of the DVB-S2 > tests, 18 successful locks out of 20, try 12 and 14 fail to lock, > increasing the sleep time between two consecutive tune tries with > DVB-S2 doesn't help and i always have around 90% successful locks. > > so, to summarize i got about 80% successful lock with DVB-S and 90% > successful locks with DVB-S2. > > i am open to help you with what i can, e.g. running more tests under > your instructions, etc. > > also i have some questions: > > Q1) here: > > http://linuxtv.org/pipermail/linux-dvb/2007-January/015585.html > > you are saying that revision C1L of STB0899 is faulty, fails to lock a > lot and we shouldn't buy cards with STB0899 revision C1L, but here: > > http://linuxtv.org/pipermail/linux-dvb/2007-October/021133.html > > you are saying that cards with C1L tune quiet fine and the lock > problems are only with revision C2L, so that confuses me a lot, could > you please clarify the situation with different revisions of STB0899 ? > > Q2) when i run " > > ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] TT-2300 with IR on CI - not work??
>> It always registers, no matter whether there is an ir receiver or not. > > oh, ok! > >>> ...and I've added the little jumper on the CI - but it won't work. >>> >>> I do a 'tail -f /dev/input/event3' and get nothing when pointing the >>> remote >>> at it. >> >> This will only work if you have loaded a keymap. > > This isn't something I've done before - always used serial homebrew and > LIRC OK - works. Thanks. Some buttons dont work - will work on this ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
