public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <lkml@rtr.ca>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: Steven Toth <stoth@linuxtv.org>,
	linux-media@vger.kernel.org,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Regression 2.6.31: xc5000 no longer works with Myth-0.21-fixes branch
Date: Sun, 19 Jul 2009 11:12:01 -0400	[thread overview]
Message-ID: <4A6337C1.6080104@rtr.ca> (raw)
In-Reply-To: <829197380907190706i686fd1afwdca0d8be648129@mail.gmail.com>

Devin Heitmueller wrote:
> On Sun, Jul 19, 2009 at 9:15 AM, Mark Lord<lkml@rtr.ca> wrote:
>> Devin,
>>
>> Thanks for your good efforts and updates on the xc5000 driver.
>> But the version in 2.6.31 no longer works with mythfrontend
>> from the 0.21-fixes branch of MythTV.
..
> Also, Could you please install the latest v4l-dvb code using the
> directions at http://linuxtv.org/repo and see if the problem still
> occurs.  This will tell us if the problem is some patch that didn't
> make it upstream, and will make it easier for me to give you patches
> that provide more debug info.
..

Okay, I pulled in v4l-dvb-bdd711bbc07e, built/installed/rebooted,
and ended up with exactly the same behaviour.

So the good news is, nothing appears to have been left out in 2.6.31. :)

But still no really good clues to go on, other than this observation
from before:

>> The mythbackend (recording) program tunes/records fine with it,
>> but any attempt to watch "Live TV" via mythfrontend just locks
>> up the UI for 30 seconds or so, and then it reverts to the menus.
>>
>> I find that rather odd, as mythfrontend normally has very little
>> interaction with the tuner devices.  But it does try to read the
>> signal strength and quality from the tuner, so perhaps this is a
>> clue as to what has gone wrong?
..

Really, the mythfrontend DOES NOT DEAL WITH TUNERS directly,
leaving that to the mythbackend.  EXCEPT for when it wants to show
a signal strength/quality indication onscreen, which is done
when tuning to a new channel.

So it's got to be something on that pathway, I suspect,
but despite being a kernel developer, I'm not terribly
knowledgeable about V4L, DVB, or the MythTV internals.

Cheers

  parent reply	other threads:[~2009-07-19 15:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-19 13:15 Regression 2.6.31: xc5000 no longer works with Myth-0.21-fixes branch Mark Lord
2009-07-19 14:06 ` Devin Heitmueller
2009-07-19 14:45   ` Mark Lord
2009-07-19 18:25     ` Mark Lord
2009-07-19 15:12   ` Mark Lord [this message]
2009-07-19 15:53     ` Mark Lord
2009-07-19 22:42       ` Mark Lord
2009-07-20  1:12         ` Devin Heitmueller
2009-07-20  1:57           ` Mark Lord
2009-07-20  1:59             ` Devin Heitmueller
2009-07-21  2:38               ` Mark Lord
2009-07-20  2:18           ` Mark Lord
2009-07-20  2:32             ` Devin Heitmueller

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=4A6337C1.6080104@rtr.ca \
    --to=lkml@rtr.ca \
    --cc=dheitmueller@kernellabs.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=stoth@linuxtv.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