From: Malcolm Priestley <tvboxspy@gmail.com>
To: Antti Palosaari <crope@iki.fi>
Cc: Jason Hecker <jwhecker@gmail.com>,
Josu Lazkano <josu.lazkano@gmail.com>,
linux-media <linux-media@vger.kernel.org>
Subject: Re: [PATCH] af9013 Extended monitoring in set_frontend.
Date: Mon, 10 Oct 2011 21:27:30 +0100 [thread overview]
Message-ID: <1318278450.16238.15.camel@localhost> (raw)
In-Reply-To: <4E93481F.8010205@iki.fi>
On Mon, 2011-10-10 at 22:31 +0300, Antti Palosaari wrote:
> On 10/08/2011 11:05 PM, Jason Hecker wrote:
> >> Which kernels are you all running?
> >
> > 2.6.38-11-generic #50-Ubuntu SMP (Mythbuntu 11.04)
>
> Have you tried other USB-cable or connect it directly to the mobo USB port.
>
> I just used one af9015 + 2x mxl5007t and got some streaming corruptions.
> I was WTF. Switched to af9015 + 2x mxl5005s since it is device I usually
> have used. Still errors. Then I commented out remote controller polling
> and all status polling from drivers. Still some stream corruptions.
> Finally I realized I have other USB-cable than normally. Plugged device
> directly to the mobo USB and now both tuners are streaming same time
> without errors.
I have just been testing af9015s both 399U and single, along with other
devices on Mythbuntu 11.04 on 2.6.38-11 and getting the same corruption.
Playing with Kaffeine or Mplayer all the devices are fine on the same
system.
This is very strange!
At the moment, I am going step by step what Myth TV is sending to the
devices.
Regards
Malcolm
next prev parent reply other threads:[~2011-10-10 20:27 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 [this message]
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=1318278450.16238.15.camel@localhost \
--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