From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mx3.redhat.com (mx3.redhat.com [172.16.48.32]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m1FMCkej023872 for ; Fri, 15 Feb 2008 17:12:46 -0500 Received: from mail-in-06.arcor-online.net (mail-in-06.arcor-online.net [151.189.21.46]) by mx3.redhat.com (8.13.8/8.13.8) with ESMTP id m1FMCDqC005084 for ; Fri, 15 Feb 2008 17:12:13 -0500 From: hermann pitton To: Hartmut Hackmann In-Reply-To: <47B4DDB3.5010904@t-online.de> References: <47B392A5.2030908@t-online.de> <1202986913.5036.3.camel@pc08.localdom.local> <1203005937.5871.12.camel@pc08.localdom.local> <47B4B9AE.5010907@t-online.de> <1203029639.6805.66.camel@pc08.localdom.local> <47B4DDB3.5010904@t-online.de> Content-Type: text/plain Date: Fri, 15 Feb 2008 23:07:16 +0100 Message-Id: <1203113236.7303.34.camel@pc08.localdom.local> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Cc: Linux and Kernel Video , LInux DVB Subject: Re: [linux-dvb] Mdeion / Creatix CTX948 DVB-S driver is ready for testing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: video4linux-list-bounces@redhat.com Errors-To: video4linux-list-bounces@redhat.com List-ID: Hi, Hartmut, Am Freitag, den 15.02.2008, 01:32 +0100 schrieb Hartmut Hackmann: > Hi, again > > > > >> So this one works as well, great! But which one is it? > >> Please tell me the minor device id. I need to use it to separate the 2 sections. > >> i will need to control the other one in a very different way. > > > > Seems default is some RF loopthrough. > > > > I'll need to measure too against loopthrough conditions, but for sure > > voltage is only on the upper connector and previously with the RF feed > > from the external receiver the lower connector was fine enough. > > > > No voltage in any previous testing and the 12Volts were always > > connected. > > > > Both slightly different Quads from different fabs work as well as the > > CTX948. In my case it is the 16be:0007 and to the 16be:0008 I have no > > access. > > > Perfect, that's what i needed to know. > > > > > > We might be already through here and you might like to commit first ;) > > > Indeed. I should also announce this status for the md8800... > > What's your opinion on this: > According to the hints i got, the isl6405 is visible only on one section > of the md8800. The other section has control over the voltage through > a GPIO port. So unless i do something very dirty, there will either be the > restriction > - that the DVB-S decoder of the 16be:0007 section needs to be selected first. > Otherwise the other DVB-S part will not work > - or i will need to always fire up the LNB supply of the 0008 section as soon > as DVB is initialized. > The second approach has the advantage that it has little effect for the end > user while the first needs to be explained. > But i am not sure whether the isl6405 is fully short circuit proof. I will read > the datasheet again... > if the second approach is safe and the API says nothing different, according to the MD8800 manual, it seems to be closer to the behavior of the other OS, but I can't test it. In opposite to what is stated for the switchable RF loopthrough on the two hybrid tuners, the manual claims that the DVB-S inputs are separate and not connected and nothing to switch there ... Andrew has loopthrough enabled by default and that is what I even see from the unused second DVB-S tuner to the first one I can use. We might want to set has_loopthrough = 0 then too. Funny stuff again. The latest revision of the manual _seems_ to be clear for possible tuner/demod/bridge combinations, also states nothing about concurrent usage of the other analog inputs. Cheers, Hermann -- video4linux-list mailing list Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe https://www.redhat.com/mailman/listinfo/video4linux-list