| To: | Gerald Champagne <gerald.champagne@esstech.com> |
|---|---|
| Subject: | Re: Remove ifdefs from setup_arch() |
| From: | Ralf Baechle <ralf@oss.sgi.com> |
| Date: | Fri, 12 Oct 2001 23:35:59 +0200 |
| Cc: | Jun Sun <jsun@mvista.com>, Geert Uytterhoeven <geert@linux-m68k.org>, "linux-mips@oss.sgi.com" <linux-mips@oss.sgi.com> |
| In-reply-to: | <3BC732C9.9080508@esstech.com>; from gerald.champagne@esstech.com on Fri, Oct 12, 2001 at 01:13:29PM -0500 |
| References: | <Pine.GSO.4.21.0110121350300.20566-100000@mullein.sonytel.be> <3BC72BE8.F50C2001@mvista.com> <3BC732C9.9080508@esstech.com> |
| Sender: | owner-linux-mips@oss.sgi.com |
| User-agent: | Mutt/1.2.5i |
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 in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Big endian problem, Dan Aizenstros |
|---|---|
| Next by Date: | Re: Big endian problem, Jun Sun |
| Previous by Thread: | Re: Remove ifdefs from setup_arch(), Gerald Champagne |
| Next by Thread: | mipsel-linux cross compiler issue while installing, balaji . ramalingam |
| Indexes: | [Date] [Thread] [Top] [All Lists] |