From: Martin Michlmayr <tbm@cyrius.com>
To: akpm@osdl.org
Cc: linux-kernel@vger.kernel.org, linux-mips@linux-mips.org
Subject: [PATCH 1/12] [MIPS] Improve description of VR41xx based machines
Date: Mon, 20 Mar 2006 04:39:02 +0000 [thread overview]
Message-ID: <20060320043902.GA20416@deprecation.cyrius.com> (raw)
In-Reply-To: <20060320043802.GA20389@deprecation.cyrius.com>
MIPS supports various NEC VR41XX chips and not just the VR4100.
Update Kconfig accordingly, thereby bringing the file in sync with
the linux-mips tree.
Signed-off-by: Martin Michlmayr <tbm@cyrius.com>
--- linux-2.6/arch/mips/Kconfig 2006-03-13 18:45:54.000000000 +0000
+++ mips.git/arch/mips/Kconfig 2006-03-20 03:22:02.000000000 +0000
@@ -503,7 +503,7 @@
ether port USB, AC97, PCI, etc.
config MACH_VR41XX
- bool "Support for NEC VR4100 series based machines"
+ bool "Support for NEC VR41XX-based machines"
select SYS_HAS_CPU_VR41XX
select SYS_SUPPORTS_32BIT_KERNEL
select SYS_SUPPORTS_64BIT_KERNEL if EXPERIMENTAL
@@ -1134,7 +1134,7 @@
select CPU_SUPPORTS_32BIT_KERNEL
select CPU_SUPPORTS_64BIT_KERNEL
help
- The options selects support for the NEC VR4100 series of processors.
+ The options selects support for the NEC VR41xx series of processors.
Only choose this option if you have one of these processors as a
kernel built with this option will not run on any other type of
processor or vice versa.
--
Martin Michlmayr
http://www.cyrius.com/
next prev parent reply other threads:[~2006-03-20 4:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-20 4:38 Bring mainline in sync with the linux-mips tree Martin Michlmayr
2006-03-20 4:39 ` Martin Michlmayr [this message]
2006-03-20 6:26 ` [PATCH 1/12] [MIPS] Improve description of VR41xx based machines Yoichi Yuasa
2006-03-20 13:10 ` Martin Michlmayr
2006-03-20 15:59 ` Yoichi Yuasa
2006-03-20 16:29 ` Martin Michlmayr
2006-03-21 2:10 ` Yoichi Yuasa
2006-03-21 2:18 ` Martin Michlmayr
2006-03-22 7:53 ` Yoichi Yuasa
2006-03-22 10:07 ` Martin Michlmayr
2006-03-20 4:39 ` [PATCH 2/12] [MIPS] Cosmetic updates to sync with linux-mips Martin Michlmayr
2006-03-20 6:31 ` Yoichi Yuasa
2006-03-20 13:11 ` Martin Michlmayr
2006-03-21 2:12 ` Yoichi Yuasa
2006-03-20 4:39 ` [PATCH 3/12] [MIPS] Remove tb0287_defconfig Martin Michlmayr
2006-03-20 6:23 ` Yoichi Yuasa
2006-03-20 4:39 ` [PATCH 4/12] [NET] Improve description of MV643XX_ETH Martin Michlmayr
2006-03-20 4:39 ` [PATCH 5/12] [NET] Bring declance.c in sync with linux-mips tree Martin Michlmayr
2006-03-20 4:40 ` [PATCH 6/12] [NET] Support the BCM1x55 and BCM1x80 chips Martin Michlmayr
2006-03-20 4:40 ` [PATCH 7/12] [IDE] Set CFLAGS only for au1xxx-ide Martin Michlmayr
2006-03-20 4:40 ` [PATCH 8/12] [MTD] Re-add module description for ms02-nv to Kconfig Martin Michlmayr
2006-03-20 4:40 ` [PATCH 9/12] [MTD] Fix #else directive in the docprobe driver Martin Michlmayr
2006-03-20 4:40 ` [PATCH 10/12] [MTD] LASAT depends on MTD_CFI Martin Michlmayr
2006-03-20 4:41 ` [PATCH 11/12] [USB] Cosmetic changes to bring ohci-au1xxx.c in sync with linux-mips Martin Michlmayr
2006-03-20 4:41 ` [PATCH 12/12] [SCSI] mem_start is a physical address already Martin Michlmayr
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=20060320043902.GA20416@deprecation.cyrius.com \
--to=tbm@cyrius.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.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