From: Andrew Morton <akpm@linux-foundation.org>
To: Krzysztof Helt <krzysztof.h1@poczta.fm>
Cc: bugzilla-daemon@bugzilla.kernel.org, samanddeanus@yahoo.com,
linux-fbdev-devel@lists.sourceforge.net,
dri-devel@lists.sourceforge.net, hramrach@centrum.cz
Subject: Re: [Bugme-new] [Bug 13285] New: INTELFB: Colors display incorrectly
Date: Tue, 2 Jun 2009 13:18:55 -0700 [thread overview]
Message-ID: <20090602131855.1d69f442.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090530135833.6a2c1bb2.krzysztof.h1@poczta.fm>
On Sat, 30 May 2009 13:58:33 +0200
Krzysztof Helt <krzysztof.h1@poczta.fm> wrote:
> The intelfb driver sets color map depending on currently active pipe. However, if an LVDS
> display is attached (like in laptop) the active pipe variable is never set. The default value is
> PIPE_A and can be wrong.
> Set up the pipe variable during driver initialization after hardware state was read.
>
> Also, the detection of the active display (and hence the pipe) is wrong. The pipes are assigned
> to so called planes. Both pipes are always enabled on my laptop but only one plane is enabled
> (the plane A for the CRT or the plane B for the LVDS). Change active pipe detection code
> to take into account a status of the plane assigned to each pipe.
>
> The problem is visible in the 8 bpp mode if colors above 15 are used. The first 16 color
> entries are displayed correctly.
>
> The graphics chip description is here (G45 vol. 3):
> http://intellinuxgraphics.org/documentation.html
>
> Signed-off-by: Krzysztof Helt <krzysztof.h1@wp.pl>
>
> ---
> The second version of the fix to this problem. Now, it is much more sophisticated
> based on the knowledge gained from documentation available at http://intellinuxgraphics.org/.
>
> It does not change a default behaviour (assumed pipe A) for all cases except the case that only
> the plane assigned to the pipe B is active. It is enough to fix the issue for me.
I queued this.
> Please test it.
But it would great be Dean and/or Michal were to be able to test it, please.
------------------------------------------------------------------------------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises
looking to deploy the next generation of Solaris that includes the latest
innovations from Sun and the OpenSource community. Download a copy and
enjoy capabilities such as Networking, Storage and Virtualization.
Go to: http://p.sf.net/sfu/opensolaris-get
next prev parent reply other threads:[~2009-06-02 20:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-13285-10286@http.bugzilla.kernel.org/>
2009-05-12 22:19 ` [Bugme-new] [Bug 13285] New: INTELFB: Colors display incorrectly Andrew Morton
2009-05-16 18:42 ` Krzysztof Helt
[not found] ` <20090517081743.92002707.krzysztof.h1@poczta.fm>
2009-05-17 6:19 ` [Linux-fbdev-devel] " Andrew Morton
[not found] ` <20090517123032.2b8bad00.krzysztof.h1@poczta.fm>
2009-05-17 15:07 ` Michal Suchanek
2009-05-30 11:58 ` Krzysztof Helt
2009-06-02 20:18 ` Andrew Morton [this message]
2009-06-03 9:27 ` Michal Suchanek
2009-06-04 20:58 ` Krzysztof Helt
2009-06-05 12:14 ` Michal Suchanek
2009-06-30 11:35 ` Michal Suchanek
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=20090602131855.1d69f442.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.sourceforge.net \
--cc=hramrach@centrum.cz \
--cc=krzysztof.h1@poczta.fm \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=samanddeanus@yahoo.com \
/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;
as well as URLs for NNTP newsgroup(s).