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: Fri, 17 Nov 2006 21:42:50 +0100 [thread overview]
Message-ID: <cda58cb80611171242sb40a53bvd02145364551b5a2@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0611171825520.32200@pentafluge.infradead.org>
On 11/17/06, James Simmons <jsimmons@infradead.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 ?
> 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
--
Franck
next prev parent reply other threads:[~2006-11-17 20:42 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
2006-11-17 18:40 ` James Simmons
2006-11-17 20:42 ` Franck Bui-Huu [this message]
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=cda58cb80611171242sb40a53bvd02145364551b5a2@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®