From: joshk@triplehelix.org (Joshua Kwan)
To: adaplas@pol.net
Cc: linux-fbdev-devel@lists.sourceforge.net,
linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [Linux-fbdev-devel] Re: Problem with current fb_get_color_depth function
Date: Thu, 11 Nov 2004 00:27:55 -0800 [thread overview]
Message-ID: <20041111082755.GE2815@triplehelix.org> (raw)
In-Reply-To: <200411030610.12231.adaplas@hotpop.com>
[-- Attachment #1: Type: text/plain, Size: 1033 bytes --]
On Wed, Nov 03, 2004 at 06:10:12AM +0800, Antonino A. Daplas wrote:
> After giving it a lot of thought, perhaps you are not booting at 16 bpp, but
> at 8bpp pseudocolor. However, radeonfb's default var use only a red, green,
> and blue length of 6. Try this patch and let me know if it helps.
The patch rejects against 2.6.10-rc1, but re-adapted, it works. Here is the
updated patch for radeon_monitor.c.
Thanks a lot for your help!
and in case this is final,
Signed-off-by: Joshua Kwan <joshk@triplehelix.org>
--
Joshua Kwan
--- a/drivers/video/aty/radeon_monitor.c 2004-11-10 23:38:18.000000000 -0800
+++ b/drivers/video/aty/radeon_monitor.c 2004-11-10 23:38:21.000000000 -0800
@@ -8,7 +8,7 @@
static struct fb_var_screeninfo radeonfb_default_var = {
640, 480, 640, 480, 0, 0, 8, 0,
- {0, 6, 0}, {0, 6, 0}, {0, 6, 0}, {0, 0, 0},
+ {0, 8, 0}, {0, 8, 0}, {0, 8, 0}, {0, 0, 0},
0, 0, -1, -1, 0, 39721, 40, 24, 32, 11, 96, 2,
0, FB_VMODE_NONINTERLACED
};
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 881 bytes --]
prev parent reply other threads:[~2004-11-11 8:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-10 22:59 Problem with current fb_get_color_depth function Joshua Kwan
2004-10-11 0:33 ` Antonino A. Daplas
2004-11-02 5:55 ` Joshua Kwan
2004-11-02 12:04 ` [Linux-fbdev-devel] " Antonino A. Daplas
2004-11-02 12:19 ` Geert Uytterhoeven
2004-11-02 22:10 ` Antonino A. Daplas
2004-11-11 8:27 ` Joshua Kwan [this message]
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=20041111082755.GE2815@triplehelix.org \
--to=joshk@triplehelix.org \
--cc=adaplas@pol.net \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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 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).