From: Sergei Shtylylov <sshtylyov@ru.mvista.com>
To: Linux MIPS <linux-mips@linux-mips.org>
Cc: Manish Lachwani <mlachwani@mvista.com>,
Konstantin Baidarov <kbaidarov@ru.mvista.com>
Subject: Re: [PATCH] SiMotion VoyagerGX framebuffer: blue stripped background
Date: Fri, 09 Dec 2005 23:29:32 +0300 [thread overview]
Message-ID: <4399E92C.6010408@ru.mvista.com> (raw)
In-Reply-To: <4399C8AB.4080403@ru.mvista.com>
[-- Attachment #1: Type: text/plain, Size: 594 bytes --]
Hello.
Sergei Shtylylov wrote:
> This driver was using an incorrect typecast when setting pseudopalette,
> hence were the blue strips on the black char background. As this driver
> happens to be maintaned by Linux/MIPS, here's the patch (I've also
> noticed a
> typo in the head comment, hence comes another hunk)...
Have noticed that regno check in smi_setcolreg() is too relaxed as
pseudo-palette has only 16 entries. So, had to update the patch.
WBR, Sergei
Signed-off-by: Konstantin Baydarov <kbaidarov@ru.mvista.com>
Signed-off-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>
[-- Attachment #2: VoyagerGX-blue-strips.patch --]
[-- Type: text/plain, Size: 1131 bytes --]
diff --git a/drivers/video/smivgxfb.c b/drivers/video/smivgxfb.c
index d5755c5..944ff4a 100644
--- a/drivers/video/smivgxfb.c
+++ b/drivers/video/smivgxfb.c
@@ -1,5 +1,5 @@
/***************************************************************************
- * Silicon Motion VoyaagerGX framebuffer driver
+ * Silicon Motion VoyagerGX framebuffer driver
*
* ported to 2.6 by Embedded Alley Solutions, Inc
* Copyright (C) 2005 Embedded Alley Solutions, Inc
@@ -159,10 +159,10 @@ smi_setcolreg(unsigned regno, unsigned r
unsigned blue, unsigned transp,
struct fb_info *info)
{
- if (regno > 255)
+ if (regno > 15)
return 1;
- ((u16 *)(info->pseudo_palette))[regno] =
+ ((u32 *)(info->pseudo_palette))[regno] =
((red & 0xf800) >> 0) |
((green & 0xfc00) >> 5) |
((blue & 0xf800) >> 11);
@@ -318,9 +318,9 @@ static int __devinit vgx_pci_probe(struc
if (!info.pseudo_palette) {
return -ENOMEM;
}
- memset(info.pseudo_palette, 0, sizeof(u32) *16);
+ memset(info.pseudo_palette, 0, sizeof(u32) * 16);
- fb_alloc_cmap(&info.cmap,256,0);
+ fb_alloc_cmap(&info.cmap, 256, 0);
smi_setmode();
next prev parent reply other threads:[~2005-12-09 20:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-09 18:10 [PATCH] SiMotion VoyagerGX framebuffer: blue stripped background Sergei Shtylylov
2005-12-09 20:29 ` Sergei Shtylylov [this message]
2005-12-11 16:53 ` Ralf Baechle
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=4399E92C.6010408@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=kbaidarov@ru.mvista.com \
--cc=linux-mips@linux-mips.org \
--cc=mlachwani@mvista.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