From: Stelian Pop <stelian@popies.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] lcd: print custom strings after the logo
Date: Tue, 21 Oct 2008 18:54:31 +0200 [thread overview]
Message-ID: <1224608071.6551.30.camel@galileo> (raw)
In-Reply-To: <48FE06A2.8090507@ronetix.at>
Le mardi 21 octobre 2008 ? 18:43 +0200, Ilko Iliev a ?crit :
> >> +#ifndef CONFIG_LCD_LOGO_TEXT1
> >> +# define CONFIG_LCD_LOGO_TEXT1 "(C) 2008 ATMEL Corp"
> >> +#endif
> >>
> >
> > Wouldn't it be better if we move this text into
> > include/configs/at91xxx.h for all the boards ?
> >
> Yes, it will be better.
> Because I'm a newbie in the U-BOOT development I didn't want to make
> changes in all boards.
> I have also other suggestions: see my email for the lowlevel_init.S
Yes, I saw them. Wolfgang proposed to use a weak function, which is
probably way better
> Do you know why the CPU registers are defined in this way:
> #define AT91_PMC (0xfffffc00 - AT91_BASE_SYS)
This is because the header files ware copied (with some editing) from
Linux, and this is how Linux does define those register offsets.
> This is OK for a C-code, but for an assembler it is a problem because
> the following code gives an "Error: bad immediate value for offset":
> ldr r1, =AT91_BASE_SYS
You shouldn't do this. Look at at91_sys_read()/at91_sys_write()
implementation. So the code should be:
ldr r1, =(AT91_BASE_SYS + AT91_PMC)
which will be optimised by cpp to:
ldr r1, =0xfffffc00
Stelian.
--
Stelian Pop <stelian@popies.net>
next prev parent reply other threads:[~2008-10-21 16:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 13:10 [U-Boot] [PATCH] lcd: print custom strings after the logo Ilko Iliev
2008-10-21 16:23 ` Stelian Pop
2008-10-21 16:43 ` Ilko Iliev
2008-10-21 16:54 ` Stelian Pop [this message]
2008-10-21 19:40 ` Wolfgang Denk
2008-10-21 20:56 ` Jean-Christophe PLAGNIOL-VILLARD
2008-10-22 14:00 ` Anatolij Gustschin
2008-10-23 18:36 ` Haavard Skinnemoen
2008-10-23 18:53 ` Jean-Christophe PLAGNIOL-VILLARD
2008-10-23 19:08 ` Haavard Skinnemoen
2008-10-23 19:19 ` Wolfgang Denk
2008-10-23 20:29 ` Jean-Christophe PLAGNIOL-VILLARD
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=1224608071.6551.30.camel@galileo \
--to=stelian@popies.net \
--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