public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gerd Knorr <kraxel@bytesex.org>
To: Luca Risolia <luca.risolia@studio.unibo.it>
Cc: Luc Saillard <luc@saillard.org>,
	linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk,
	akpm@osdl.org
Subject: Re: Linux 2.6.9-ac3
Date: 22 Oct 2004 16:10:04 +0200	[thread overview]
Message-ID: <878y9y269v.fsf@bytesex.org> (raw)
In-Reply-To: <20041022143036.462742ca.luca.risolia@studio.unibo.it>

Luca Risolia <luca.risolia@studio.unibo.it> writes:

> If it ever happens that this driver is accepted, be also prepared to
> accept patches adding decompression and colorspace conversions for
> every video driver I am aware of, starting from the ones I have already
> written to the ones I'll submit in the future.

Uhm, colorspace conversions and decompression are two different
problems.  Drivers should support at least one of the v4l2 standard
formats.  They might have to do decompression in kernel space to to
that.

colorspace conversion should be the job of the userspace app, I think
everyone agrees on that.  Same goes for any *standard* compression
formats, i.e. webcams which simply use jpeg for example (where the
driver can say "Hey, I'll give you V4L2_PIX_FMT_JPEG" and the decoding
can easily be done using libjpeg.

The corner case are the vendor-specific compressions.  IMHO it doesn't
make much sense to attempt to implement every strange format some
engineer invented in every v4l2 application.  Especially if there is
no free implementation of it (which is the reason the non-gpl pwcx
module was created IIRC).

  Gerd

-- 
return -ENOSIG;

  parent reply	other threads:[~2004-10-22 14:22 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 [this message]
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=878y9y269v.fsf@bytesex.org \
    --to=kraxel@bytesex.org \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luc@saillard.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