public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Luc Saillard <luc@saillard.org>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Luca Risolia <luca.risolia@studio.unibo.it>,
	linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk
Subject: Re: Linux 2.6.9-ac3
Date: Tue, 26 Oct 2004 07:29:51 +0200	[thread overview]
Message-ID: <20041026052951.GA4993@sd291.sivit.org> (raw)
In-Reply-To: <417D7C9D.8040409@tmr.com>

On Mon, Oct 25, 2004 at 06:22:21PM -0400, Bill Davidsen wrote:
> >Hmm..What about a common library finally?
> 
> That sounds like the eventual solution. A vendor to common format 
> conversion library, and with luck someone will be clever and let the 
> driver select it in a nice acceptable way. Thought: after open an ioctl 
> to tell you which conversion to use? The optimal mechanics are 
> inobvious, but I think the library is the right idea.

It's difficult to create a API that will be use for anyone. I try to be
application developper and want to grab an image from a device. I need to
know the list of webcams, the list of capture devices, ... and want to
display some sliders to control the camera like red,blue,gamma, ...
I want one format even if it's not supported by the driver.

What's the goal of our API ?
 - open,close, enumerate any device (usb,pci, firewire, ...) on the host.
 - convert any format (i'm YetAnotherCameraApp, want a RGB image, but the
   driver only support YUV)
 - can recognize special video source and activate some features.
 - can be use by any program or language ?
 - provide API to change red, blue, balance, gamma, ... without using ioctl.
   Perhaps like Alsa, provinding two levels: - a hardware interface, and a
   software interface.
 - provides some additionals features, like flipping image, change
   colorspace, use MMX ...
 - Please insert any features you want.

The ffmpeg project have already some source code to convert data between
various format without loosing to much information. (Think YUV to RGB, and
RGB to YUV410P).

When i'll finished to support v4l2 for the PWC driver, i'll try to begin a
little library to be use and a sample application. But this takes times ...

Luc

  reply	other threads:[~2004-10-26  5:38 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-22  8:13 Linux 2.6.9-ac3 Luca Risolia
2004-10-22  9:21 ` Luc Saillard
2004-10-22 12:30   ` Luca Risolia
2004-10-22 12:34     ` Xavier Bestel
2004-10-22 13:33       ` Luc Saillard
2004-10-22 14:22         ` Ronald S. Bultje
2004-10-22 14:38         ` David Weinehall
2004-10-22 14:15       ` Gergely Nagy
2004-10-22 13:16     ` Luc Saillard
2004-10-22 14:07       ` Luca Risolia
2004-10-22 14:10     ` Gerd Knorr
2004-10-22 15:51       ` Alan Cox
2004-10-22 18:14         ` Gerd Knorr
2004-10-23 13:41           ` Luca Risolia
2004-10-22 11:09 ` Alan Cox
2004-10-22 13:00   ` Luca Risolia
2004-10-22 15:49     ` Alan Cox
2004-10-23 14:54 ` Bill Davidsen
2004-10-23 17:36   ` Luca Risolia
2004-10-25 22:22     ` Bill Davidsen
2004-10-26  5:29       ` Luc Saillard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-10-21 23:08 Alan Cox
2004-10-22  0:59 ` Mark Lord
2004-10-22  1:18 ` Con Kolivas
2004-10-22  6:36 ` Jens Axboe

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=20041026052951.GA4993@sd291.sivit.org \
    --to=luc@saillard.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luca.risolia@studio.unibo.it \
    /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