From: Mario Bachmann <grafgrimm77@gmx.de>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: linux-media@vger.kernel.org
Subject: Re: 2.6.32 regression: can't tune DVB with firedtv
Date: Sat, 17 Oct 2009 22:24:37 +0200 [thread overview]
Message-ID: <20091017222437.0cbbe897@x2.grafnetz> (raw)
In-Reply-To: <4ADA149E.1070704@s5r6.in-berlin.de>
Am Sat, 17 Oct 2009 21:01:50 +0200
schrieb Stefan Richter <stefanr@s5r6.in-berlin.de>:
> Hi list,
>
> 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?
>
> (I am not subscribed to the list.)
Hi there,
perhaps it is related:
with kernel 2.6.30.8 my "TwinhanDTV USB-Ter USB1.1 / Magic Box I"
worked.
Now with kernel 2.6.32-rc3 (and 2.6.31.1) the modules seems to be
loaded fine, but tzap/kaffeine/mplayer can not tune to a channel.
i think the cause must be here:
/usr/src/linux-2.6.32-rc3/drivers/media/dvb/dvb-usb/dibusb-common.c
line 136 to line 146
i changed this hole section to the version of 2.6.30.8 and it works
again.
Mario
prev parent reply other threads:[~2009-10-17 20:24 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
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 ` Mario Bachmann [this message]
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=20091017222437.0cbbe897@x2.grafnetz \
--to=grafgrimm77@gmx.de \
--cc=linux-media@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
/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