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 majord...@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 -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
