mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Hubert Tonneau <hubert.tonneau@fullpliant.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: video4linux user land API concern
Date: Wed, 09 Nov 2005 12:31:14 +0000	[thread overview]
Message-ID: <1131539474.6540.10.camel@localhost.localdomain> (raw)
In-Reply-To: <05G2L0Z12@briare1.heliogroup.fr>

On Mer, 2005-11-09 at 10:26 +0000, Hubert Tonneau wrote:
> Any Video4Linux driver should support both native hardware color encoding
> (for maximum performances) and rgb (for maximum flexibility).
> 
> Requiering user land tools to be prepared to match the webcam native color
> encoding is poor kernel API design for several reasons:

The kernel API was designed on the basis that someone would one day have
the sense to write a nice user space library of formats. 

> . if new color models appear in new cameras, the current design will require
>   to map them anyway to some existing encodings not to break existing softwares,
>   so the end result will be even more confusing because the driver supporting a
>   non rgb encoding will not necessary mean that selecting the encoding is better
>   from the performances point of view

Many of the encodings done by hardware are extremely complicated and
tricky to unpack in kernel space. If a camera captures jpeg for example
you don't want in kernel jpeg decoders, let alone mpeg decoders etc


  reply	other threads:[~2005-11-09 12:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-09 10:26 Hubert Tonneau
2005-11-09 12:31 ` Alan Cox [this message]
2005-11-09 12:58 Hubert Tonneau
2005-11-09 13:36 ` linux-os (Dick Johnson)
2005-11-09 15:57 ` Alan Cox
2005-11-09 16:41 Hubert Tonneau

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=1131539474.6540.10.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=hubert.tonneau@fullpliant.org \
    --cc=linux-kernel@vger.kernel.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®