From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Uboot bitmap utility
Date: Tue, 28 Apr 2009 10:50:41 +0200 [thread overview]
Message-ID: <m2eivdp3fi.fsf@ohwell.denx.de> (raw)
In-Reply-To: <23265072.post@talk.nabble.com> (Steven Zedeck's message of "Mon, 27 Apr 2009 14:05:22 -0700 (PDT)")
Hi Steven,
> Yes, I do see what U-boot is doing. I looked at bmp_logo.c and its output.
> It seems that the color palette entries are all 16 bits (unsigned short).
To synch up - you are trying to use the 'logo_plot' code from
drivers/video/cfb_console.c, right?
> For my application, I have 24 bit color, which expects each pixel to be 32
> bits, of which only 24 bits are used. So the palette, I assume, should be
> unsigned longs for each color entry. Correct or am I missing something?
Rather than changing this code, why don't you switch to the bmp routines
(common/cmd_bmp.c + (one option) common/lcd.c) which recently got
support for 16bpp displays? It may be easier to add 32-bit support
here...
> Did I interpret the code correctly? Does it expect 16 bits per color?
It seems so..
Cheers
Detlev
--
... does Linux have a better [security] track record than MS? Damn right it
does. We've had fewer problems, and I think there are more people out there
standing up for what's right anyway. Less PR people deathly afraid of rocking
the boat. Better technology, and fewer horrid design mistakes. [Linus Torvalds]
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de
next prev parent reply other threads:[~2009-04-28 8:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 14:30 [U-Boot] Uboot bitmap utility Steven Zedeck
2009-04-24 14:34 ` Steven Zedeck
2009-04-24 18:03 ` Wolfgang Denk
2009-04-27 21:05 ` Steven Zedeck
2009-04-28 8:50 ` Detlev Zundel [this message]
2009-05-21 12:27 ` Steven Zedeck
2009-04-24 17:59 ` Wolfgang Denk
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=m2eivdp3fi.fsf@ohwell.denx.de \
--to=dzu@denx.de \
--cc=u-boot@lists.denx.de \
/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