From: Roland Scheidegger <rscheidegger_lists@hispeed.ch>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 3/4] drm: Add drm_format_{horz, vert}_chroma_subsampling() utility functions
Date: Fri, 13 Apr 2012 04:42:04 +0200 [thread overview]
Message-ID: <4F87927C.1090905@hispeed.ch> (raw)
In-Reply-To: <20120412122309.GM4917@intel.com>
Am 12.04.2012 14:23, schrieb Ville Syrjälä:
> On Wed, Apr 11, 2012 at 08:53:08PM +0200, Roland Scheidegger wrote:
>> Am 05.04.2012 20:35, schrieb ville.syrjala@linux.intel.com:
>>> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>>>
>>> These functions return the chroma subsampling factors for the specified
>>> pixel format.
>> Hmm not really related but looking at it this reminds me these formats
>> always look a bit underspecified wrt chroma subsample positions. Are
>> these fixed, undefined, or what (even mpeg1 and mpeg2 differ there, and
>> let's not even talk about the big mess that interlaced mpeg2 is)?
>
> My thinking is that the sample positions can be configured through
> some other means. It doesn't affect the in memory layout at all so
> tying it to the format isn't necessary.
>
> This also depends on the hardware. On some hardware you can configure
> it quite freely, but on some you may be left with just the one option,
> which is often not even documented.
>
> I sent another patch [1] some time ago which provides a helper function
> for drivers dealing with good hardware.
>
> [1] http://lists.freedesktop.org/archives/dri-devel/2011-December/017585.html
>
I guess that makes sense. As long as those "other means" are available.
Not like with xv where I think drivers just default to what is probably
the most likely subsample positions, so assuming mpeg2/4 progressive or
something (which gets mpeg1 slightly wrong), if they even bother to care
about such subtleties :-).
Roland
next prev parent reply other threads:[~2012-04-13 2:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-05 18:35 [PATCH 1/4] drm: Move drm_format_num_planes() to drm_crtc.c ville.syrjala
2012-04-05 18:35 ` [PATCH 2/4] drm: Add drm_format_plane_cpp() utility function ville.syrjala
2012-04-05 18:35 ` [PATCH 3/4] drm: Add drm_format_{horz, vert}_chroma_subsampling() utility functions ville.syrjala
2012-04-11 18:53 ` Roland Scheidegger
2012-04-12 12:23 ` Ville Syrjälä
2012-04-13 2:42 ` Roland Scheidegger [this message]
2012-04-13 12:09 ` Ville Syrjälä
2012-04-05 18:35 ` [PATCH 4/4] drm: Add sanity checks to framebuffer creation ville.syrjala
2012-04-20 11:43 ` [PATCH 1/4] drm: Move drm_format_num_planes() to drm_crtc.c Dave Airlie
2012-04-20 12:23 ` Ville Syrjälä
2012-04-20 12:29 ` Dave Airlie
2012-04-20 12:48 ` Rob Clark
2012-04-20 13:49 ` Ville Syrjälä
2012-04-20 14:22 ` Rob Clark
2012-04-21 4:00 ` InKi Dae
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=4F87927C.1090905@hispeed.ch \
--to=rscheidegger_lists@hispeed.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=ville.syrjala@linux.intel.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