From: Jim Darby <uberscubajim@gmail.com>
To: gennarone@gmail.com
Cc: linux-media@vger.kernel.org, Mauro Carvalho Chehab <mchehab@redhat.com>
Subject: Re: Possible regression in 3.2 kernel with PCTV Nanostick T2 (em28xx, cxd2820r and tda18271)
Date: Thu, 12 Jan 2012 16:35:59 +0000 [thread overview]
Message-ID: <4F0F0BEF.8040002@gmail.com> (raw)
In-Reply-To: <4F0F08DB.4050301@gmail.com>
On 12/01/12 16:22, Gianluca Gennari wrote:
> Hi Jim,
> you spotted a regression in the latest media_build release from
> 11/01/2012.
> I had the same problem here:
>
> "dvb_frontend_ioctl_legacy: doesn't know how to handle a DVBv3 call to
> delivery system 0"
>
> with 3 totally different sticks (em28xx, dvb-usb, as102).
>
> Everything was working fine with media_build drivers from 08/01/2011, so
> the problem originates from a patch committed in the last few days.
>
> In fact, I reverted this patch:
>
> http://patchwork.linuxtv.org/patch/9443/
>
> and Kaffeine started working again with all my DVB-T sticks.
>
> Best regards,
> Gianluca
I think that we need to be careful about two different problems here.
The first is the regression that I originally reported. In this case the
device stops sending data after a variable period of time and we get to
miss the end of the programme that we're watching.
The second, which is the one that Gianluca has spotted as well, is that
there seems to be some form of API change in the latest linux-media
which is causing kaffeine to stop working.
I'm still unsure about the first. It might be a 32/64-bit problem (based
on evidence from Simon Jones), it might be flaky hardware or it might be
a real problem. I'm planning to build the 3.2.0 kernel (minus the
linux-media patches) for 64-bit on different hardware and see what happens.
As for the second I suspect it might be a kaffeine problem. It might
just need recompiling with the new headers or it might need some work on
it. I'll investigate that after I've solved the first regression.
Pedant mode: the kaffeine problem isn't really a regression as such.
It's more of a API versioning issue. More on this later.
Hope this helps,
Jim.
next prev parent reply other threads:[~2012-01-12 16:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 13:28 Possible regression in 3.2 kernel with PCTV Nanostick T2 (em28xx, cxd2820r and tda18271) Jim Darby
2012-01-10 13:54 ` Steven Toth
2012-01-10 23:22 ` Jim Darby
2012-01-11 0:01 ` Steven Toth
2012-01-11 0:34 ` Andy Walls
2012-01-11 1:05 ` Antti Palosaari
2012-01-11 11:30 ` Jim Darby
2012-01-11 19:19 ` Jim Darby
2012-01-12 16:22 ` Gianluca Gennari
2012-01-12 16:35 ` Jim Darby [this message]
2012-01-12 17:13 ` Simon Jones
2012-01-12 17:34 ` Gianluca Gennari
2012-01-13 11:21 ` Mauro Carvalho Chehab
2012-01-13 11:45 ` Gianluca Gennari
2012-01-13 13:50 ` [PATCH] [media] dvb-core: preserve the delivery system at cache clear Mauro Carvalho Chehab
2012-01-13 16:04 ` Gianluca Gennari
2012-01-14 0:00 ` Jim Darby
2012-01-14 14:51 ` Mauro Carvalho Chehab
2012-01-13 13:09 ` Possible regression in 3.2 kernel with PCTV Nanostick T2 (em28xx, cxd2820r and tda18271) Jim Darby
2012-01-13 14:24 ` Gianluca Gennari
2012-01-12 14:29 ` Simon Jones
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=4F0F0BEF.8040002@gmail.com \
--to=uberscubajim@gmail.com \
--cc=gennarone@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).