On Wed, Sep 9, 2009 at 9:09 PM, Devin Heitmueller<dheitmueller@xxxxxxxxxxxxxx> wrote: > On Wed, Sep 9, 2009 at 3:02 PM, Markus Rechberger<mrechberger@xxxxxxxxx> wrote: >> this is not true my old driver which is not available anymore did not >> ship any other modules aside the em28xx driver itself. >> This is a video4linux issue and has nothing to do with it. >> >> Best Regards, >> Markus >> > > Hello Marks, > > While it is true that your driver did not include anything other than > em28xx, I assume it is compiled against a certain set of v4l2 headers, > and if those headers change (such as changes to data structures), then > the em28xx modules you distributed would not work with that version of > the v4l2 modules. I stopped the work at around Oct last year, 2.6.27 is the latest kernel which is supposed to be supported with it. Although since there are some bad bugs in it which I've been told by the manufacturer afterwards I do not recommend to use it either it shortens the lifetime of most devices... Best is to stick with windows unless the manufacturer and chipdesigners support a driver. WARNING: Error inserting videobuf_core (/lib/modules/2.6.30-tuxonice- r5/kernel/drivers/media/video/videobuf-core.ko): Invalid module format this is something that cannot be caused by the em28xx work, it's any other messy issue with the v4l2 kernel API. Markus > If he wants to use your driver, I would assume he would need to > reinstall the stock kernel (overwriting whatever locally built version > of v4l-dvb he previously installed). > > Cheers, > > Devin > > -- > Devin J. Heitmueller - Kernel Labs > http://www.kernellabs.com > -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
