From: Arnd Bergmann <arnd@arndb.de>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Jason Wessel <jason.wessel@windriver.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [BISECTED, -next] drm/i915: blurred HDMI output
Date: Mon, 18 Oct 2010 21:57:05 +0200 [thread overview]
Message-ID: <201010182157.05339.arnd@arndb.de> (raw)
In-Reply-To: <20101018122801.6a09dd25@jbarnes-desktop>
On Monday 18 October 2010 21:28:01 Jesse Barnes wrote:
>
> On Mon, 18 Oct 2010 21:13:59 +0200
> Arnd Bergmann <arnd@arndb.de> wrote:
>
> > On Monday 18 October 2010 20:56:48 Jesse Barnes wrote:
> > > Hm, the LVDS code should take care of panel fitting in
> > > the !HAS_PCH_SPLIT case. Does this patch achieve the same thing as
> > > yours? Maybe we were leaving a stale PFIT value in place...
> >
> > No, your patch doesn't have any effect for me.
>
> Oh right, you were complaining about HMDI. :)
>
> Yes we still need to shut off panel fitting elsewhere. Do you see the
> blurriness at boot or just after turning on HDMI while leaving the
> laptop panel enabled?
It's a G45 desktop machine, not a laptop.
i915 is a module with kms enabled, the blur seems to show up on the
text console the moment that the module gets loaded during boot.
Before that, the console is in VGA text mode, which is always
slightly blurred because the screen has a different native resolution.
Arnd
next prev parent reply other threads:[~2010-10-18 19:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-17 17:37 [BISECTED, -next] drm/i915: blurred HDMI output Arnd Bergmann
2010-10-18 18:56 ` Jesse Barnes
2010-10-18 19:13 ` Arnd Bergmann
2010-10-18 19:28 ` Jesse Barnes
2010-10-18 19:57 ` Arnd Bergmann [this message]
2010-10-18 20:15 ` Jesse Barnes
2010-10-18 20:30 ` Arnd Bergmann
2010-10-18 20:37 ` Arnd Bergmann
2010-10-18 21:05 ` Jesse Barnes
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=201010182157.05339.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=jason.wessel@windriver.com \
--cc=jbarnes@virtuousgeek.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.