From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
To: Gregor Jasny <gjasny@googlemail.com>
Cc: Marcel Heinz <quisquilia@gmx.de>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: Bug#854100: libdvbv5-0: fails to tune / scan
Date: Wed, 15 Feb 2017 12:37:40 -0200 [thread overview]
Message-ID: <20170215123740.00bc9e8e@vento.lan> (raw)
In-Reply-To: <20170215111318.65ae1f0b@vento.lan>
Em Wed, 15 Feb 2017 11:13:18 -0200
Mauro Carvalho Chehab <mchehab@osg.samsung.com> escreveu:
> Hi Gregor,
>
> Em Mon, 13 Feb 2017 08:04:48 -0200
> Mauro Carvalho Chehab <mchehab@osg.samsung.com> escreveu:
>
> > Em Fri, 10 Feb 2017 22:02:01 +0100
> > Gregor Jasny <gjasny@googlemail.com> escreveu:
> >
> > > Hello Mauro & DVB-S maintainers,
> > >
> > > could you please have a look at the bug report below? Marcel was so kind
> > > to bisect the problem to the following commit:
> > >
> > > https://git.linuxtv.org/v4l-utils.git/commit/?id=d982b0d03b1f929269104bb716c9d4b50c945125
> >
> > Sorry for not handling it earlier. I took vacations on Jan, and had a pile
> > of patches to handle after my return. I had to priorize them, as we're
> > close to a Kernel merge window.
> >
> > Now that Linus postponed the merge window, I had some time to dig into
> > it.
> >
> > >
> > > Bug report against libdvbv5 is here:
> > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854100
> >
> > There was a bug at the logic that was checking if the frequency was
> > at the range of the local oscillators. This patch should be addressing
> > it:
> > https://git.linuxtv.org/v4l-utils.git/commit/?id=5380ad44de416a41b4972e8a9c147ce42b0e3ba0
> >
> > With that, the logic now seems to be working fine:
> >
> > $ ./utils/dvb/dvbv5-scan ~/Intelsat-34 --lnbf universal -vv
> > Using LNBf UNIVERSAL
> > Universal, Europe
> > 10800 to 11800 MHz, LO: 9750 MHz
> > 11600 to 12700 MHz, LO: 10600 MHz
> > ...
> > Seeking for LO for 12.17 MHz frequency
> > LO setting 0: 10.80 MHz to 11.80 MHz
> > LO setting 1: 11.60 MHz to 12.70 MHz
> > Multi-LO LNBf. using LO setting 1 at 10600.00 MHz
> > frequency: 12170.00 MHz, high_band: 1
> > L-Band frequency: 1570.00 MHz (offset = 10600.00 MHz)
> >
> > I can't really test it here, as my satellite dish uses a different
> > type of LNBf, but, from the above logs, the bug should be fixed.
> >
> > Marcel,
> >
> > Could you please test? The patch is already upstream.
> > I added a debug patch after it, in order to help LNBf issues
> > (enabled by using "-vv" command line parameters).
>
> I added both patches to stable-1.12 branch. I also added a small
> patch there adding support for an extra LNBf model at the DVB
> Satellite table. Such change is not disruptive, as it just
> adds a new element on an already-existing table.
>
> Btw, I found another bug there. Starting to look on it right now.
>
> There's something wrong with translations there. It seems that
> something is causing i18n to print its headers instead of doing
> the right thing.
>
> I'm enclosing the results at the end of this e-mail, with
> pt_BR translation, with is currently the only one available.
>
> I think you should wait for this bug to get fixed before releasing
> a new -stable release.
Bug fixed and pushed to stable-1.12 directory. I also updated
there the pt_BR translation for libdvbv5.
--
Thanks,
Mauro
next prev parent reply other threads:[~2017-02-15 14:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <148617570740.6827.6324247760769667383.reportbug@ixtlilton.netz.invalid>
2017-02-04 9:08 ` Bug#854100: libdvbv5-0: fails to tune / scan Gregor Jasny
2017-02-04 12:35 ` Marcel Heinz
[not found] ` <CAJxGH0-ewWzxSJ1vE+n4FMkqv+pnmT9G0uAZS5oUYkhxWm+=5A@mail.gmail.com>
2017-02-04 16:43 ` Marcel Heinz
2017-02-10 21:02 ` Gregor Jasny
2017-02-13 10:04 ` Mauro Carvalho Chehab
2017-02-15 13:13 ` Mauro Carvalho Chehab
2017-02-15 14:37 ` Mauro Carvalho Chehab [this message]
2017-02-17 21:50 Marcel Heinz
2017-02-20 9:52 ` Mauro Carvalho Chehab
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=20170215123740.00bc9e8e@vento.lan \
--to=mchehab@osg.samsung.com \
--cc=gjasny@googlemail.com \
--cc=linux-media@vger.kernel.org \
--cc=quisquilia@gmx.de \
/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.