From: Jean Delvare <khali@linux-fr.org>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Old Video ML <video4linux-list@redhat.com>
Subject: Re: Conversion of vino driver for SGI to not use the legacy decoder API
Date: Fri, 27 Feb 2009 10:09:47 +0100 [thread overview]
Message-ID: <20090227100947.160abd0b@hyperion.delvare> (raw)
In-Reply-To: <200902270819.17862.hverkuil@xs4all.nl>
Hi Hans,
On Fri, 27 Feb 2009 08:19:17 +0100, Hans Verkuil wrote:
> On Friday 27 February 2009 01:47:42 Mauro Carvalho Chehab wrote:
> > After the conversion of Zoran driver to V4L2, now almost all drivers are
> > using the new API. However, there are is one remaining driver using the
> > video_decoder.h API (based on V4L1 API) for message exchange between the
> > bridge driver and the i2c sensor: the vino driver.
> >
> > This driver adds support for the Indy webcam and for a capture hardware
> > on SGI. Does someone have those hardware? If so, are you interested on
> > helping to convert those drivers to fully use V4L2 API?
> >
> > The SGI driver is located at:
> > drivers/media/video/vino.c
> >
> > Due to vino, those two drivers are also using the old API:
> > drivers/media/video/indycam.c
> > drivers/media/video/saa7191.c
> >
> > It shouldn't be hard to convert those files to use the proper APIs, but
> > AFAIK none of the current active developers has any hardware for testing
> > it.
>
> The conversion has already been done in my v4l-dvb-vino tree. I'm trying to
> convince the original vino author to boot up his Indy and test it, but he
> is not very interested in doing that. I'll ask him a few more times, but we
> may have to just merge my code untested. Or perhaps just drop it.
>
> Jean, I remember you mentioning that you wouldn't mind if the i2c-algo-sgi
> code could be dropped which is only used by vino. How important is that to
> you? Perhaps we are flogging a dead horse here and we should just let this
> driver die.
My rant was based on the fact that i2c-algo-sgi is totally SGI-specific
while i2c-algo-* modules are supposed to be generic abstractions that
can be reused by a variety of hardware. So i2c-algo-sgi should really be
merged into drivers/media/video/vino.c. But as it takes a SGI system to
build-test such a change, and I don't have one, I am reluctant to do
it. If we can find a tester for your V4L2 conversion then maybe the
same tester will be able to test my own changes.
But i2c-algo-sgi isn't a big problem per se, it doesn't block further
evolutions or anything like that, so if we can't find a tester and it
has to stay for a few more years, this really isn't a problem for me.
--
Jean Delvare
next prev parent reply other threads:[~2009-02-27 9:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-27 0:47 Conversion of vino driver for SGI to not use the legacy decoder API Mauro Carvalho Chehab
2009-02-27 7:19 ` Hans Verkuil
2009-02-27 9:09 ` Jean Delvare [this message]
2009-02-27 11:22 ` Mauro Carvalho Chehab
2009-02-27 11:53 ` Hans Verkuil
2009-02-27 12:12 ` Hans Verkuil
2009-02-27 13:59 ` Jean Delvare
2009-02-27 13:50 ` Douglas Schilling Landgraf
2009-02-27 15:37 ` Mauro Carvalho Chehab
2009-02-27 16:33 ` Douglas Schilling Landgraf
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=20090227100947.160abd0b@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.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