[Top] [All Lists]

Re: configure spaghetti code

To: Florian Lohoff <>
Subject: Re: configure spaghetti code
From: Ralf Baechle <>
Date: Sun, 2 Apr 2000 05:16:26 +0200
In-reply-to: <>; from on Sat, Apr 01, 2000 at 06:19:31PM +0200
References: <>
On Sat, Apr 01, 2000 at 06:19:31PM +0200, Florian Lohoff wrote:

> Hi,
> i tried to compile my own kernel for the IP22 (mips not mips64) and 
> had no sucess (no output on any console) - I think this is due
> to the a couple of bugs ...
> First of all - The spaghetti code in the contains a lot if nice
> gimmicks like:
> if [ "$CONFIG_DECSTATION" != "y" ]; then
>    source drivers/char/
> else
>    mainmenu_option next_comment
>    comment 'DECstation Character devices'
> [...]
>    if [ "$CONFIG_SGI_IP22" = "y" ]; then
>       bool 'SGI PROM Console Support' CONFIG_SGI_PROM_CONSOLE
>    fi
> [...]
> Due to this the CONFIG_SGI_PROM_CONSOLE is not even selectable if
> i do not enable CONFIG_DECSTATION with CONFIG_SGI_IP22 ...
> As most of the Architectures (IP22, Decstation etc) have VERY special
> hardware and nothing in common with the "default pc architecture"
> wouldnt it be a good way to 
> 1. Have a choice of ONE architecture to select (Most of them can coexist
>    within the same kernel)

Most of them can NOT coexist in one kernel due to address space layout
differences, firmware differences etc. and users can not be expected to
know the details nor is it realistic to make a generic kernel for MIPS.
So as you say there should only one be selectable.

> 2. Depending on the selected Architecture include "config" scripts
>    within their special directory (Probably common CPU Type and networking
>    option, filesystem selection)
> 3. Only show devices which are really available for the architectures
>    (I dont think anyone has succeeded in plugging a 3C509 into a DecStation 
>    5000 or a Telephony card or even IDE)

Patches will be accepted :-)  Actually in the past things were slightly
more as you were suggesting but the code was fairly spagetty-like with the
intension to redo it somewhen.


<Prev in Thread] Current Thread [Next in Thread>