From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Check for a change in fb size, and reconfigure the pipe
Date: Tue, 13 Nov 2012 15:15:55 +0200 [thread overview]
Message-ID: <20121113131555.GI3791@intel.com> (raw)
In-Reply-To: <b94cdc$7ascgg@fmsmga001.fm.intel.com>
On Tue, Nov 13, 2012 at 12:48:11PM +0000, Chris Wilson wrote:
> On Tue, 13 Nov 2012 14:42:36 +0200, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> > On Tue, Nov 13, 2012 at 12:15:10PM +0000, Chris Wilson wrote:
> > > In the slightly unusual case where the pipe is programmed to the same
> > > modeline, but the framebuffer is a new size, we need to resetup the
> > > panel fitter as appropriate and this requires a full modeset. This can
> > > only occur currently as part of the BIOS takeover where there are
> > > slightly different semantics governing how the panel fitter and
> > > framebuffer is programmed relative to the modeline.
> >
> > Hmm. I don't get it. Why would the framebuffer size affect the panel
> > fitter configuration?
>
> The BIOS uses fb->(width,height) to program PIPESRC, we use
> mode->[hv]display. The BIOS's semantics makes more sense
I don't think so. That would make panning impossible.
> and is
> ultimately more flexible - especially if we do end up exposing more
> information to userspace to solve the under/overscan issue using the
> panel fitter.
I've been known to bitch about this issue also. I'd like to have
the mode be strictly the display mode. Then we'd need another way to
configure PIPESRC (some kind of CRTC dimensions properties would do
it). And then we also need to expose the primary plane as a drm_plane.
Those measures would allow full control over the pipe, rather than
relying on some magic connector properties that may or may not do
what you want.
Doing all that seems straightforward enough, but I suspect trying to
maintain some kind of compatibility with the current mess is going
to be the hard part.
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2012-11-13 13:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-13 12:15 [PATCH] drm/i915: Check for a change in fb size, and reconfigure the pipe Chris Wilson
2012-11-13 12:42 ` Ville Syrjälä
2012-11-13 12:48 ` Chris Wilson
2012-11-13 13:15 ` Ville Syrjälä [this message]
2012-11-13 13:33 ` Chris Wilson
2012-11-13 13:59 ` Ville Syrjälä
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=20121113131555.GI3791@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.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