From: Andrey Panin <pazke@orbita1.ru>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH: NEW SUBARCHITECTURE FOR 2.5.21] support for NCR voyager (3/4/5xxx series)
Date: Thu, 13 Jun 2002 12:20:53 +0400 [thread overview]
Message-ID: <20020613082053.GA614@pazke.ipt> (raw)
In-Reply-To: <200206091754.g59Hs0d08560@localhost.localdomain>
[-- Attachment #1.1: Type: text/plain, Size: 608 bytes --]
Attached patch is needed to compile kernel with Voyager patch applied
for the SMP PC machine.
Also some questions, mostly related to arch-split patch:
[Q1] Will it be better to create separate directory for PC architecture
and split some PC'isms from arch/i386/generic ? Right now it contains
acpi.c, bootflag.c and dmi_scan.c which are not generic in any way :)
[Q2] May be directory naming like mach-visws, mach-voyager and possible
mach-pc will be more convinent ?
--
Andrey Panin | Embedded systems software engineer
pazke@orbita1.ru | PGP key: wwwkeys.eu.pgp.net
[-- Attachment #1.2: patch-voyager --]
[-- Type: text/plain, Size: 1253 bytes --]
diff -urN -X /usr/share/dontdiff linux.vanilla/arch/i386/config.in linux/arch/i386/config.in
--- linux.vanilla/arch/i386/config.in Thu Jun 13 00:30:57 2002
+++ linux/arch/i386/config.in Wed Jun 12 20:25:15 2002
@@ -425,11 +425,6 @@
fi
fi
-if [ "$CONFIG_X86_LOCAL_APIC" = "y" ]; then
- define_bool CONFIG_X86_EXTRA_IRQS y
- define_bool CONFIG_X86_FIND_SMP_CONFIG y
-fi
-
endmenu
source lib/Config.in
@@ -443,6 +438,13 @@
if [ "$CONFIG_SMP" = "y" ]; then
define_bool CONFIG_X86_SMP y
define_bool CONFIG_X86_HT y
+ define_bool CONFIG_X86_IO_APIC y
+ define_bool CONFIG_X86_LOCAL_APIC y
fi
define_bool CONFIG_X86_BIOS_REBOOT y
+fi
+
+if [ "$CONFIG_X86_LOCAL_APIC" = "y" ]; then
+ define_bool CONFIG_X86_EXTRA_IRQS y
+ define_bool CONFIG_X86_FIND_SMP_CONFIG y
fi
diff -urN -X /usr/share/dontdiff linux.vanilla/arch/i386/generic/Makefile linux/arch/i386/generic/Makefile
--- linux.vanilla/arch/i386/generic/Makefile Thu Jun 13 00:30:50 2002
+++ linux/arch/i386/generic/Makefile Thu Jun 13 00:38:25 2002
@@ -18,7 +18,6 @@
obj-y := setup.o
-obj-$(CONFIG_PCI) += pci-pc.o pci-irq.o
obj-$(CONFIG_X86_LOCAL_APIC) += mpparse.o
include $(TOPDIR)/Rules.make
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-06-13 8:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-09 17:54 [PATCH: NEW SUBARCHITECTURE FOR 2.5.21] support for NCR voyager (3/4/5xxx series) James Bottomley
2002-06-13 8:20 ` Andrey Panin [this message]
2002-06-13 15:48 ` James Bottomley
2002-06-13 23:17 ` Dave Jones
2002-06-14 0:13 ` James Bottomley
2002-06-14 0:45 ` Dave Jones
2002-06-14 2:19 ` Matthew D. Pitts
2002-06-14 2:52 ` SCSI host/channel/lun/part to /dev/sd* or maj/minor mapping Mark Atwood
2002-06-14 13:41 ` [PATCH: NEW SUBARCHITECTURE FOR 2.5.21] support for NCR voyager (3/4/5xxx series) Andrey Panin
2002-06-14 13:49 ` Dave Jones
2002-06-14 13:52 ` Andrey Panin
2002-06-14 14:14 ` James Bottomley
2002-06-14 14:16 ` Dave Jones
2002-06-17 13:36 ` Andrey Panin
2002-06-17 14:03 ` Dave Jones
2002-06-16 0:00 ` James Bottomley
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=20020613082053.GA614@pazke.ipt \
--to=pazke@orbita1.ru \
--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