linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: workshop-2011@linuxtv.org, linux-media <linux-media@vger.kernel.org>
Subject: Re: V4L2 API ambiguities: workshop presentation
Date: Fri, 17 Aug 2012 14:48:23 +0200	[thread overview]
Message-ID: <502E3D97.3090502@redhat.com> (raw)
In-Reply-To: <201208171235.58094.hverkuil@xs4all.nl>

Hi,

On 08/17/2012 12:35 PM, Hans Verkuil wrote:
> Hi all,
>
> I've prepared a presentation for the upcoming workshop based on my RFC and the
> comments I received.
>
> It is available here:
>
> http://hverkuil.home.xs4all.nl/presentations/v4l2-workshop-2012.odp
> http://hverkuil.home.xs4all.nl/presentations/v4l2-workshop-2012.pdf
>
> Attendees of the workshop: please review this before the workshop starts. I
> want to go through this list fairly quickly (particularly slides 1-14) so we
> can have more time for other topics.

A note on the Pixel Aspect Ratio from me, since I won't be attending:

I'm not sure if having a VIDIOC_G_PIXELASPECT is enough, it will work
to get the current mode, but not for enumerating. Also it will not
work with TRY_FMT, that is one cannot find out the actual pixelaspect
until after a S_FMT. As mentioned in previous mail I think at a minimum
the results of ENUM_FRAMESIZES should contain the pixel aspect per framesize,
there is enough reserved space in the relevant structs to make this happen

Regards,

Hans

  reply	other threads:[~2012-08-17 12:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-17 10:35 V4L2 API ambiguities: workshop presentation Hans Verkuil
2012-08-17 12:48 ` Hans de Goede [this message]
2012-08-17 12:55   ` Hans Verkuil
2012-08-17 12:57     ` [Workshop-2011] " Laurent Pinchart
2012-08-17 13:23       ` Hans de Goede
2012-08-22 11:09 ` Hans Verkuil

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=502E3D97.3090502@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=workshop-2011@linuxtv.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;
as well as URLs for NNTP newsgroup(s).