From: Richard Atterer <richard@2008.atterer.net>
To: video4linux-list@redhat.com
Subject: Re: pixel count doubts
Date: Fri, 16 May 2008 16:35:37 +0200 [thread overview]
Message-ID: <20080516143537.GA7963@fluff.lan> (raw)
In-Reply-To: <a5eaedfa0805160656t29d2858ao3c1c81469b87b0af@mail.gmail.com>
On Fri, May 16, 2008 at 07:26:27PM +0530, Veda N wrote:
> Hi,
> I am trying to write a camera sensor driver.
>
> The sensor documents says that -
> For the resolution VGA, The pixel count is 640x480x3.
>
> I did not understand what is meant by x3 in pixel count.
>
> Usually it is 60x480. The number of bytes per pixel is 2.
>
> Does this mean that instead of 2 bytes per pixel. it is 3 bytes?
There isn't really enough information to tell, but probably yes.
Note that it is often the case that a claimed sensor resolution of, say,
640x480 means that the _Bayer pattern_ resolution is 640x480 - in other
words, there are that many pixels, but each pixel is only for one of the
colours red, green or blue, and further interpolation is necessary to get a
640x480 RGB picture.
So the "640x480x3" /could/ mean "3 subpixels for each image pixel", but I
strongly doubt it; Foveon sensors are fairly rare in webcams. ;-)
> How should i account this pixel count in my driver.
> How much should be bytesperline and sizeimage
> How should i account this in my application as well.
I think you will have to play around to see what the exact data format is.
Cheers,
Richard
--
__ _
|_) /| Richard Atterer | GnuPG key: 888354F7
| \/¯| http://atterer.net | 08A9 7B7D 3D13 3EF2 3D25 D157 79E6 F6DC 8883 54F7
¯ '` ¯
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next prev parent reply other threads:[~2008-05-16 14:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 13:56 pixel count doubts Veda N
2008-05-16 14:35 ` Richard Atterer [this message]
2008-05-16 14:35 ` Roger Oberholtzer
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=20080516143537.GA7963@fluff.lan \
--to=richard@2008.atterer.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.