> Aidan Thornton wrote:
> > I looked at this recently, and I'm not sure the core em28xx code was
> > really that different (at least, pre-userspace). Most of the core
> > changes seemed to be related to Markus' driver having (semi-working)
> > VBI support. I haven't tried this recently; I disabled it a while back
> > because it had a bug that caused a kernel panic half the time when
> > attempting to record something with MythTV.
> >
> > The in-kernel driver looks mostly sound, though I can't test it
> > myself. (One other interesting thing that was added in Markus' driver
> > is various v4l1 ioctls, which may be useful to some people.)
>
> Yes, for example VLC doesn't support v4l2 yet.
> Here is a patch I back ported to 2.6.17 last year.
>
http://www.pixelbeat.org/patches/linux-2.6.17-em28xx-v4l1.diff
> I didn't try to get it merged as I thought Markus would do it,
> but looks like that's unlikely now.
>
> Also here is a patch to allow shared access to the video device
> (so you can have a separate tuner program to VLC for example):
>
http://www.pixelbeat.org/patches/linux-2.6.17-em28xx-shared.diff
>
> > Incidentally, I notice you appear to be developing userspace drivers
> > for the tvp5150 and zl10353. Is that really necessary?
>
> It is necessary if Markus wants to stop people merging code back from
> his in-kernel driver fork. Call me a cynic, but I'm confused about Markus'
> motives in all this.
>