From: Richard Zidlicky <rz@linux-m68k.org>
To: "Pedro Côrte-Real" <pedro@pedrocr.net>
Cc: linux-media@vger.kernel.org
Subject: Re: Trouble getting DVB-T working with Portuguese transmissions
Date: Sat, 19 Jun 2010 20:58:17 +0200 [thread overview]
Message-ID: <20100619185817.GA20032@linux-m68k.org> (raw)
In-Reply-To: <AANLkTilA7_uw8memTQfyv5-YJD02HaroYmKJuSzePZBS@mail.gmail.com>
On Fri, Jun 18, 2010 at 02:28:38PM +0100, Pedro Côrte-Real wrote:
> On Thu, Jun 17, 2010 at 9:00 PM, Richard Zidlicky <rz@linux-m68k.org> wrote:
> > berr is supposed to be the bit error rate. The values displayed here appear to be
> > bogus - then again I am not familiar with this particular driver so maybe just the
> > error reporting is bogus. The w_scan results also look pretty bad.
> >
> > Newest kernel is allways worth a try.
>
> I have tried a git snapshot of Linus' 2.6.35 kernel. Is there another
> non-mainline tree I should try?
>
> Would it help to get some kind of dvbsnoop log of this? I've tried
> doing "dvbsnoop -s pidscan" and "dvbsnoop 0" but didn't get anything
> that seemed valid.
did you test the hardware with the evil OS?
> Alternatively what is a well supported usb DVB-T tunner? I've also
> bought an Avermedia Volar HX and a Gigabyte 7200 which seem to have at
> best some half-assed out-of-tree drivers.
I am using
idVendor=2040, idProduct=5500
WinTV MiniStick
Manufacturer: Hauppauge Computer Works
works reasonably well, needs a patch to enable remote.
Richard
next prev parent reply other threads:[~2010-06-19 18:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-16 10:24 Trouble getting DVB-T working with Portuguese transmissions Pedro Côrte-Real
2010-06-16 10:43 ` Pedro Côrte-Real
2010-06-16 20:57 ` Richard Zidlicky
2010-06-17 9:03 ` Pedro Côrte-Real
2010-06-17 9:51 ` Pedro Côrte-Real
2010-06-17 20:00 ` Richard Zidlicky
2010-06-18 13:28 ` Pedro Côrte-Real
2010-06-19 18:58 ` Richard Zidlicky [this message]
2010-06-19 19:17 ` Pedro Côrte-Real
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=20100619185817.GA20032@linux-m68k.org \
--to=rz@linux-m68k.org \
--cc=linux-media@vger.kernel.org \
--cc=pedro@pedrocr.net \
/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.