From: Andrew Morton <akpm@linux-foundation.org>
To: linux-fbdev-devel@lists.sourceforge.net, dri-devel@lists.sourceforge.net
Cc: samanddeanus@yahoo.com, bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 13285] New: INTELFB: Colors display incorrectly
Date: Tue, 12 May 2009 15:19:34 -0700 [thread overview]
Message-ID: <20090512151934.d7e6c54e.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-13285-10286@http.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Tue, 12 May 2009 01:40:48 GMT
bugzilla-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=13285
>
> Summary: INTELFB: Colors display incorrectly
> Product: Drivers
> Version: 2.5
> Kernel Version: 2.6.30-rc5
This is a post-2.6.29 regression.
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: Console/Framebuffers
> AssignedTo: jsimmons@infradead.org
> ReportedBy: samanddeanus@yahoo.com
> Regression: Yes
>
>
> On my system, the colors are displaying incorrectly when using the Intel
> framebuffer. For example the Tux penguin logo has a blue background, and when
> I start X11 with the fbdev drivers, the xterm also has a blue background, when
> it is set up to have a white background.
>
> 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.
>
The only change to drivers/video/intelfb/ since 2.6.29 was
347486bb108fa6e0fd2753c1be3519d6be2516ed ("intelfb: support i854")
which added a device ID.
Do we think that this regression is due to fbdev changes, or to DRI
changes?
Thanks.
------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
--
next parent reply other threads:[~2009-05-12 22: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 ` Andrew Morton [this message]
2009-05-16 18:42 ` [Bugme-new] [Bug 13285] New: INTELFB: Colors display incorrectly 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
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=20090512151934.d7e6c54e.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.sourceforge.net \
--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).