[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0611201636500.17639@pentafluge.infradead.org>
Date: Mon, 20 Nov 2006 16:42:58 +0000 (GMT)
From: James Simmons <jsimmons@...radead.org>
To: Franck Bui-Huu <vagabon.xyz@...il.com>
cc: Linux Fbdev development list
<linux-fbdev-devel@...ts.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...l.org>
Subject: Re: [Linux-fbdev-devel] fbmem: is bootup logo broken for monochrome
LCD ?
> On 11/17/06, James Simmons <jsimmons@...radead.org> wrote:
> >
> > Are those actually numbers? If they are the problem isn't byte reversal
> > but bit shifting.
> >
> > 1010100 = 54
> > 0101010 = 2A
>
> It's not byte reversal, but _bits_ of each bytes have been inversed
> (bit7->bit0, bit6->bit1, bit5->bit2, bit4->bit3, bit3->bit4, ...)
> after calling slow_imageblit(). Is it something expected ?
Yipes!! Bit reversal. I have never seen that before. Is only the logo
messed up? Slow_imageblit can be called if there is no dword alignment
for the font bitmaps. So the question is do most if not all our fonts
look okay?
> > I really don't understand why fbmem.c has its own routines to handle the
> > logo for the color > map. I can set creating a fbcmap and calling
> > fb_set_cmap instead.
>
> Unfortunately I cannot help you on this point...
>
> > That will be a separte patch.
> >
>
> Thanks
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists