From: Andrew Morton <akpm@osdl.org>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Fw: [Bugme-new] [Bug 3849] New: tridentfb console at 16 bpp appears in funny colours
Date: Thu, 2 Dec 2004 07:53:47 -0800 [thread overview]
Message-ID: <20041202075347.455bbbb2.akpm@osdl.org> (raw)
Begin forwarded message:
Date: Thu, 2 Dec 2004 02:00:38 -0800
From: bugme-daemon@osdl.org
To: bugme-new@lists.osdl.org
Subject: [Bugme-new] [Bug 3849] New: tridentfb console at 16 bpp appears in funny colours
http://bugme.osdl.org/show_bug.cgi?id=3849
Summary: tridentfb console at 16 bpp appears in funny colours
Kernel Version: 2.6.9
Status: NEW
Severity: normal
Owner: jsimmons@infradead.org
Submitter: timothy.lee@siriushk.com
Hardware: CyberBlade/i1 on VIA Epia-800
Problem Description: When the framebuffer is set to 16 bpp, console's text
colours are incorrect. For example, white becomes yellow, black becomes blue, etc.
Steps to reproduce:
1. Load tridentfb
2. Use "setterm -n -depth 16" to request 16 bpp framebuffer
The problem arose from the fact that each psuedo palette entry should be 32-bit
in size, even under 16-bit display mode.
I will attach a patch.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
reply other threads:[~2004-12-02 15:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20041202075347.455bbbb2.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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.