mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Luca Risolia <luca.risolia@studio.unibo.it>
To: Luc Saillard <luc@saillard.org>
Cc: linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk, akpm@osdl.org
Subject: Re: Linux 2.6.9-ac3
Date: Fri, 22 Oct 2004 16:07:03 +0200	[thread overview]
Message-ID: <20041022160703.1ca025f4.luca.risolia@studio.unibo.it> (raw)
In-Reply-To: <20041022131639.GC16963@sd291.sivit.org>

On Fri, 22 Oct 2004 15:16:39 +0200
Luc Saillard <luc@saillard.org> wrote:

> On Fri, Oct 22, 2004 at 02:30:36PM +0200, Luca Risolia wrote:
> > Either port the driver to V4L2, which handles decompression stuff well,

> no, it only provide a number (that needs to be reserved) to the user API, but
> if the user API doesn't exist, application will not support your camera. I
> can provide a .c and .h for the decompression module, but since the
> decompression table depend of the resolution,quality choose by the webcam
> (thinks as quality fine,normal,low). I can't provide with v4l2 a generic
> control for this.

Modify the V4L2 API by adding the correct generic interface.

> > or provide a separate downloadble GPL'ed module. Other drivers in the
> > mainline kernel observe this rule; the pwc case is not an exception.

> The driver, in it's current status, is GPL. Can you give me some examples
> about "other drivers" ?

At least two: w9968cf, ov511.

> > Also, this matter has been already discussed many times in the v4l
> > mailing list: no video decompression at all in kernel space, even if
> > *optional* through an *indipendent* module.

> It's easy for you to say that, because your driver returns a native format.
> Since nobody cares about webcam, and stream compressed, if today, i remove
> the table in the module, i'll wait one year ? two years for app that support
> my webcam ?

No, it's not easy for me to say that: the w9968cf driver is not really usefull
without the optional module available *outside* the kernel, since native UYVY
is not supported in userland at all. Furthermore, having had a separate module
for these things, is one more reason why none never patched any of the existing
applications.

Another example: sometime ago I had to patch the V4L2 API to add Bayer format
support to V4L2. This saved me from implementing colorspace conversion in the
sn9c102 driver. The patch was *one line* long and one of its results is that
now someone is working on gnomemeeting/pwlib to implement Bayer-to-* color
conversions that will make thousands of webcams work on Linux with this
application.

Regards,
	Luca Risolia

  reply	other threads:[~2004-10-22 13:58 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-22  8:13 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 [this message]
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
  -- 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=20041022160703.1ca025f4.luca.risolia@studio.unibo.it \
    --to=luca.risolia@studio.unibo.it \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luc@saillard.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®