From: Joseph V Moss <jmoss@ichips.intel.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: Lockups on 2.4.1
Date: Sat, 24 Feb 2001 23:18:38 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005199@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005175@msgid-missing>
> On Fri, 23 Feb 2001, Jesse Barnes wrote:
>
> >
> > This seems like the sort of info that should be in Configure.help. Anyone
> > interested in posting a patch to add it?
> >
>
> As attachment. This is over 2.4.1 + 010131 ia64 patch. I also added help for
> B1/B2 specific stuff. Please verify that it is correct...
You've got a small cut'n'paste error there:
> +Enable Itanium B1-step specific code
> +CONFIG_ITANIUM_B1_SPECIFIC
> + Select this option to bild a kernel for an Itanium prototype system
> + with a B1-step CPU. You have a B0-step CPU if the "revision" field in
^^
> + /proc/cpuinfo is 2.
> +
> +Enable Itanium B2-step specific code
> +CONFIG_ITANIUM_B2_SPECIFIC
> + Select this option to bild a kernel for an Itanium prototype system
> + with a B2-step CPU. You have a B0-step CPU if the "revision" field in
^^
> + /proc/cpuinfo is 3.
> +
next prev parent reply other threads:[~2001-02-24 23:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-21 16:05 [Linux-ia64] Re: Lockups on 2.4.1 Bill Nottingham
2001-02-21 17:16 ` Gerrit Huizenga
2001-02-21 17:57 ` David Mosberger
2001-02-21 18:58 ` Chris McDermott
2001-02-21 21:02 ` David Mosberger
2001-02-23 15:19 ` Jun Nakajima
2001-02-23 19:06 ` Seth, Rohit
2001-02-23 19:20 ` Michael Madore
2001-02-23 19:48 ` Seth, Rohit
2001-02-23 20:00 ` Jesse Barnes
2001-02-24 13:39 ` Francis Galiegue
2001-02-24 14:44 ` Francis Galiegue
2001-02-24 18:45 ` Michael Madore
2001-02-24 23:18 ` Joseph V Moss [this message]
2001-02-25 2:43 ` Francis Galiegue
2001-02-26 20:52 ` Jim Wilson
2001-03-07 3:51 ` [linux-ia64] " Tom King
2001-03-07 20:34 ` Jim Wilson
2001-03-08 3:45 ` Tom King
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=marc-linux-ia64-105590693005199@msgid-missing \
--to=jmoss@ichips.intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.