From: "Franck Bui-Huu" <vagabon.xyz@gmail.com>
To: "James Simmons" <jsimmons@infradead.org>
Cc: "Linux Fbdev development list"
<linux-fbdev-devel@lists.sourceforge.net>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Andrew Morton" <akpm@osdl.org>
Subject: Re: [Linux-fbdev-devel] fbmem: is bootup logo broken for monochrome LCD ?
Date: Tue, 14 Nov 2006 10:44:43 +0100 [thread overview]
Message-ID: <cda58cb80611140144q79718798p40f2762955c1d91@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0611131850410.2366@pentafluge.infradead.org>
On 11/13/06, James Simmons <jsimmons@infradead.org> wrote:
>
> Let me know if it works now.
>
OK I can apply it now.
>
> diff -urN -X linus-2.6/Documentation/dontdiff linus-2.6/drivers/video/cfbimgblt.c fbdev-2.6/drivers/video/cfbimgblt.c
> --- linus-2.6/drivers/video/cfbimgblt.c 2006-11-07 05:38:36.000000000 -0500
> +++ fbdev-2.6/drivers/video/cfbimgblt.c 2006-11-12 10:29:49.000000000 -0500
[snip]
> +static inline void slow_imageblit(const struct fb_image *image,
> + struct fb_info *p, u8 __iomem *dst,
> + u32 start_index, u32 pitch_index)
I still have my problem there: for example if image data are
0, 0, 0x54, 0, ...
then slow_imageblit() will write into the frame buffer, the following bytes:
0, 0, 0x2a, 0, ...
instead of the initial ones:
0, 0, 0x54, 0, ...
Bits of each bytes are reversed. I already tried to explain my
problem, please look at
http://marc.theaimsgroup.com/?l=linux-kernel&m=116315548626875&w=2
>
> diff -urN -X linus-2.6/Documentation/dontdiff linus-2.6/drivers/video/fbmem.c fbdev-2.6/drivers/video/fbmem.c
[snip]
> @@ -480,14 +436,13 @@
> int fb_show_logo(struct fb_info *info, int rotate)
> {
> u32 *palette = NULL, *saved_pseudo_palette = NULL;
> - unsigned char *logo_new = NULL, *logo_rotate = NULL;
> struct fb_image image;
>
> /* Return if the frame buffer is not mapped or suspended */
> if (fb_logo.logo == NULL || info->state != FBINFO_STATE_RUNNING)
> return 0;
>
> - image.depth = 8;
> + image.depth = fb_logo.depth;
> image.data = fb_logo.logo->data;
>
> if (fb_logo.needs_cmapreset)
> @@ -508,17 +463,13 @@
> info->pseudo_palette = palette;
> }
>
> - if (fb_logo.depth <= 4) {
> - logo_new = kmalloc(fb_logo.logo->width * fb_logo.logo->height,
> - GFP_KERNEL);
> - if (logo_new == NULL) {
> - kfree(palette);
> - if (saved_pseudo_palette)
> - info->pseudo_palette = saved_pseudo_palette;
> - return 0;
> + if (fb_logo.depth == 1) {
> + if (info->fix.visual == FB_VISUAL_MONO01) {
> + u32 fg = image.fg_color;
> +
> + image.fg_color = image.bg_color;
> + image.bg_color = fg;
I had to fix this part to make the bootup logo worked. image.fg_color
is not uninitialised at this point. I had to change this part as
follow:
if (fb_logo.depth == 1) {
image.fg_color = (info->fix.visual == FB_VISUAL_MONO01) ? 1: 0;
image.bg_color = !image.fg_color;
}
Otherwise this part of your patch (the one which fix the logo display)
seems ok for my naive look. It would be nice if this part could be
sent in a single patch to Andrew. I already tried to fix it but your
patch looks better.
Thanks
--
Franck
next prev parent reply other threads:[~2006-11-14 9:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-09 16:49 Franck Bui-Huu
2006-11-12 22:04 ` [Linux-fbdev-devel] " James Simmons
2006-11-13 9:53 ` Franck Bui-Huu
2006-11-13 14:17 ` James Simmons
2006-11-13 14:31 ` Franck Bui-Huu
2006-11-13 18:55 ` James Simmons
2006-11-13 18:27 ` Franck Bui-Huu
2006-11-13 18:51 ` James Simmons
2006-11-14 9:44 ` Franck Bui-Huu [this message]
2006-11-17 18:40 ` James Simmons
2006-11-17 20:42 ` Franck Bui-Huu
2006-11-20 16:42 ` James Simmons
2006-11-21 9:45 ` Franck Bui-Huu
2006-11-21 18:02 ` James Simmons
2006-11-22 8:48 ` Franck Bui-Huu
2006-11-22 19:43 ` James Simmons
2006-11-22 21:04 ` James Simmons
2006-11-23 14:53 ` Franck Bui-Huu
2006-11-27 16:01 ` James Simmons
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=cda58cb80611140144q79718798p40f2762955c1d91@mail.gmail.com \
--to=vagabon.xyz@gmail.com \
--cc=akpm@osdl.org \
--cc=jsimmons@infradead.org \
--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
all inboxes | Powered by JetHome®