public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
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 18:11:29 +0200	[thread overview]
Message-ID: <55AE6F31.3050308@gmail.com> (raw)
In-Reply-To: <CALzAhNVmmAy=4r0Vd=T82HPUrOzxK9Rg2-M=DQ8gUa-DXKsS6w@mail.gmail.com>

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.

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.

Regards,
Tycho.

Op 20-07-15 om 18:32 schreef Steven Toth:
> On Mon, Jul 20, 2015 at 12:06 PM, Tycho Lürsen <tycholursen@gmail.com> wrote:
>> Hi Steven,
>> I was not aware of the fact that your patch depends on dvb-core as in
>> 4.2-RC2 (and up, I guess)
>> I tested against 3.18.18 and 4.1.2. That might explain the failures.
>> Anyhow, as soon as Antti and you are on the same page regarding this patch,
>> I'll test again against a 4.2-RC>1
>> Regards,
>> Tycho.
> Thank you Tycho.
>
> I specifically only tested on 4.2, with the entire tree. No attempt
> was made to backport or otherwise test in environments outside on
> prior kernels.
>
> - Steve
>


  reply	other threads:[~2015-07-21 16:11 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 [this message]
2015-07-21 16:19           ` Steven Toth
2015-07-21 18:07             ` Tycho Lürsen
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=55AE6F31.3050308@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