All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gianluca Gennari <gennarone@gmail.com>
To: Jim Darby <uberscubajim@gmail.com>,
	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 17:22:51 +0100	[thread overview]
Message-ID: <4F0F08DB.4050301@gmail.com> (raw)
In-Reply-To: <4F0DE0C2.5050907@gmail.com>

Il 11/01/2012 20:19, Jim Darby ha scritto:
> On 11/01/12 01:05, Antti Palosaari wrote:
>> [snip]
>> Also latest LinuxTV.org devel could be interesting to see. There is
>> one patch that changes em28xx driver endpoint configuration. But as
>> that patch is going for 3.3 it should not be cause of issue, but I
>> wonder if it could fix... Use media_build.git if possible.
> 
> Well, I built the kernel and installed it. Sadly I get entries of the
> form: "dvb_frontend_ioctl_legacy: doesn't know how to handle a DVBv3
> call to delivery system 0" which isn't what I was looking for. I guess
> there's a new API? It would appear this is from the set frontend call.
> 
> This is most annoying as I'd like to try out the newest code.
> 
> Is there a v3 to v3 transition document anywhere?
> 
> Best regards,
> 
> Jim.
> -- 
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

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

  reply	other threads:[~2012-01-12 16:22 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 [this message]
2012-01-12 16:35       ` Jim Darby
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=4F0F08DB.4050301@gmail.com \
    --to=gennarone@gmail.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@redhat.com \
    --cc=uberscubajim@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.