From: Rodolfo Giometti <giometti@enneenne.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [RFC] Splash image
Date: Thu, 19 Jul 2007 16:18:29 +0200 [thread overview]
Message-ID: <20070719141829.GA8458@enneenne.com> (raw)
In-Reply-To: <20070719095239.GU25573@enneenne.com>
On Thu, Jul 19, 2007 at 11:52:40AM +0200, Rodolfo Giometti wrote:
> On Thu, Jul 19, 2007 at 11:47:59AM +0200, Wolfgang Grandegger wrote:
> > Rodolfo Giometti wrote:
> >> On Wed, Jul 18, 2007 at 06:17:12PM +0200, Wolfgang Grandegger wrote:
> >>> Rodolfo Giometti wrote:
> >>>> On Wed, Jul 18, 2007 at 06:03:54PM +0200, Wolfgang Grandegger wrote:
> >>>>> What color format do you want to support?
> >>>> 16 bpp
> >>> Then use "drivers/cfb_console.c" as it already supports that format.
> >>> Adapting the interface to pxafb should not be a big deal.
> >> In order to adapt pxafb support to "drivers/cfb_console.c" I think I
> >> should move cpu/pxa/pxafb.c to drivers/pxafb.c adapting the internal
> >> functions to use video_hw_init() and video_set_lut(). Is that right?
> >
> > I think so and drivers is also the correct place for pxafb.c.
>
> Ok, I'll propose a patch ASAP. However, simply moving the file from
> cpu/pxa/ to drivers/ shouldn't break any code but modifying it in
> order to support cfb_console.c will do.
>
> What do you suggest in order to do the right steps? Maybe should I
> remove lcd.c support before doing my modifications?
Just to gain some time and doing some tests I did the modifications in
order to support splash screen into cfb_console for PXAFB.
I noticed that I have to disable some code regarding LCD otherwise
there are doubled code execution and several incongruences, see here:
static int bmp_display(ulong addr, int x, int y)
{
#if defined(CONFIG_LCD)
extern int lcd_display_bitmap (ulong, int, int);
return (lcd_display_bitmap (addr, x, y));
#elif defined(CONFIG_VIDEO)
extern int video_display_bitmap (ulong, int, int);
return (video_display_bitmap (addr, x, y));
#else
# error bmp_display() requires CONFIG_LCD or CONFIG_VIDEO
#endif
}
This code seems OK but if you doesn't define CONFIG_LCD you cannot get
framebuffer memory here (lib_arm/board.c):
#ifdef CONFIG_LCD
# ifndef PAGE_SIZE
# define PAGE_SIZE 4096
# endif
/*
* reserve memory for LCD display (always full pages)
*/
/* bss_end is defined in the board-specific linker script */
addr = (_bss_end + (PAGE_SIZE - 1)) & ~(PAGE_SIZE - 1);
size = lcd_setmem (addr);
gd->fb_base = addr;
#endif /* CONFIG_LCD */
Ok, I can add a defined() but this is not the right solution IMHO.
I wish to remove LCD support at all... are you agree? Any suggestions
in order to which steps I should do for better result?
Thanks in advance,
Rodolfo
--
GNU/Linux Solutions e-mail: giometti at enneenne.com
Linux Device Driver giometti at gnudd.com
Embedded Systems giometti at linux.it
UNIX programming phone: +39 349 2432127
next prev parent reply other threads:[~2007-07-19 14:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-18 8:30 [U-Boot-Users] [RFC] Splash image Rodolfo Giometti
2007-07-18 13:40 ` Joey Oravec
2007-07-18 13:58 ` Rodolfo Giometti
2007-07-18 14:31 ` Jerry Van Baren
2007-07-18 15:32 ` Rodolfo Giometti
2007-07-18 14:47 ` Wolfgang Grandegger
2007-07-18 15:37 ` Rodolfo Giometti
2007-07-18 16:03 ` Wolfgang Grandegger
2007-07-18 16:01 ` Rodolfo Giometti
2007-07-18 16:17 ` Wolfgang Grandegger
2007-07-19 8:36 ` Rodolfo Giometti
2007-07-19 9:47 ` Wolfgang Grandegger
2007-07-19 9:52 ` Rodolfo Giometti
2007-07-19 14:18 ` Rodolfo Giometti [this message]
2007-07-19 14:41 ` Wolfgang Grandegger
2007-07-19 14:40 ` Rodolfo Giometti
2007-07-19 7:09 ` Matthias Fuchs
2007-07-19 8:19 ` Wolfgang Grandegger
2007-07-19 8:33 ` Rodolfo Giometti
[not found] <008901c7ca10$f1921a40$d4b64ec0$@com>
2007-07-19 20:30 ` 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=20070719141829.GA8458@enneenne.com \
--to=giometti@enneenne.com \
--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