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 00:20:59 +0100	[thread overview]
Message-ID: <47BCB5DB.8000800@kaiser-linux.li> (raw)
In-Reply-To: <175f5a0f0802201441n5ea7bb58rdfa70663799edcad@mail.gmail.com>

H. Willstrand wrote:
> On Wed, Feb 20, 2008 at 11:12 PM, Thomas Kaiser
> <linux-dvb@kaiser-linux.li> wrote:
>> Daniel Glöckner wrote:
>>  > On Wed, Feb 20, 2008 at 10:11:36PM +0100, Thomas Kaiser wrote:
>>  >> H. Willstrand wrote:
>>  >>> Well, it can go ugly if one piece of hardware supports several "raw"
>>  >>> formats, they need to be distinct. And in the end of the day the V4L2
>>  >>> drivers might consist of several identical "raw" formats which then
>>  >>> aren't consolidated.
>>  >> I don't really understand what you try to say here.
>>  >
>>  > Think about an analog TV card.
>>  > In the future there might be one where RAW could mean either sampled
>>  > CVBS or sampled Y/C. The card may be able to provide the Y/C in planar
>>  > and packed format. It may be capable of 16 bit at 13.5Mhz and 8 bit at
>>  > 27Mhz, ...
>>  >
>>  > If we start defining raw formats, there needs to be a way to choose
>>  > between all those variants without defining lots of additional pixel
>>  > formats.
>>  >
>>  > Maybe an ioctl VIDIOC_S_RAW where one passes a number to select the
>>  > variant. An application would then have to check the driver and version
>>  > field returned by VIDIOC_QUERYCAP to determine the number to pass. This
>>  > way drivers may freely assign numbers to their raw formats.
>>
>>  Yeh, That's something I mean.
>>
> 
> Okay, suppose we have pixel formats and raw formats. Comparing with
> digital cameras raw usually means non processed image in a proprietary
> format. What do we mean here?

I talk about webcams. But It looks like you don't get the point.
A ISOC stream can be received, then we forward this to user space! That's it.

This has nothing to do with pixel format, just deliver  the stream from the cam 
to user space, That's all what I won't.
I think raw means raw, "not manipulated"! Oder in Deutsch Roh equals raw, which 
means "not touched".

You get the point?

I just would like to have a way to get the stream "as it is" to user spcae.

Thomas


-- 
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-20 23:21 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                   ` Thomas Kaiser [this message]
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                           ` V4L2_PIX_FMT_RAW Thomas Kaiser
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=47BCB5DB.8000800@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