Linux Media Controller development
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: linux-media@vger.kernel.org
Subject: Re: 2.6.32 regression: can't tune DVB with firedtv
Date: Sat, 17 Oct 2009 22:19:28 +0200	[thread overview]
Message-ID: <4ADA26D0.6010108@s5r6.in-berlin.de> (raw)
In-Reply-To: <4ADA149E.1070704@s5r6.in-berlin.de>

Stefan Richter wrote:
> I just switched from kernel 2.6.31 to 2.6.32-rc5.  Using kaffeine, I
> can't tune FireDTV-C and FireDTV-T boxes via the firedtv driver anymore.
> Electronic program guide data is still displayed though.
> 
> Under 2.6.31, I used firedtv at the same patchlevel as present in
> 2.6.32-rc5, hence I guess that it is a DVB core problem rather than a
> driver problem.
> 
> Any suggestions where to look for the cause?

>From looking at the git history of dvb-core, I think the cause is
"V4L/DVB (12685): dvb-core: check fe->ops.set_frontend return value",
but the actual bug is in the driver in
firedtv-fe.c::fdtv_set_frontend().  Let me boot back into 2.6.32-rc5 and
check my theory...

> (I am not subscribed to the list.)
-- 
Stefan Richter
-=====-==--= =-=- =---=
http://arcgraph.de/sr/

  reply	other threads:[~2009-10-17 20:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-17 19:01 2.6.32 regression: can't tune DVB with firedtv Stefan Richter
2009-10-17 20:19 ` Stefan Richter [this message]
2009-10-17 20:46   ` [PATCH] firedtv: fix regression: tuning fails due to bogus error return Stefan Richter
2009-11-13 10:09     ` Stefan Richter
2009-11-13 10:20       ` Stefan Richter
2009-10-17 20:24 ` 2.6.32 regression: can't tune DVB with firedtv Mario Bachmann

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=4ADA26D0.6010108@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --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