From: "Tycho Lürsen" <tycholursen@gmail.com>
To: Steven Toth <stoth@kernellabs.com>
Cc: tonyc@wincomm.com.tw, Antti Palosaari <crope@iki.fi>,
Linux-Media <linux-media@vger.kernel.org>
Subject: Re: Adding support for three new Hauppauge HVR-1275 variants - testers reqd.
Date: Tue, 21 Jul 2015 20:07:47 +0200 [thread overview]
Message-ID: <55AE8A73.9070802@gmail.com> (raw)
In-Reply-To: <CALzAhNVuez1_byQe+FiOjZPdUpdgMg0q8CT2KPJ-rO8o8dohzw@mail.gmail.com>
Op 21-07-15 om 18:19 schreef Steven Toth:
> On Tue, Jul 21, 2015 at 12:11 PM, Tycho Lürsen <tycholursen@gmail.com> wrote:
>> Hi Steven,
>> I was too curious to wait for you and Antti to settle your differences, so I
>> tested again against a 4.2-RC2
>> I did not disable DVB-T/T2, instead I reordered the lot. MythTV just sees
>> the first system in the .delsys line in si2168.c,
>> so when it looks like this:
>> SYS_DVBC_ANNEX_A, SYS_DVBT, SYS_DVBT2
>> I'm good.
> We have no differences, its Antti's si2168 driver. If Antti doesn't
> like the approach for tri-stating, he's free to suggest and
> alternative. I suggested two alternatives yesterday.
>
>> Result:
>> With your patch both MythTV and Tvheadend still can't tune. Without it,
>> everything is ok.
>>
>> I'm not very interested in czap results, only in real use cases. For me
>> that's MythTV, but just to be sure I also tested with TVheadend.
> That's pretty bizarre results, although thank you for testing. :)
>
> When you say it can't tune, do you mean the signal does not lock, or
> that no video appears?
>
No lock, or partial lock.
next prev parent reply other threads:[~2015-07-21 18:07 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-18 22:21 Adding support for three new Hauppauge HVR-1275 variants - testers reqd Steven Toth
2015-07-19 7:34 ` Tycho Lürsen
2015-07-20 13:13 ` Steven Toth
2015-07-20 16:06 ` Tycho Lürsen
2015-07-20 16:32 ` Steven Toth
2015-07-21 16:11 ` Tycho Lürsen
2015-07-21 16:19 ` Steven Toth
2015-07-21 18:07 ` Tycho Lürsen [this message]
2015-07-21 18:59 ` Tycho Lürsen
2015-07-21 19:02 ` Steven Toth
2015-07-21 19:21 ` Tycho Lürsen
2015-07-21 19:00 ` Steven Toth
2015-07-21 21:33 ` Tycho Lürsen
2015-07-22 7:15 ` Tycho Lürsen
2015-07-22 12:55 ` Steven Toth
2015-07-22 17:44 ` Tycho Lürsen
2015-07-24 13:38 ` Steven Toth
2015-07-20 0:52 ` Tony Chang(Wincomm)
[not found] ` <1454427BAA91444C85615ABB9382A2DE@wincomm.com.tw>
2015-07-20 12:38 ` Steven Toth
2015-07-20 14:30 ` Antti Palosaari
2015-07-20 15:00 ` Steven Toth
2015-07-20 16:35 ` Antti Palosaari
2015-07-20 16:45 ` Devin Heitmueller
2015-07-20 16:54 ` Antti Palosaari
2015-07-20 17:14 ` Steven Toth
2015-07-20 17:28 ` Antti Palosaari
2015-07-20 19:04 ` Steven Toth
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=55AE8A73.9070802@gmail.com \
--to=tycholursen@gmail.com \
--cc=crope@iki.fi \
--cc=linux-media@vger.kernel.org \
--cc=stoth@kernellabs.com \
--cc=tonyc@wincomm.com.tw \
/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