From: James E Wilson <wilson@tuliptree.org>
To: linux-ia64@vger.kernel.org
Subject: Re: anyone using Itanium B-step support?
Date: Fri, 28 Jan 2005 01:24:02 +0000 [thread overview]
Message-ID: <1106875442.18514.121.camel@aretha.corp.specifixinc.com> (raw)
In-Reply-To: <1106862995.18514.108.camel@aretha.corp.specifixinc.com>
[-- Attachment #1: Type: text/plain, Size: 227 bytes --]
On Thu, 2005-01-27 at 13:56, James E Wilson wrote:
> However, rather than add more ITANIUM_BSTEP_SPECIFIC support to the
> kernel, I think it makes more sense to obsolete it and remove it.
Here is the change I am suggesting.
[-- Attachment #2: patch.bstep.remove --]
[-- Type: text/x-patch, Size: 896 bytes --]
*** Kconfig.orig Sat Aug 14 03:56:22 2004
--- Kconfig Thu Jan 27 17:16:51 2005
*************** config IA64_BRL_EMU
*** 134,147 ****
depends on ITANIUM
default y
- config ITANIUM_BSTEP_SPECIFIC
- bool "Itanium B-step specific code"
- depends on ITANIUM
- help
- Select this option to build a kernel for an Itanium prototype system
- with a B-step CPU. You have a B-step CPU if the "revision" field in
- /proc/cpuinfo has a value in the range from 1 to 4.
-
# align cache-sensitive data to 128 bytes
config IA64_L1_CACHE_SHIFT
int
--- 134,139 ----
*** Makefile.orig Sat Aug 14 03:54:48 2004
--- Makefile Thu Jan 27 17:17:03 2005
*************** ifeq ($(GCC_VERSION),3)
*** 49,56 ****
endif
endif
- cflags-$(CONFIG_ITANIUM_BSTEP_SPECIFIC) += -mb-step
-
CFLAGS += $(cflags-y)
head-y := arch/ia64/kernel/head.o arch/ia64/kernel/init_task.o
--- 49,54 ----
next prev parent reply other threads:[~2005-01-28 1:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-27 21:56 anyone using Itanium B-step support? James E Wilson
2005-01-27 22:12 ` David Mosberger
2005-01-28 1:24 ` James E Wilson [this message]
2005-01-28 1:54 ` David Mosberger
2005-01-28 2:32 ` James E Wilson
2005-01-28 6:17 ` David Mosberger
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=1106875442.18514.121.camel@aretha.corp.specifixinc.com \
--to=wilson@tuliptree.org \
--cc=linux-ia64@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