All of lore.kernel.org
 help / color / mirror / Atom feed
From: Damien Lespiau <damien.lespiau@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: "Gohad, Tushar" <tushar.gohad@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>
Subject: Re: AVI infoframes: default aspect ratio/VIC for CEA modes
Date: Thu, 21 Nov 2013 17:28:35 +0000	[thread overview]
Message-ID: <20131121172835.GC26262@strange.amr.corp.intel.com> (raw)
In-Reply-To: <20131121171945.GB10036@intel.com>

On Thu, Nov 21, 2013 at 07:19:45PM +0200, Ville Syrjälä wrote:
> > > It seems natural to extend those flags to describe the picture aspect ratio (that
> > > why dri-devel is in Cc., touching core DRM).
> > 
> > To start with we can use a single bit in drm_display_mode->flags to distinguish 16:9 vs 4:3.
> 
> I must admit I haven't really looked into the matter, but do we actually
> need any mode bits? Would it be enoguh to just have a property that
> allows the user to specify the picture aspect ratio?

Well, that's a good question! the picture aspect ratio is attached to
modes in CEA-861, but it could be a good idea to have an orthogonal
picture a-r property on the crtc.

Not quite sure at this point, needs a bit more understanding of the
problem.

-- 
Damien

      reply	other threads:[~2013-11-21 17:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-20 21:48 AVI infoframes: default aspect ratio/VIC for CEA modes Gohad, Tushar
2013-11-20 22:11 ` Damien Lespiau
2013-11-20 22:20   ` Damien Lespiau
2013-11-20 23:45     ` Gohad, Tushar
2013-11-21  0:37       ` Damien Lespiau
2013-11-21  2:48         ` [Intel-gfx] " Gohad, Tushar
2013-11-21 17:19           ` Ville Syrjälä
2013-11-21 17:28             ` Damien Lespiau [this message]

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=20131121172835.GC26262@strange.amr.corp.intel.com \
    --to=damien.lespiau@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=tushar.gohad@intel.com \
    --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 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.