From: Wolfgang Grandegger <wg@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] LOGO: Adds LCD color map 565 support.
Date: Wed, 30 May 2007 09:50:55 +0200 [thread overview]
Message-ID: <465D2CDF.4010906@denx.de> (raw)
In-Reply-To: <20070526131851.GO21180@enneenne.com>
Hi Rodolfo,
sorry for the late answer.
Rodolfo Giometti wrote:
> On Fri, May 25, 2007 at 06:53:52PM +0200, Wolfgang Denk wrote:
>> What about lcd_display_bitmap() and the color map it uses?
>
> This is used for the splash screen... to be honest I don't know which
> is the difference against the logo but so it is...
>
>> Why do we have two functions lcd_display_bitmap() and bitmap_plot(*)
>> in the first place? I feel both do very similar things? Maybe only
>> one function is needed?
>
> I think so...
Yes, it should be possible handle both with one drawing function.
>> [Please negotiate this also with Wolfgang Grandegger!]
>
> Ok. Currently I only used bitmap_plot() since, in my opinion, is more
> easy to manage...
One limitation of bitmap_plot, and also display_bitmap is, that it does
not work for back&white displays, even if the latter function is used
somehow for black&white display, e.g. with ugly hacks for MCC200. I
would like to have generic drawing functions for 1, 8 and 16 bpp.
Wolfgang.
next prev parent reply other threads:[~2007-05-30 7:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-25 15:36 [U-Boot-Users] [PATCH] LOGO: Adds LCD color map 565 support Rodolfo Giometti
2007-05-25 15:47 ` Wolfgang Denk
2007-05-25 16:21 ` Rodolfo Giometti
2007-05-25 16:53 ` Wolfgang Denk
2007-05-26 13:18 ` Rodolfo Giometti
2007-05-30 7:50 ` Wolfgang Grandegger [this message]
2007-05-30 8:00 ` Rodolfo Giometti
2007-05-30 12:28 ` Wolfgang Grandegger
2007-05-30 13:33 ` Rodolfo Giometti
2007-05-30 14:35 ` Wolfgang Grandegger
2007-05-30 14:39 ` Rodolfo Giometti
2007-05-30 19:19 ` Wolfgang Grandegger
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=465D2CDF.4010906@denx.de \
--to=wg@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