public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Gregor Jasny <gjasny@googlemail.com>
To: abel@uni-bielefeld.de
Cc: linux-media@vger.kernel.org
Subject: Re: [libv4l] Bytes per Line
Date: Wed, 15 Feb 2012 23:30:17 +0100	[thread overview]
Message-ID: <4F3C31F9.8070000@googlemail.com> (raw)
In-Reply-To: <4F3BD50A.3010608@uni-bielefeld.de>

Hello,

On 2/15/12 4:53 PM, Robert Abel wrote:
> Basically, I found that libv4l and its conversion functions usually
> choose to ignore v4l2_pix_format.bytesperline, which seems to work out
> most of the time.

> I patched the issue for bayer => rgbbgr24 and will possibly fix it for
> bayer => yuv as well.
> 
> Is there a general understanding that v4l media drivers must not pad
> their data, or that libv4l is ignoring padding?
> I've worked with some webcams in the past and they all padded their
> data, so I'm wondering if assuming bytesperline = width was done on
> purpose and by design of out of necessity (speed..?) or if it just
> happened to work for most people?

As far as I understand the V4L2 spec the bytesperline != width is no
optional feature. If post your patches here I'll review them and add
them to the development tree.

Thanks,
Gregor

  reply	other threads:[~2012-02-15 22:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-15 15:53 [libv4l] Bytes per Line Robert Abel
2012-02-15 22:30 ` Gregor Jasny [this message]
2012-02-20 19:42   ` [PATCH][libv4l] Bytes per Line (was: [libv4l] Bytes per Line) Robert Abel
2012-02-25 17:19     ` [PATCH][libv4l] Bytes per Line Gregor Jasny
2012-02-26 12:15       ` Robert Abel

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=4F3C31F9.8070000@googlemail.com \
    --to=gjasny@googlemail.com \
    --cc=abel@uni-bielefeld.de \
    --cc=linux-media@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