From: Richard Retanubun <RichardRetanubun@RuggedCom.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Coldfire: Compiler warnings when building M5271EVB
Date: Fri, 23 Jan 2009 17:27:38 -0500 [thread overview]
Message-ID: <497A445A.1050807@RuggedCom.com> (raw)
Tsi-Chung:
Sorry for the delay. I've posted the M5271 patches to the mailing list just now.
Also, I have a question about the compiler warning I see when building the M5271EVB:
cpu_init.c:57:2: warning: #warning "Chip Select 0 are not initialized/used"
cpu_init.c: In function 'init_fbcs':
cpu_init.c:49: warning: unused variable 'fbcs'
The line numbers are AFTER my patches, so they may not match yours precisely.
Is the correct answer to add CONFIG_M5271 to the this #ifndef ?
- #ifndef CONFIG_M5272
+ #if !(defined CONFIG_M5272) && !(defined CONFIG_M5271)
/* Only 5272 Flexbus chipselect is different from the rest */
void init_fbcs(void)
{
I think that will remove the warnings for M5271, but I may be missing the
context here :)
what is the flexBus by the way?
Thanks for the time
- Richard Retanubun
next reply other threads:[~2009-01-23 22:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 22:27 Richard Retanubun [this message]
2009-01-28 21:46 ` [U-Boot] Coldfire: Compiler warnings when building M5271EVB Liew Tsi Chung-R5AAHP
2009-01-28 23:21 ` Richard Retanubun
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=497A445A.1050807@RuggedCom.com \
--to=richardretanubun@ruggedcom.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.