From: Chris Wilson <chris@chris-wilson.co.uk>
To: Olof Johansson <olof@lixom.net>, Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: intel-gfx@lists.freedesktop.org, Mandeep Baines <msb@chromium.org>
Subject: Re: [PATCH] i915: Initialize panel timing registers if VBIOS did not.
Date: Thu, 14 Oct 2010 09:22:06 +0100 [thread overview]
Message-ID: <89k83a$a0d8uk@azsmga001.ch.intel.com> (raw)
In-Reply-To: <AANLkTi=9yj4P9t_eyTk0-jZrvzkCrFYkuzynPJzMc4V-@mail.gmail.com>
On Wed, 13 Oct 2010 16:00:44 -0500, Olof Johansson <olof@lixom.net> wrote:
> On Fri, Oct 8, 2010 at 4:17 PM, Jesse Barnes <jbarnes@virtuousgeek.org>wrote:
> > I can't vouch for any particular set of values, but Bryan's analysis
> > looks good to me; only a few of the values actually matter, and for
> > those having slightly longer delays should be safe.
> >
>
> Sounds like a soft ack to me. :)
Close enough. I rearranged the code slightly so that the act of fixing up
registers was separated from the code who purpose is simply to parse the
VBIOS and pushed into drm-intel-staging.
If you could check it over for obvious mistakes as it will land in -next
just as soon as I've fixed up a troublesome merge with nouveau.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
prev parent reply other threads:[~2010-10-14 8:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 0:05 [PATCH] i915: Initialize panel timing registers if VBIOS did not Bryan Freed
2010-10-08 9:58 ` Chris Wilson
2010-10-08 18:35 ` Bryan Freed
2010-10-08 20:11 ` Jim Gettys
2010-10-08 20:28 ` Chris Wilson
2010-10-08 21:17 ` Jesse Barnes
2010-10-13 21:00 ` Olof Johansson
2010-10-14 8:22 ` Chris Wilson [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='89k83a$a0d8uk@azsmga001.ch.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.org \
--cc=msb@chromium.org \
--cc=olof@lixom.net \
/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