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 22:30:17 +0200 [thread overview]
Message-ID: <201010182230.17669.arnd@arndb.de> (raw)
In-Reply-To: <20101018131523.19f71ca3@jbarnes-desktop>
On Monday 18 October 2010 22:15:23 Jesse Barnes wrote:
> On Mon, 18 Oct 2010 21:57:05 +0200 Arnd Bergmann <arnd@arndb.de> wrote:
> > 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.
>
> Arg why would the BIOS set the panel fitting bit at all in this
> config? Any attached outputs (VGA, HDMI) will have their own scalers...
I didn't think the BIOS was setting it. Text mode appears to be blurred
differently, but that's hard to tell...
> Obviously we need to clear it somewhere, but we should be able to avoid
> clearing it on every mode set. We should probably shut down all panel
> related bits in intel_lvds.c if we fail to detect an LVDS output; that
> should save a little power and avoid problems like this.
>
> Maybe the below patch which does that will help?
No luck here either.
I don't think the code path you patch here actually gets used, since
intel_lvds_init gets called by intel_setup_outputs only for mobile devices.
Arnd
next prev parent reply other threads:[~2010-10-18 20:30 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
2010-10-18 20:15 ` Jesse Barnes
2010-10-18 20:30 ` Arnd Bergmann [this message]
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=201010182230.17669.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.