public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Per Heldal <heldal@eml.cc>
To: Goga777 <goga777@bk.ru>
Cc: Hans Werner <HWerner4@gmx.de>, linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] [PATCH] scan-s2: fixes and diseqc rotor support
Date: Wed, 12 Nov 2008 11:21:35 +0100	[thread overview]
Message-ID: <1226485295.19990.28.camel@obelix> (raw)
In-Reply-To: <E1L09Ud-000GW2-00.goga777-bk-ru@f149.mail.ru>

On Wed, 2008-11-12 at 09:46 +0300, Goga777 wrote:
> thanks for your patch.
> 
> btw - could you scan dvb-s2 (qpsk & 8psk) channels with scan-s2 and
> hvr4000 ? with which drivers ?
> 

I seem to be able to scan some transponders, but not all, using current
code from the repos at http://linuxtv.org/hg/v4l-dvb/ and
http://mercurial.intuxication.org/hg/scan-s2 

I run scan-s2 on the following list of HD-transponders on 0.8w :

S 11938000 H 25000000 3/4 35 8PSK
S 12015000 H 30000000 3/4 35 8PSK
S 12130000 H 30000000 3/4 35 8PSK
S 12188000 V 25000000 3/4 35 8PSK

(a selection of transponders from
http://lyngsat.com/packages/canaldigital.html)

With rolloff set to AUTO scan-s2 will not lock to any transponder.
Instead it will appear to repeatedly re-scan sources on any transponder
the tuner previously was tuned to.

With rolloff set to 35 as above scan-s2 will lock and find channels on
both transponders with SR=25000000, but for the 2 in the middle with
SR=30000000 it simply repeats the channel-list of the previous
transponder. I've been playing with alternatives for rolloff and
modulation with no result.



-- 


Per Heldal - http://heldal.eml.cc/


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

  reply	other threads:[~2008-11-12 10:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-12  2:31 [linux-dvb] [PATCH] scan-s2: fixes and diseqc rotor support Hans Werner
2008-11-12  6:46 ` Goga777
2008-11-12 10:21   ` Per Heldal [this message]
2008-11-12 10:44     ` Alex Betis
2008-11-12 11:51   ` Hans Werner
2008-11-12 10:43 ` Alex Betis
2008-11-12 11:24   ` BOUWSMA Barry
2008-11-12 11:44     ` Ales Jurik
2008-11-12 12:08     ` Alex Betis
2008-11-12 12:47       ` BOUWSMA Barry
2008-11-12 12:59         ` Alex Betis
2008-11-12 13:20           ` BOUWSMA Barry
2008-11-12 12:59       ` Christophe Thommeret
     [not found]       ` <200811121353.47705.hftom@free.fr>
2008-11-12 13:01         ` Alex Betis
2008-11-12 13:04           ` Christophe Thommeret
2008-11-12 14:03             ` Hans Werner
2008-11-12 12:39   ` Hans Werner
2008-11-12 20:56 ` Alex Betis
2008-11-13 23:04   ` Hans Werner
2008-11-14  8:30     ` Alex Betis

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=1226485295.19990.28.camel@obelix \
    --to=heldal@eml.cc \
    --cc=HWerner4@gmx.de \
    --cc=goga777@bk.ru \
    --cc=linux-dvb@linuxtv.org \
    /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