public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: "Hans Werner" <HWerner4@gmx.de>
To: linux-media@vger.kernel.org
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] How to use scan-s2?
Date: Sun, 25 Jan 2009 17:29:59 +0100	[thread overview]
Message-ID: <20090125162959.86940@gmx.net> (raw)
In-Reply-To: <c74595dc0901250654l49b419dcw2327b1cfb0ebe0dc@mail.gmail.com>

> On Sun, Jan 25, 2009 at 4:41 PM, Hans Werner <HWerner4@gmx.de> wrote:
> 
> > > If you have a stb0899 device, don't forget to add "-k 3".
> >
> > Oh. Can someone say what's different about the stb0899 here,
> > and how -k 3 helps ?
> 
> 
> Since I've added it, I'll try to defend it :)
> 
> stb0899 driver (or maybe the chip?) has some buffers inside that are not
> reset between tunnings.
> In that case messages from *previous* channel will arrive after the
> tunning
> to new channel is complete.
> Those messages will create a big mess in the results, such as channels
> without names, duplicate channels on different transponders.
> -k option specifies how many messages should be ignored before processing
> it. I couldn't think of a more elegant way to ignore messages from
> previously tuned channel. I use "-k 3" by myself, but after playing around
> with "-k 2" saw that its also working. "-k 1" was still not enough.
> 
> The proper way is to have an option to reset that buffer in the driver
> after
> tunning.
> Since I don't know how it can be done and how it will affect tunning of
> channels for viewing, I didn't want to go that way and solve it in
> scan-s2.
> 
> Regards,
> Alex.

OK, thanks, I will check if I see that problem. Which card(s)
did you see this with?
Hans
-- 
Release early, release often.

Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger

  reply	other threads:[~2009-01-25 16:30 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-25 10:29 [linux-dvb] How to use scan-s2? Artem Makhutov
2009-01-25  9:49 ` Jens Krehbiel-Gräther
2009-01-25 13:25   ` Alex Betis
2009-01-25 14:41     ` Hans Werner
2009-01-25 14:54       ` Alex Betis
2009-01-25 16:29         ` Hans Werner [this message]
2009-01-25 16:56           ` Alex Betis
2009-01-26  3:24             ` BOUWSMA Barry
2009-01-25 23:48     ` Mika Laitio
2009-01-26  9:35       ` Alex Betis
2009-01-26 15:43         ` Mika Laitio
2009-01-26 15:53           ` Alex Betis
2009-01-26 17:32             ` Darron Broad
2009-01-26 19:30               ` Alex Betis
2009-01-26 20:20                 ` Darron Broad
2009-01-26 20:31                   ` Alex Betis
2009-01-27  0:59                     ` Andy Walls
2009-01-27  7:48                       ` Alex Betis
2009-01-27 14:11                       ` Darron Broad
2009-01-27 14:07                     ` Darron Broad
2009-01-26 19:44           ` Goga777
2009-01-25 14:25   ` Artem Makhutov
2009-01-25 17:48     ` Goga777

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=20090125162959.86940@gmx.net \
    --to=hwerner4@gmx.de \
    --cc=linux-dvb@linuxtv.org \
    --cc=linux-media@vger.kernel.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