public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Kaiser <v4l@kaiser-linux.li>
To: kilgota@banach.math.auburn.edu
Cc: Kyle Guinn <elyk03@gmail.com>,
	Jean-Francois Moine <moinejf@free.fr>,
	Hans de Goede <hdegoede@redhat.com>,
	linux-media@vger.kernel.org
Subject: Re: RFC on proposed patches to mr97310a.c for gspca and v4l
Date: Thu, 05 Mar 2009 14:02:19 +0100	[thread overview]
Message-ID: <49AFCD5B.4050100@kaiser-linux.li> (raw)
In-Reply-To: <alpine.LNX.2.00.0903041248020.22500@banach.math.auburn.edu>

Hello Theodore

kilgota@banach.math.auburn.edu wrote:
> 
> 
> On Wed, 4 Mar 2009, Thomas Kaiser wrote:
> As to the actual contents of the header, as you describe things,
> 
> 0. Do you have any idea how to account for the discrepancy between
> 
>>>  From usb snoop.
>>> FF FF 00 FF 96 64 xx 00 xx xx xx xx xx xx 00 00
> and
>>> In Linux the header looks like this:
>>>
>>> FF FF 00 FF 96 64 xx 00 xx xx xx xx xx xx F0 00
> 
> (I am referring to the 00 00 as opposed to F0 00)? Or could this have 
> happened somehow just because these were not two identical sessions?

Doesn't remember what the differences was. The first is from Windoz 
(usbsnoop) and the second is from Linux.

> 
>>> 1. xx: don't know but value is changing between 0x00 to 0x07
> 
> as I said, this signifies the image format, qua compression algorithm in 
> use, or if 00 then no compression.

On the PAC207, the compression can be controlled with a register called 
"Compression Balance size". So, I guess, depending on the value set in 
the register this value in the header will show what compression level 
is set.

> 
>>> 2. xx: this is the actual pixel clock
> 
> So there is a control setting for this?

Yes, in the PAC207, register 2. (12 MHz divided by the value set).

> 
>>> 3. xx: this is changing according light conditions from 0x03 (dark) to
>>> 0xfc (bright) (center)
>>> 4. xx: this is changing according light conditions from 0x03 (dark) to
>>> 0xfc (bright) (edge)
>>> 5. xx: set value "Digital Gain of Red"
>>> 6. xx: set value "Digital Gain of Green"
>>> 7. xx: set value "Digital Gain of Blue"
> 
> Does anyone have any idea of how actually to use this information/ for 
> example, since a lot of cameras are reporting some kind of similar 
> looking information, does anyone know if there are any kinds of standard 
> scales for these entries? Just what are they supposed to signify, and 
> how exactly is one supposed to use such values, if they have been 
> presented? When I say "a lot of cameras," understand, I mean still 
> cameras as well as webcams, and cameras with a lot of different chipsets 
> in them, too. So this is a question whether there is any standard system 
> for the presentation of such data, and how it might constructively be 
> used in image processing. I have had questions about this kind of thing 
> for a long time, and I do not know where to look for the answers.

For the brightness, I guess, 0 means dark and 0xff completely bright 
(sensor is in saturation)?

Thomas


  reply	other threads:[~2009-03-05 13:02 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-17 19:09 MR97310A and other image formats Jean-Francois Moine
2009-02-17 19:35 ` Thomas Kaiser
2009-02-18  9:25   ` Jean-Francois Moine
2009-02-18 12:58     ` Thomas Kaiser
2009-02-18 19:17       ` Jean-Francois Moine
2009-02-17 19:43 ` Thomas Kaiser
2009-02-18  1:07 ` Kyle Guinn
2009-02-19  0:40   ` kilgota
2009-03-04  0:12   ` RFC on proposed patches to mr97310a.c for gspca and v4l kilgota
2009-03-04  2:50     ` Kyle Guinn
2009-03-04  5:21       ` kilgota
2009-03-04  8:41         ` Thomas Kaiser
2009-03-04  8:54           ` Thomas Kaiser
2009-03-04 19:01             ` kilgota
2009-03-05 13:02               ` Thomas Kaiser [this message]
2009-03-05 18:29                 ` kilgota
2009-03-05 19:19                   ` Thomas Kaiser
2009-03-05 19:45                     ` kilgota
2009-03-05 20:29                       ` Thomas Kaiser
2009-03-05 20:55                         ` kilgota
2009-03-05 20:51                           ` Thomas Kaiser
2009-04-15 23:59                 ` Some questions about mr97310 controls (continuing previous thread on mr97310a.c) Theodore Kilgore
2009-04-16 16:10                   ` Thomas Kaiser
2009-04-16 22:50                     ` Theodore Kilgore
2009-04-17  8:36                       ` Hans de Goede
2009-05-02  1:47                   ` Progress with the MR97310A "CIF" cameras Theodore Kilgore
2009-04-16  5:14           ` RFC on proposed patches to mr97310a.c for gspca and v4l Kyle Guinn
2009-04-16 18:22             ` Theodore Kilgore
2009-04-17  4:33               ` Kyle Guinn
2009-04-17 17:50                 ` Theodore Kilgore
2009-04-18  0:04                   ` Kyle Guinn
2009-04-18  0:43                     ` Theodore Kilgore
2009-04-21  1:18                     ` RFC on proposed patches to mr97310a.c for gspca and v4l (headers) Theodore Kilgore
2009-04-21  2:44                       ` Theodore Kilgore
2009-05-15 22:31             ` Preliminary results with an SN9C2028 camera Theodore Kilgore
2009-05-19  7:56               ` Hans de Goede
2009-05-19 18:18                 ` Theodore Kilgore
2009-03-04  8:39       ` RFC on proposed patches to mr97310a.c for gspca and v4l Hans de Goede
2009-03-04 18:46         ` kilgota
2009-03-05  1:33         ` Kyle Guinn
2009-03-05  7:01           ` Hans de Goede
2009-03-04  8:35     ` Hans de Goede
2009-03-05  2:49     ` Kyle Guinn
2009-03-05  4:34       ` kilgota
2009-03-05  5:54         ` Kyle Guinn
2009-03-05  6:47           ` kilgota
2009-03-05  7:00           ` Hans de Goede
2009-03-05 19:08             ` kilgota
2009-03-05 19:07               ` Hans de Goede
2009-03-05 20:42                 ` kilgota
2009-03-05 20:40                   ` Hans de Goede
2009-03-05 20:58                     ` kilgota
2009-03-06  1:21                       ` Kyle Guinn
2009-03-06  1:57                         ` kilgota
2009-03-28 22:42                         ` [PATCH] to add new camera in gspca/mr97310a.c Theodore Kilgore
2009-02-19 18:17 ` MR97310A and other image formats kilgota
2009-02-19 19:17   ` Thomas Kaiser
2009-02-19 21:54     ` kilgota
2009-02-19 22:45       ` Thomas Kaiser
2009-02-19 23:50         ` kilgota
2009-02-20  0:52           ` Thomas Kaiser
2009-02-20  1:32             ` kilgota
2009-02-20  8:00               ` Thomas Kaiser
2009-02-20 18:45                 ` kilgota
2009-02-20 19:05                   ` Thomas Kaiser
2009-02-20 20:26                     ` kilgota

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=49AFCD5B.4050100@kaiser-linux.li \
    --to=v4l@kaiser-linux.li \
    --cc=elyk03@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=kilgota@banach.math.auburn.edu \
    --cc=linux-media@vger.kernel.org \
    --cc=moinejf@free.fr \
    /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