public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gerd Knorr <kraxel@bytesex.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Luca Risolia <luca.risolia@studio.unibo.it>,
	Luc Saillard <luc@saillard.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	akpm@osdl.org
Subject: Re: Linux 2.6.9-ac3
Date: Fri, 22 Oct 2004 20:14:57 +0200	[thread overview]
Message-ID: <20041022181457.GB8067@bytesex> (raw)
In-Reply-To: <1098460282.19459.15.camel@localhost.localdomain>

On Fri, Oct 22, 2004 at 04:51:23PM +0100, Alan Cox wrote:
> On Gwe, 2004-10-22 at 15:10, Gerd Knorr wrote:
> > 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).
> 
> The pwc formats look like they can be done a lot faster in MMX, which
> argues for some format of user space exposure and a set of format idents
> for "vendor foo, protocol 0" etc

We'll also need a libv4l2-vendorstuff then (*one* libary for *all* these
vendor formats), otherwise that isn't going to work.  If someone is
willing to create & maintain such a library -- fine with me.  I'll
happily hand out v4l2 vendor format ID's and agree do drop stuff from
kernel space then.  But asking the apps to decode stuff in userspace
without providing a way to do so isn't a good idea.

  Gerd

-- 
return -ENOSIG;

  reply	other threads:[~2004-10-22 18:46 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 [this message]
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=20041022181457.GB8067@bytesex \
    --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