From: Robert P. J. Day <rpjday@crashcourse.ca>
To: u-boot@lists.denx.de
Subject: [U-Boot] some dead code and redundant files for nios?
Date: Fri, 1 Feb 2013 18:50:14 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.02.1302011723560.4290@oneiric> (raw)
another observation about header files, this time related to
nios/nios2:
$ grep -r CONFIG_NIOS *
arch/nios2/config.mk:PLATFORM_CPPFLAGS += -DCONFIG_NIOS2 -D__NIOS2__
arch/nios2/cpu/epcs.c:#endif /* CONFIG_NIOS_EPCS */
board/psyent/common/AMDLV065D.c:#if defined(CONFIG_NIOS) <-- ???
board/altera/common/AMDLV065D.c:#if defined(CONFIG_NIOS) <-- ???
common/cmd_bdinfo.c:#elif defined(CONFIG_NIOS2)
examples/standalone/stubs.c:#elif defined(CONFIG_NIOS2)
$
first, given that there is no "nios" architecture anymore, isn't
that preprocessor test of:
#if defined(CONFIG_NIOS)
in those two files always going to be false? the usage is:
#if defined(CONFIG_NIOS)
#include <nios.h>
#else
#include <asm/io.h>
#endif
and there *is* no nios.h file, anyway, so that pretty clearly looks
like a removable test. more to the point, the same source file --
AMDLV065D.c -- is in two different directories, and they differ
slightly:
$ diff board/{altera,psyent}/common/AMDLV065D.c
175c175
< writeb (b, dst);
---
> writeb (dst, b);
$
that looks kind of weird, doesn't it? i haven't looked any more
closely but for two source files with the same name to have that
single, subtle difference just looks strange.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next reply other threads:[~2013-02-01 23:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-01 23:50 Robert P. J. Day [this message]
2013-02-02 10:06 ` [U-Boot] some dead code and redundant files for nios? Robert P. J. Day
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=alpine.DEB.2.02.1302011723560.4290@oneiric \
--to=rpjday@crashcourse.ca \
--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