public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@fs.tum.de>
To: James.Bottomley@HansenPartnership.com
Cc: linux-kernel@vger.kernel.org
Subject: RFC: [2.5 patch] Create a "Subarchitecture" menu
Date: Sat, 16 Nov 2002 22:15:36 +0100	[thread overview]
Message-ID: <20021116211536.GF28356@fs.tum.de> (raw)

My impression is that it's currently easy to accidentially activate the
Voyager support in 2.5.47 by typing once too often "y" which results in
a kernel that doesn't boot on a PC. The patch below is a suggestion to
to create a "Subarchitecture" choice.

The wording might not be perfect and it might make sense to add other
subarchs there, too. I'm interested in comments whether this is a good
idea or whether there are reasons why this is a bad idea.

TIA
Adrian


--- linux-2.5.47-full/arch/i386/Kconfig.old	2002-11-16 21:36:44.000000000 +0100
+++ linux-2.5.47-full/arch/i386/Kconfig	2002-11-16 22:02:47.000000000 +0100
@@ -39,7 +39,33 @@
 menu "Processor type and features"
 
 choice
+	prompt "Subarchitecture"
+	default PC
+
+config PC
+	bool "PC"
+	help
+	  Choose this option if your computer is a PC.
+
+	  Choose this option unless you really know what you are doing.
+
+config VOYAGER
+	bool "Support for the NCR Voyager Architecture"
+	help
+	  Voyager is a MCA based 32 way capable SMP architecture proprietary
+	  to NCR Corp.  Machine classes 345x/35xx/4100/51xx are voyager based.
+  
+	  *** WARNING ***
+
+	  If you do not specifically know you have a Voyager based machine,
+	  don't choose this option otherwise the kernel you build will not
+	  be bootable.
+
+endchoice
+
+choice
 	prompt "Processor family"
+	depends on PC
 	default M686
 
 config M386
@@ -980,17 +1006,6 @@
 
 menu "Bus options (PCI, PCMCIA, EISA, MCA, ISA)"
 
-config VOYAGER
-	bool "Support for the NCR Voyager Architecture"
-	depends on MCA
-	help
-	  Voyager is a MCA based 32 way capable SMP architecture proprietary
-	  to NCR Corp.  Machine classes 345x/35xx/4100/51xx are voyager based.
-  
-	  *** WARNING ***
-
-	  If you do not specifically know you have a Voyager based machine,
-	  say N here otherwise the kernel you build will not be bootable.
 
 # Visual Workstation support is utterly broken.
 # If you want to see it working mail an VW540 to hch@infradead.org 8)
@@ -1102,8 +1117,12 @@
 	  Otherwise, say N.
 
 config MCA
+	bool
+	depends on VOYAGER
+
+config MCA
 	bool "MCA support"
-	depends on !VISWS
+	depends on !VISWS && !VOYAGER
 	help
 	  MicroChannel Architecture is found in some IBM PS/2 machines and
 	  laptops.  It is a bus system similar to PCI or ISA. See

                 reply	other threads:[~2002-11-16 21:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20021116211536.GF28356@fs.tum.de \
    --to=bunk@fs.tum.de \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=linux-kernel@vger.kernel.org \
    /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