All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Toth <stoth@linuxtv.org>
To: David Engel <david@istwok.net>
Cc: linux-media@vger.kernel.org, V4L <video4linux-list@redhat.com>
Subject: Re: PVR x50 corrupts ATSC 115 streams
Date: Thu, 19 Feb 2009 11:44:54 -0500	[thread overview]
Message-ID: <499D8C86.4050501@linuxtv.org> (raw)
In-Reply-To: <20090219162820.GA23759@opus.istwok.net>

> 
> FWIW, I used a different 115 with that same motherboard for several
> months up until about two weeks ago and with that same graphics card
> for most of that time.  Like I said above, I've got to be missing
> something very stupid here.  
> 
> BTW, during all of the testing without the active splitter, I had it
> unplugged to make sure it wasn't contributing any extra RF noise.  I
> won't have an opportunity to do any more testing until this weekend.

I think CityK confirmed that the nxt2004 driver statistics are probably bogus so 
I doubt you're going to get your 115's running with BER 0 regardless, which is 
unfortunate.

Assuming your original configuration was fine, the second part of the problem 
remains then.... is the DMA being screwed by the mix of boards.

I'm not sure I have an easy way for you to determine this, other than making 
sure everything is on it's own interrupt, going back to basics to a single 115 
and a single 250 and trying to isolate the changes step by step.

- Steve



  reply	other threads:[~2009-02-19 16:45 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-17 15:53 PVR x50 corrupts ATSC 115 streams David Engel
2009-02-17 16:05 ` Steven Toth
2009-02-17 20:17   ` David Engel
2009-02-17 20:29     ` Steven Toth
2009-02-17 20:56       ` David Engel
2009-02-17 21:05         ` Devin Heitmueller
2009-02-17 22:29           ` Steven Toth
2009-02-17 22:38             ` Devin Heitmueller
2009-02-18 15:16               ` Steven Toth
2009-02-19  2:11                 ` CityK
2009-02-19 15:26                   ` Steven Toth
2009-02-18  5:19       ` David Engel
2009-02-18  8:25         ` Rudy Zijlstra
2009-02-18 15:29           ` David Engel
2009-02-18 14:56         ` Steven Toth
2009-02-18 15:34           ` David Engel
2009-02-19 16:28             ` David Engel
2009-02-19 16:44               ` Steven Toth [this message]
2009-02-22 19:35               ` CityK
2009-02-23 18:39                 ` David Engel
2009-02-23 19:06                   ` Steven Toth
2009-02-23 20:10                     ` David Engel
2009-02-23 21:53                       ` Steven Toth
2009-02-23 22:03                         ` Devin Heitmueller
2009-02-23 22:48                           ` David Engel
2009-02-23 22:58                             ` Devin Heitmueller
2009-02-24  1:38                               ` pat-lkml
2009-02-24 16:40                               ` David Engel
2009-02-24  0:05                       ` Andy Walls
2009-08-07  2:50 ` David Engel
  -- strict thread matches above, loose matches on Subject: below --
2009-02-18 12:41 Andreas
2009-02-18 15:39 ` David Engel
2009-02-19  3:37 ` CityK
2009-02-19 13:30   ` Andreas

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=499D8C86.4050501@linuxtv.org \
    --to=stoth@linuxtv.org \
    --cc=david@istwok.net \
    --cc=linux-media@vger.kernel.org \
    --cc=video4linux-list@redhat.com \
    /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.