public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Kaiser <linux-dvb@kaiser-linux.li>
To: "H. Willstrand" <h.willstrand@gmail.com>
Cc: Linux and Kernel Video <video4linux-list@redhat.com>
Subject: Re: V4L2_PIX_FMT_RAW
Date: Thu, 21 Feb 2008 13:00:08 +0100	[thread overview]
Message-ID: <47BD67C8.5000305@kaiser-linux.li> (raw)
In-Reply-To: <175f5a0f0802210110k11dc73f6pbbdd7100c1ca8fdb@mail.gmail.com>

H. Willstrand wrote:
> On Thu, Feb 21, 2008 at 2:20 AM, Daniel Glöckner <daniel-gl@gmx.net> wrote:
>> On Thu, Feb 21, 2008 at 01:02:39AM +0100, H. Willstrand wrote:
>>  > What's the problem with having a name of the formalized data in the
>>  > video stream? ie raw do not mean undefined.
>>
>>  I thought you wanted to avoid having to define V4L2_PIX_FMT_x for an
>>  exploding number of proprietary formats that are quite similar but still
>>  incompatible. It makes sense for formats that are used by more than one
>>  driver.
> 
> Correct, the number of unique pixel formats should be kept down.
> Again, comparing with digital cameras there are >200 proprietary
> formats and there is a "clean-up" on-going where the "market" is
> aiming for a OpenRAW.
> 
> However, by declaring a generic RAW format (which is then driver
> specific) doesn't help the user mode app developers. Calling a
> multitude of libraries to see if you get lucky might not be a good
> idea.
> 
> Still, I'm suspectious about the definition "raw" used here.
> RAW should mean unprocessed image data:
> * no white balance adjustment
> * no color saturation adjustments
> * no contrast adjustments
> * no sharpness improvements
> * no compression with loss

Yes, raw means "as it is" no stripping, decoding  or removing of SOF headers are 
done in the driver. May be V4L2_PIX_FMT_AII (AII -> As It Is) is the better name?

> 
> So, by looking for similarities in the "raw" formats where available
> there should be a potential to consolidate them.
> 
>>
>>  > I don't see how separate RAW ioctl's will add value to the V4l2 API,
>>  > it fits into the current API.
>>
>>  Yes, it does. Each driver having multiple raw formats just needs a
>>  private control id to select one.
>>
> I was more thinking about the VIDIOC_S_RAW stuff, a VIDIOC_S_FMT
> should do the job.
> I.e. I think there should be strong reasons to break V4L2 API behavior.
> 
> Harri


-- 
http://www.kaiser-linux.li

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

  reply	other threads:[~2008-02-21 12:00 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-20 19:25 V4L2_PIX_FMT_RAW Thomas Kaiser
     [not found] ` <175f5a0f0802201208u4bca35afqc0291136fe2482b@mail.gmail.com>
     [not found]   ` <47BC8BFC.2000602@kaiser-linux.li>
     [not found]     ` <175f5a0f0802201232y6a1bfc53u4fe92fede3abcb34@mail.gmail.com>
     [not found]       ` <47BC90CA.1000707@kaiser-linux.li>
     [not found]         ` <175f5a0f0802201254q7dc96190k35caafe9ba7d3274@mail.gmail.com>
2008-02-20 21:11           ` V4L2_PIX_FMT_RAW Thomas Kaiser
2008-02-20 21:41             ` V4L2_PIX_FMT_RAW H. Willstrand
2008-02-20 22:02               ` V4L2_PIX_FMT_RAW Thomas Kaiser
2008-02-20 21:58             ` V4L2_PIX_FMT_RAW Daniel Glöckner
2008-02-20 22:12               ` V4L2_PIX_FMT_RAW Thomas Kaiser
2008-02-20 22:41                 ` V4L2_PIX_FMT_RAW H. Willstrand
2008-02-20 23:20                   ` V4L2_PIX_FMT_RAW Thomas Kaiser
2008-02-21  0:02                     ` V4L2_PIX_FMT_RAW H. Willstrand
2008-02-21  1:20                       ` V4L2_PIX_FMT_RAW Daniel Glöckner
2008-02-21  9:10                         ` V4L2_PIX_FMT_RAW H. Willstrand
2008-02-21 12:00                           ` Thomas Kaiser [this message]
2008-02-21 12:43                             ` V4L2_PIX_FMT_RAW Daniel Glöckner
2008-02-21 12:48                               ` V4L2_PIX_FMT_RAW H. Willstrand
2008-02-21 12:43                             ` V4L2_PIX_FMT_RAW H. Willstrand
2008-02-21 18:55                               ` V4L2_PIX_FMT_RAW Thomas Kaiser
2008-02-21 20:12                                 ` V4L2_PIX_FMT_RAW H. Willstrand
2008-02-21 20:40                                   ` V4L2_PIX_FMT_RAW Thomas Kaiser
2008-02-21 21:06                                     ` V4L2_PIX_FMT_RAW H. Willstrand
2008-02-21 21:29                                       ` V4L2_PIX_FMT_RAW Thomas Kaiser
2008-02-21 21:40                                         ` V4L2_PIX_FMT_RAW H. Willstrand
2008-02-21 22:03                                     ` V4L2_PIX_FMT_RAW Laurent Pinchart
2008-02-21 22:22                                       ` V4L2_PIX_FMT_RAW Thomas Kaiser
2008-02-22  9:38                                         ` V4L2_PIX_FMT_RAW Thierry Merle
2008-02-22 12:22                                           ` V4L2_PIX_FMT_RAW Thomas Kaiser
2008-02-23  0:15                                           ` V4L2_PIX_FMT_RAW H. Willstrand
2008-02-23 19:51                                             ` V4L2_PIX_FMT_RAW Thierry Merle
2008-02-24 21:46                                               ` V4L2_PIX_FMT_RAW Laurent Pinchart
2008-02-21 21:59                                 ` V4L2_PIX_FMT_RAW Laurent Pinchart
2008-02-21 22:28                                   ` V4L2_PIX_FMT_RAW Thomas Kaiser

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=47BD67C8.5000305@kaiser-linux.li \
    --to=linux-dvb@kaiser-linux.li \
    --cc=h.willstrand@gmail.com \
    --cc=video4linux-list@redhat.com \
    /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