From: "Pádraig Brady" <P@draigBrady.com>
To: Aidan Thornton <makosoft@googlemail.com>
Cc: Markus Rechberger <mrechberger@gmail.com>,
Chuck Ebbert <cebbert@redhat.com>,
video4linux-list@redhat.com, linux-kernel@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-dvb-maintainer@linuxtv.org,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [v4l-dvb-maintainer] [GIT PATCHES] V4L/DVB changes for 2.6.24
Date: Thu, 11 Oct 2007 11:42:32 +0100 [thread overview]
Message-ID: <470DFE18.7010001@draigBrady.com> (raw)
In-Reply-To: <c8b4dbe10710110250w10ddfc0du6ae4b6bb95cb2d2f@mail.gmail.com>
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.
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).
Pádraig.
next prev parent reply other threads:[~2007-10-11 11:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-10 21:50 [GIT PATCHES] V4L/DVB changes for 2.6.24 Mauro Carvalho Chehab
2007-10-10 23:00 ` [v4l-dvb-maintainer] " Markus Rechberger
2007-10-10 23:24 ` Markus Rechberger
2007-10-10 23:35 ` Chuck Ebbert
2007-10-11 4:59 ` Markus Rechberger
2007-10-11 9:50 ` Aidan Thornton
2007-10-11 10:42 ` Pádraig Brady [this message]
2007-10-11 11:39 ` Markus Rechberger
2007-10-10 23:36 ` Andrew Morton
2007-10-11 5:09 ` Markus Rechberger
2007-10-11 5:32 ` Andrew Morton
2007-10-11 5:50 ` Markus Rechberger
2007-10-11 7:11 ` Dave Jones
2007-10-14 10:40 ` Markus Rechberger
2007-10-14 11:12 ` Hans Verkuil
2007-10-14 11:28 ` Markus Rechberger
2007-10-14 20:49 ` Johannes Stezenbach
2007-10-10 23:42 ` Linus Torvalds
2007-10-11 4:50 ` Markus Rechberger
2007-10-11 6:08 ` Aurelien Jarno
2007-10-11 6:31 ` Markus Rechberger
2007-10-11 9:33 ` Marcel Siegert
2007-10-11 10:20 ` Markus Rechberger
2007-10-11 12:54 ` Marcel Siegert
2007-10-11 13:01 ` Markus Rechberger
2007-10-11 13:22 ` Aurelien Jarno
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=470DFE18.7010001@draigBrady.com \
--to=p@draigbrady.com \
--cc=akpm@linux-foundation.org \
--cc=cebbert@redhat.com \
--cc=linux-dvb-maintainer@linuxtv.org \
--cc=linux-kernel@vger.kernel.org \
--cc=makosoft@googlemail.com \
--cc=mchehab@infradead.org \
--cc=mrechberger@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=video4linux-list@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox