public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: hermann pitton <hermann-pitton@arcor.de>
To: Hartmut Hackmann <hartmut.hackmann@t-online.de>
Cc: Linux and Kernel Video <video4linux-list@redhat.com>,
	LInux DVB <linux-dvb@linuxtv.org>
Subject: Re: [linux-dvb] Mdeion / Creatix CTX948 DVB-S driver is ready	for testing
Date: Fri, 15 Feb 2008 23:07:16 +0100	[thread overview]
Message-ID: <1203113236.7303.34.camel@pc08.localdom.local> (raw)
In-Reply-To: <47B4DDB3.5010904@t-online.de>

Hi, Hartmut,

Am Freitag, den 15.02.2008, 01:32 +0100 schrieb Hartmut Hackmann:
> Hi, again
> 
> <snip>
> 
> >> 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.
> 
> <snip>
> > 
> > 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

      reply	other threads:[~2008-02-15 22:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-14  1:00 Mdeion / Creatix CTX948 DVB-S driver is ready for testing Hartmut Hackmann
2008-02-14 11:01 ` [linux-dvb] " hermann pitton
2008-02-14 16:18   ` hermann pitton
2008-02-14 21:59     ` Hartmut Hackmann
2008-02-14 22:53       ` hermann pitton
2008-02-15  0:32         ` Hartmut Hackmann
2008-02-15 22:07           ` hermann pitton [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1203113236.7303.34.camel@pc08.localdom.local \
    --to=hermann-pitton@arcor.de \
    --cc=hartmut.hackmann@t-online.de \
    --cc=linux-dvb@linuxtv.org \
    --cc=video4linux-list@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox