From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: Adrian Bunk <bunk@stusta.de>,
v4l-dvb-maintainer@linuxtv.org, linux-kernel@vger.kernel.org
Subject: Re: [v4l-dvb-maintainer] [2.6 patch] VIDEO_V4L1 shouldn't be user-visible
Date: Fri, 30 Jun 2006 16:14:34 -0300 [thread overview]
Message-ID: <1151694874.2006.7.camel@praia> (raw)
In-Reply-To: <9e4733910606291759t140e1ea7yf14cca699988cd50@mail.gmail.com>
Em Qui, 2006-06-29 às 20:59 -0400, Jon Smirl escreveu:
> On 6/29/06, Mauro Carvalho Chehab <mchehab@infradead.org> wrote:
> > Also, on V4L side, the V4L1 api is stopping V4L development. V4L API 2
> > is already at kernel since the beginning of kernel 2.6 series, and fixes
> > several flaws at the old api (V4L1 API were designed on 2.1 series).
> > Still now, most applications still implement only V4L1, and people do
> > submit newer v4l1 drivers to us.
> >
> > We do really go ahead, making V4L2 API the standard.
>
> I don't think anyone would complain about dropping V4L1 if the people
> pushing V4L2 were to port the 25 or so drivers that depend on V4L1 to
> the V4L2 API.
We are working on it. The issue will be someone to test all those
drivers for the obsolete hardwares.
> As long as those V4L1 dependent drivers are around
> people are going to want to keep using V4L1. You may want to consider
> building some in-kernel compatibility APIs into V4L2 to make porting
> those drivers easier.
Most of changes are just trivial. Just one will requre more work, since
it is related to newer mmap methods on V4L2.
>
Cheers,
Mauro.
prev parent reply other threads:[~2006-06-30 19:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-29 19:21 [2.6 patch] VIDEO_V4L1 shouldn't be user-visible Adrian Bunk
2006-06-29 20:18 ` [v4l-dvb-maintainer] " Mauro Carvalho Chehab
2006-06-29 21:08 ` Adrian Bunk
2006-06-29 21:43 ` Mauro Carvalho Chehab
2006-06-30 0:59 ` Jon Smirl
2006-06-30 19:14 ` Mauro Carvalho Chehab [this message]
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=1151694874.2006.7.camel@praia \
--to=mchehab@infradead.org \
--cc=bunk@stusta.de \
--cc=jonsmirl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=v4l-dvb-maintainer@linuxtv.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.