All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Dave Airlie <airlied@gmail.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [RFC] Three pipe support for IVB
Date: Thu, 6 Oct 2011 08:18:30 -0700	[thread overview]
Message-ID: <20111006081830.44dc520f@jbarnes-desktop> (raw)
In-Reply-To: <CAPM=9twh4cN5ydYOAS3+C9AU1Gmso-byp+tfANnwKoGV+Linsw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1894 bytes --]

On Thu, 6 Oct 2011 07:31:44 +0100
Dave Airlie <airlied@gmail.com> wrote:

> On Wed, Oct 5, 2011 at 9:18 PM, Keith Packard <keithp@keithp.com> wrote:
> > On Wed, 5 Oct 2011 12:56:47 -0700, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> >
> >> Unfortunately, (2) complicates our mode list output.  If you query for
> >> available modes, you'll definitely see some that you can't drive with 3
> >> pipes enabled.  I'm not sure if the best way to handle that...
> >
> > All we can do is say 'no' when someone tries to select that
> > configuration. We've never figured out a better way to list valid
> > settings.
> >
> > The proposed RandR 1.4 protocol has a 'set everything all at once' API
> > which allows you to say 'no' before even starting the mode setting
> > process, which is kinda nice. We just need to make sure sure this can be
> > mirrored through KMS to the hardware.
> 
> Fine for dynamic stuff, how do you pick a correct initial mode?
> 
> You can't say no there, you need to make a decision from the
> information provided.

Yeah that's a good point.  There's something weird going on in general
with X's default config on my system at least.  All 3 heads come up at
1280x1024, but the two identical HDMI heads come up with different
refresh rates for some reason (one uses the preferred mode and the
other tries to get 75Hz).

Of course I'd prefer an extended config as the default, which might
make it easier to choose all the preferred modes, but that doesn't
solve the problem of having say two 1920x1200 monitors attached along
with a 2560x1600, which won't work on IVB...

Should we add a new mode flag to indicate which modes are conditional
on config and which modes can always be supported?  That way X and
other tools could get all the heads lit up by default at least...

-- 
Jesse Barnes, Intel Open Source Technology Center

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2011-10-06 15:18 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-05 17:25 [RFC] Three pipe support for IVB Jesse Barnes
2011-10-05 17:25 ` [PATCH 1/4] drm/i915: PLL macro cleanup and pipe assertion check Jesse Barnes
2011-10-05 17:29   ` Jesse Barnes
2011-10-05 18:07   ` Keith Packard
2011-10-05 18:25     ` Jesse Barnes
2011-10-05 18:43   ` Chris Wilson
2011-10-05 18:48     ` Jesse Barnes
2011-10-05 17:25 ` [PATCH 2/4] drm/i915: support 3 pipes on IVB+ Jesse Barnes
2011-10-05 17:25 ` [PATCH 3/4] drm/i915: split refclk code out of ironlake_crtc_mode_set Jesse Barnes
2011-10-05 18:09   ` Keith Packard
2011-10-05 18:26     ` Jesse Barnes
2011-10-05 19:15       ` Keith Packard
2011-10-05 17:25 ` [PATCH 4/4] drm/i915: more 3 pipe support Jesse Barnes
2011-10-05 19:48   ` Jesse Barnes
2011-10-05 22:07     ` Eugeni Dodonov
2011-10-05 19:56 ` [RFC] Three pipe support for IVB Jesse Barnes
2011-10-05 20:18   ` Keith Packard
2011-10-06  6:31     ` Dave Airlie
2011-10-06 15:18       ` Jesse Barnes [this message]
2011-10-06 15:51         ` Daniel Vetter
2011-10-06 15:29       ` Keith Packard
2011-10-05 22:00   ` Eugeni Dodonov

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=20111006081830.44dc520f@jbarnes-desktop \
    --to=jbarnes@virtuousgeek.org \
    --cc=airlied@gmail.com \
    --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 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.