public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Malcolm Priestley <tvboxspy@gmail.com>
To: Jason Hecker <jwhecker@gmail.com>
Cc: Antti Palosaari <crope@iki.fi>,
	Josu Lazkano <josu.lazkano@gmail.com>,
	linux-media <linux-media@vger.kernel.org>
Subject: Re: [PATCH] af9013 Extended monitoring in set_frontend.
Date: Sun, 16 Oct 2011 21:26:33 +0100	[thread overview]
Message-ID: <4e9b3dff.e766e30a.54ec.4d44@mx.google.com> (raw)
In-Reply-To: <CAATJ+fub_tmoXxxPKU1vBnRNT=7MEUTn0T=_+iP2koj7N4MBrA@mail.gmail.com>

On Tue, 2011-10-11 at 08:06 +1100, Jason Hecker wrote:
> > Playing with Kaffeine or Mplayer all the devices are fine on the same
> > system.
> 
> Right, admittedly most of my testing has been done with MythTV.  I
> recall about a month ago I could also get corruption with mplayer.
> 
> > At the moment, I am going step by step what Myth TV is sending to the
> > devices.
> 
> Great.  If you want I can replicate your tests here to see what I get.
> 
> Antti, my AF9015 chips are integrated on PCI so I can't swap cables
> (alas, if only this was my problem!)

Jason, do you get firmware loading fails on boot with the PCI device?

There needs to be a delay put in the firmware download of at least 250uS
after each write, but this does not solve the corruption.

I have tried everything, but all of them fail to get rid of the
corruption on the first frontend when the second frontend starts and
then corruptions every 5 seconds or so. These only come through demux on
endpoint 84 and are not caused by any other frontend operations.

Trouble is, on a Nvidia motherboard I have it does not do it at all and
all applications work without any troubles.  This seems to suggest a USB
motherboard driver issue.

However, the frontend lock does make it at least work on Myth TV.

I am continuing to look into it.

Regards

Malcolm


  reply	other threads:[~2011-10-16 20:26 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4e83369f.5d6de30a.485b.ffffdc29@mx.google.com>
2011-10-04 19:28 ` [PATCH] af9013 frontend tuner bus lock Josu Lazkano
2011-10-04 20:44   ` Jason Hecker
2011-10-04 21:54     ` Malcolm Priestley
2011-10-04 22:10       ` Jason Hecker
2011-10-05 11:40         ` Josu Lazkano
2011-10-05 22:19           ` Jason Hecker
2011-10-05 23:12             ` Josu Lazkano
2011-10-06  2:39               ` Jason Hecker
2011-10-06 20:07               ` dave cunningham
2011-10-06 21:48                 ` Josu Lazkano
2011-10-06 22:34                   ` Jason Hecker
2011-10-06 21:13               ` Malcolm Priestley
2011-10-07 21:11             ` [PATCH] af9013 Extended monitoring in set_frontend Malcolm Priestley
2011-10-07 22:46               ` Jason Hecker
2011-10-08 13:10                 ` Malcolm Priestley
2011-10-08 13:13                 ` Josu Lazkano
2011-10-08 13:26                   ` Malcolm Priestley
2011-10-08 13:42                     ` Josu Lazkano
2011-10-08 14:06                     ` Antti Palosaari
2011-10-08 20:05                     ` Jason Hecker
2011-10-10 19:31                       ` Antti Palosaari
2011-10-10 20:27                         ` Malcolm Priestley
2011-10-10 21:06                           ` Jason Hecker
2011-10-16 20:26                             ` Malcolm Priestley [this message]
2011-10-16 21:18                               ` Jason Hecker

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=4e9b3dff.e766e30a.54ec.4d44@mx.google.com \
    --to=tvboxspy@gmail.com \
    --cc=crope@iki.fi \
    --cc=josu.lazkano@gmail.com \
    --cc=jwhecker@gmail.com \
    --cc=linux-media@vger.kernel.org \
    /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