Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Gerald Champagne <gerald.champagne@esstech.com>
Cc: "linux-mips@oss.sgi.com" <linux-mips@oss.sgi.com>
Subject: Re: Remove ifdefs from setup_arch()
Date: Wed, 3 Oct 2001 21:29:24 +0200	[thread overview]
Message-ID: <20011003212924.A28810@dea.linux-mips.net> (raw)
In-Reply-To: <3BBB62DE.3040003@esstech.com>; from gerald.champagne@esstech.com on Wed, Oct 03, 2001 at 02:11:26PM -0500

On Wed, Oct 03, 2001 at 02:11:26PM -0500, Gerald Champagne wrote:

> For each configuration, only one case is compiled in.  Wouldn't it
> be simpler to just give the board-specific setup function a common name
> and consider it part of the board-specific api like all the other
> board-specific functions.  Can this be changed to just this:
> 
> -----------------
> void __init setup_arch(char **cmdline_p)
> {
> 	void foo_setup(void);
> 
> 	...
> 
> 	foo_setup();  /* someone pick a name for this */
> 	...
> -----------------
> 
> I'm trying to document an api for supporting an arbitrary board, and little
> things like this make it more difficult to define something along the lines
> of a bsp interface.  Any suggestions?  Any objections?

We used to allow support for multiple boards in one kernel binary though
that usually doesn't work for MIPS due to the large number of very different
systems.  People have asked to resurrect this option, so I'd like to go
for an option that only removes all those awful #ifdefs.  Something based
on ELF sections looks like a way to do this.

  Ralf

  reply	other threads:[~2001-10-03 19:29 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 [this message]
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

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=20011003212924.A28810@dea.linux-mips.net \
    --to=ralf@oss.sgi.com \
    --cc=gerald.champagne@esstech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox