From: Brice DUBOST <braice@braice.net>
To: "Ali H.M. Hoseini" <alihmh@gmail.com>
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] how to prevent scan utility from scaning other transponders?
Date: Sat, 16 Aug 2008 11:10:08 +0200 [thread overview]
Message-ID: <48A69970.4040706@braice.net> (raw)
In-Reply-To: <66caf1560808160142g7446425co164b36cce747c600@mail.gmail.com>
Ali H.M. Hoseini a écrit :
>
>
> On Sat, Aug 16, 2008 at 12:02 PM, Brice DUBOST <braice@braice.net
> <mailto:braice@braice.net>> wrote:
>
> Ali H.M. Hoseini a écrit :
> > Hi all,
> >
> > When I use scan utility to scan a transponder, in some freq. scan
> > continues to scan other transponders (I think find them in NIT
> tables),
> > and that mean I should wait 2-3 minutes for scan to complete it's
> work,
> > and list all the transponders it found.
> >
> > how should I prevent scan utility from scaning other transponders? And
> > force it to scan just the transponder I want?
> >
> >
> > Thanks.
> >
> > Ali.
> >
>
> Hello
>
> Lock on the transponder
>
> and use scan -c
>
> Regards
>
>
> Hi ,
>
> Thanks Brice, But I'm trying to find a way to do this just with scan.
> Because if I want to tune to freq. with szap, first I should create an
> channels.conf file. This is the hen and egg problem, because I should
> first scan that freq. to create channels.conf.
>
> Does anybody knows a solution for this?
>
> Regard.
>
Hello
Use dvbtune
Regards
--
Brice
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
prev parent reply other threads:[~2008-08-16 9:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-16 8:30 [linux-dvb] how to prevent scan utility from scaning other transponders? Ali H.M. Hoseini
2008-08-16 8:32 ` Brice DUBOST
2008-08-16 8:42 ` Ali H.M. Hoseini
2008-08-16 9:10 ` Brice DUBOST [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=48A69970.4040706@braice.net \
--to=braice@braice.net \
--cc=alihmh@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.