From: Tom <Tom.Rix@windriver.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] vxworks: Make loading vxworks less verbose
Date: Wed, 23 Sep 2009 06:31:46 -0500 [thread overview]
Message-ID: <4ABA0722.8070809@windriver.com> (raw)
In-Reply-To: <1253686951-30678-1-git-send-email-niklaus.giger@netstal.com>
Niklaus Giger wrote:
> Newer vxWorks 6.x images have over 20 different C++ segments.
> This fills up the output with rarely used information.
>
> Signed-off-by: Niklaus Giger <niklaus.giger@netstal.com>
> ---
> common/cmd_elf.c | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/common/cmd_elf.c b/common/cmd_elf.c
> index 63f6fe7..bf7dd63 100644
> --- a/common/cmd_elf.c
> +++ b/common/cmd_elf.c
> @@ -286,6 +286,7 @@ unsigned long load_elf_image (unsigned long addr)
> continue;
> }
>
> +#ifdef DEBUG
> if (strtab) {
> debug("%sing %s @ 0x%08lx (%ld bytes)\n",
> (shdr->sh_type == SHT_NOBITS) ?
> @@ -294,6 +295,7 @@ unsigned long load_elf_image (unsigned long addr)
> (unsigned long) shdr->sh_addr,
> (long) shdr->sh_size);
> }
> +#endif
I am not sure this will do anything.
From the decl of 'debug'
#ifdef DEBUG
#define debug(fmt,args...) printf (fmt ,##args)
#define debugX(level,fmt,args...) if (DEBUG>=level) printf(fmt,##args);
#else
#define debug(fmt,args...)
#define debugX(level,fmt,args...)
#endif /* DEBUG */
debug is already hidden by the DEBUG define.
Maybe a better choice would be to switch to debugX
Tom
>
> if (shdr->sh_type == SHT_NOBITS) {
> memset ((void *)shdr->sh_addr, 0, shdr->sh_size);
prev parent reply other threads:[~2009-09-23 11:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 6:22 [U-Boot] [PATCH] vxworks: Make loading vxworks less verbose Niklaus Giger
2009-09-23 8:31 ` Niklaus Giger
2009-09-23 11:37 ` Tom
2009-09-23 11:31 ` Tom [this message]
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=4ABA0722.8070809@windriver.com \
--to=tom.rix@windriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.