linux-mips
[Top] [All Lists]

Re: make xmenuconfig is broken

To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Subject: Re: make xmenuconfig is broken
From: Jun Sun <jsun@mvista.com>
Date: Thu, 7 Nov 2002 14:23:04 -0800
Cc: Karsten Merker <karsten@excalibur.cologne.de>, linux-mips@linux-mips.org, jsun@mvista.com
In-reply-to: <Pine.GSO.3.96.1021107201241.5894L-100000@delta.ds2.pg.gda.pl>; from macro@ds2.pg.gda.pl on Thu, Nov 07, 2002 at 08:26:19PM +0100
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <Pine.GSO.3.96.1021030135048.1859E-100000@delta.ds2.pg.gda.pl> <Pine.GSO.3.96.1021107201241.5894L-100000@delta.ds2.pg.gda.pl>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.2.5i
Yes, this patch takes care of DECSTATION part of the xconfig problem. 
Thanks.

Now we still have IP22 config which needs to be fixed.  Any volunteers?

This is the additional hack needed that would make xconfig (serial/serial 
console options) work.

diff -Nru arch/mips/config-shared.in.orig arch/mips/config-shared.in
--- arch/mips/config-shared.in.orig     Thu Nov  7 14:14:09 2002
+++ arch/mips/config-shared.in  Thu Nov  7 14:17:33 2002
@@ -800,9 +800,9 @@
 fi
 endmenu
 
-if [ "$CONFIG_SGI_IP22" = "y" ]; then
-   source drivers/sgi/Config.in
-fi
+#if [ "$CONFIG_SGI_IP22" = "y" ]; then
+#   source drivers/sgi/Config.in
+#fi
 
 source drivers/usb/Config.in
 
Jun

On Thu, Nov 07, 2002 at 08:26:19PM +0100, Maciej W. Rozycki wrote:
> On Wed, 30 Oct 2002, Maciej W. Rozycki wrote:
> 
> > On Tue, 29 Oct 2002, Jun Sun wrote:
> > 
> > > My limited xconfig knowledge seems to tell me that moving to the generic
> > > config file is the only way to make it work.  If you know a better way to 
> > > fix
> > > this, I will be happy to see it.
> [...]
> >  The problem is CONFIG_SERIAL having different meanings for the MIPS port. 
> > It causes annoyance with dynamic parsers (like `make config') and I'm not
> > surprised it breaks the xconfig static parser. 
> 
>  I renamed the guilty options and also I decided moving DECstation serial
> port configuration to drivers/char is the way to go.  As a side effect you
> now may build both the dz11/z8530 drivers and the i8250 one (as an advance
> towards a generic kernel).
> 

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