From: Andrew Morton <akpm@linux-foundation.org>
To: Krzysztof Helt <krzysztof.h1@poczta.fm>
Cc: samanddeanus@yahoo.com, linux-fbdev-devel@lists.sourceforge.net,
dri-devel@lists.sourceforge.net,
bugzilla-daemon@bugzilla.kernel.org
Subject: Re: [Linux-fbdev-devel] [Bugme-new] [Bug 13285] New: INTELFB: Colors display incorrectly
Date: Sat, 16 May 2009 23:19:32 -0700 [thread overview]
Message-ID: <20090516231932.2e02647b.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090517081743.92002707.krzysztof.h1@poczta.fm>
On Sun, 17 May 2009 08:17:43 +0200 Krzysztof Helt <krzysztof.h1@poczta.fm> wrote:
> From: Krzysztof Helt <krzysztof.h1@wp.pl>
>
> 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.
>
> I also found by experiment that if both pipes were enabled, the PIPE_B is used (active).
>
> The problem is visible in the 8 bpp mode if colors above 15 are used. The first 16 color
> entries are displayed correctly.
>
> Signed-off-by: Krzysztof Helt <krzysztof.h1@wp.pl>
>
> ---
> This is not a regression. I have reproduced it in the 2.6.28 easily.
hm, Dean's original report had
This does not occur in kernel 2.6.29 -- I can see the Tasmanian
devil in a penguin mask (Tuz) just fine and can view images, etc on
the framebuffer.
> Dean, please test the patch.
Yes please.
> diff --git a/drivers/video/intelfb/intelfbdrv.c b/drivers/video/intelfb/intelfbdrv.c
> index ace14fe..b47f6dd 100644
> --- a/drivers/video/intelfb/intelfbdrv.c
> +++ b/drivers/video/intelfb/intelfbdrv.c
> @@ -871,6 +871,12 @@ static int __devinit intelfb_pci_register(struct pci_dev *pdev,
>
> intelfbhw_print_hw_state(dinfo, &dinfo->save_state);
>
> + /* Check whether pipe A or pipe B is enabled. */
> + if (dinfo->save_state.pipe_a_conf & PIPECONF_ENABLE)
> + dinfo->pipe = PIPE_A;
> + if (dinfo->save_state.pipe_b_conf & PIPECONF_ENABLE)
> + dinfo->pipe = PIPE_B;
> +
> if (bailearly == 18)
> bailout(dinfo);
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables
unlimited royalty-free distribution of the report engine
for externally facing server and web deployment.
http://p.sf.net/sfu/businessobjects
--
next prev parent reply other threads:[~2009-05-17 6:19 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 ` Andrew Morton [this message]
[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
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=20090516231932.2e02647b.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.sourceforge.net \
--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).