From: Ralf Baechle <ralf@oss.sgi.com>
To: Gerald Champagne <gerald.champagne@esstech.com>
Cc: Jun Sun <jsun@mvista.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
"linux-mips@oss.sgi.com" <linux-mips@oss.sgi.com>
Subject: Re: Remove ifdefs from setup_arch()
Date: Fri, 12 Oct 2001 23:35:59 +0200 [thread overview]
Message-ID: <20011012233559.A1799@dea.linux-mips.net> (raw)
In-Reply-To: <3BC732C9.9080508@esstech.com>; from gerald.champagne@esstech.com on Fri, Oct 12, 2001 at 01:13:29PM -0500
On Fri, Oct 12, 2001 at 01:13:29PM -0500, Gerald Champagne wrote:
> Can you wrap this code into small functions like machine_detect() and
> board_setup() and put it all in one place? That way those of us who
> just want a simple system supporting only one board can just replace
> those two functions with defines that alias the proper machine_detect
> and board_setup fuctions. Then all of the special elf sections and
> function pointers go away.
>
> If it's all in one place like this, then maybe it could be configured
> in the config.in file. I can ifdef it out for boards like mine or other
> boards that can't possibly support more than one system in a given binary
> image. config.in could ifdef it in for configurations that could possibly
> support more than one configuration in a given binary image.
That would all be initcode / initdata so effective bloat zero.
Ralf
prev parent reply other threads:[~2001-10-12 21:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-03 19:11 Remove ifdefs from setup_arch() Gerald Champagne
2001-10-03 19:29 ` Ralf Baechle
2001-10-03 21:11 ` Jun Sun
2001-10-12 11:52 ` Geert Uytterhoeven
2001-10-12 17:44 ` Jun Sun
2001-10-12 18:13 ` Gerald Champagne
2001-10-12 21:35 ` Ralf Baechle [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=20011012233559.A1799@dea.linux-mips.net \
--to=ralf@oss.sgi.com \
--cc=geert@linux-m68k.org \
--cc=gerald.champagne@esstech.com \
--cc=jsun@mvista.com \
--cc=linux-mips@oss.sgi.com \
/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.