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: Josu Lazkano <josu.lazkano@gmail.com>,
	linux-media <linux-media@vger.kernel.org>
Subject: Re: [PATCH] af9013 frontend tuner bus lock
Date: Tue, 04 Oct 2011 22:54:28 +0100	[thread overview]
Message-ID: <4e8b8099.95d1e30a.4bee.0501@mx.google.com> (raw)
In-Reply-To: <CAATJ+fvHQgVMVp1uwxxci61qdCdxG89qK0ja-=jo4JRyGW52cw@mail.gmail.com>

On Wed, 2011-10-05 at 07:44 +1100, Jason Hecker wrote:
> I have had some luck with this patch.  I am still getting fouled
> recordings with tuner A but it's not consistent.  I have yet to
> ascertain if the problem occurs depending on the order of tuning to
> have both tuners recording different frquencies at the same time, ie
> Tuner B then Tuner A or vice versa.

Which Firmware are your using?

I am having some problems with firmware version:5.1.0
I have gone back to using firmware version:4.95.0 no problems at all.

> 
> Malcolm, did you say there was a MythTV tubing bug?  
Yes, sometimes tries to tune to same frequency as the other frontend for
a different channel.

> Do you have an
> URL for the bug if it has been reported?
No

> 
> I fear I might have a multi-layered problem - not only the Afatech
> tuners but perhaps some PCI issue too.  It doesn't help if MythTV
> isn't doing the right thing either.
> 
Yes, because it is also happening with other duo devices on Myth TV
0.24.1

So far Myth TV 0.23.0 on Kernel 2.6.35 seems consistently stable.

Regards

Malcolm


  reply	other threads:[~2011-10-04 21:54 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 [this message]
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
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=4e8b8099.95d1e30a.4bee.0501@mx.google.com \
    --to=tvboxspy@gmail.com \
    --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