From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] M28: Cleanup memsize.o OOT build
Date: Fri, 09 Dec 2011 10:14:21 +0100 [thread overview]
Message-ID: <4EE1D16D.6050003@denx.de> (raw)
In-Reply-To: <1323347237-6021-1-git-send-email-marek.vasut@gmail.com>
On 08/12/2011 13:27, Marek Vasut wrote:
> Signed-off-by: Marek Vasut <marek.vasut@gmail.com>
> Cc: Wolfgang Denk <wd@denx.de>
> Cc: Detlev Zundel <dzu@denx.de>
> Cc: Stefano Babic <sbabic@denx.de>
> ---
Hi Marek,
> arch/arm/cpu/arm926ejs/mx28/Makefile | 7 +------
> arch/arm/cpu/arm926ejs/mx28/spl_boot.c | 13 ++-----------
> arch/arm/cpu/arm926ejs/mx28/u-boot-spl.lds | 12 ++++++------
> include/configs/m28evk.h | 2 ++
> 4 files changed, 11 insertions(+), 23 deletions(-)
>
It seems to me that your patch does much more as what you describe in
the commit message.
> diff --git a/arch/arm/cpu/arm926ejs/mx28/spl_boot.c b/arch/arm/cpu/arm926ejs/mx28/spl_boot.c
> index 3cd4c24..dfb8309 100644
> --- a/arch/arm/cpu/arm926ejs/mx28/spl_boot.c
> +++ b/arch/arm/cpu/arm926ejs/mx28/spl_boot.c
> @@ -68,17 +68,8 @@ inline void board_init_r(gd_t *id, ulong dest_addr)
> ;
> }
>
> -inline int printf(const char *fmt, ...)
> -{
> - return 0;
> -}
> -
> -inline void __coloured_LED_init(void) {}
> -inline void __red_LED_on(void) {}
> -void coloured_LED_init(void)
> - __attribute__((weak, alias("__coloured_LED_init")));
> -void red_LED_on(void)
> - __attribute__((weak, alias("__red_LED_on")));
> +void serial_putc(const char c) {}
> +void serial_puts(const char *s) {}
Make a note in the commit message about these changes (not related to
the subject)
> void hang(void) __attribute__ ((noreturn));
> void hang(void)
> {
> diff --git a/arch/arm/cpu/arm926ejs/mx28/u-boot-spl.lds b/arch/arm/cpu/arm926ejs/mx28/u-boot-spl.lds
> index 893320f..0fccd52 100644
> --- a/arch/arm/cpu/arm926ejs/mx28/u-boot-spl.lds
> +++ b/arch/arm/cpu/arm926ejs/mx28/u-boot-spl.lds
> @@ -67,16 +67,16 @@ SECTIONS
> *(.dynsym)
> }
>
> - _end = .;
> -
> - .bss __rel_dyn_start (OVERLAY) : {
> + .bss : {
> + . = ALIGN(4);
> __bss_start = .;
> - *(.bss)
> - . = ALIGN(4);
> + *(.bss*)
> + . = ALIGN(4);
> __bss_end__ = .;
> }
>
> - /DISCARD/ : { *(.bss*) }
> + _end = .;
> +
> /DISCARD/ : { *(.dynstr*) }
> /DISCARD/ : { *(.dynsym*) }
> /DISCARD/ : { *(.dynamic*) }
However, these change fix another issue. You want to cleanup
u-boot-spl.lds, but then there are some other parts I cannot understand.
For example, why is __u_boot_cmd_start = needed ?
If your goal is to cleanup the linker file, please submit a separate
patch removing also the unused sections in SPL.
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
next prev parent reply other threads:[~2011-12-09 9:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-08 12:27 [U-Boot] [PATCH] M28: Cleanup memsize.o OOT build Marek Vasut
2011-12-08 19:46 ` [U-Boot] [PATCH V2] " Marek Vasut
2011-12-09 9:14 ` Stefano Babic [this message]
2011-12-09 9:48 ` [U-Boot] [PATCH] " Marek Vasut
2011-12-09 10:37 ` Stefano Babic
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=4EE1D16D.6050003@denx.de \
--to=sbabic@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