[lkml]   [2007]   [Oct]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [v4l-dvb-maintainer] [GIT PATCHES] V4L/DVB changes for 2.6.24
On 10/11/07, Pádraig Brady <> wrote:
> 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.
> 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):
> > 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.

The tvp5150 as well as several other drivers have some slight changes
in it to get some devices work.
My motivation behind it is that since I don't agree with certain
linuxtv development paths and it makes it alot easier to handle
prewritten code from some companies.

> Markus, please do the right thing and just merge your code!
> (and please don't reply this giving reasons you won't/can't do this).

Merge the bridging code and the issue is done, the other guys should
go their own paths with their own drivers if they want so. Time will
show what will be better in the end.
There are not so many devices out there which have newer requirements,
although the em28xx is a good example for at least one device which
doesn't fit.

If someone's looking for another disagreement between developers
(which my code is not part of):

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2007-10-11 13:43    [W:0.048 / U:26.136 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site