From: Jim Wilson <wilson@cygnus.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] binary kernel module build flags
Date: Wed, 13 Dec 2000 21:09:18 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205827@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205824@msgid-missing>
You shouldn't worry about A-step or B0-step processors unless you personally
are still using them because you haven't gotten upgrades yet. I'd like to
eliminate the compiler -ma-step option before gcc3 comes out, which means it
won't be in the next compiler release. Meanwhile, if you must use A-step or
B0-step processors, then you must use the -ma-step compiler option. Otherwise,
I recommend using -mb-step for now, which will support B1 and higher processor
steppings.
The current round of OS releases are coming out with B step kernel support only
by default, and A step support is provided with an optional kernel (TurboLinux)
or not at all (Red Hat).
Jim
next prev parent reply other threads:[~2000-12-13 21:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-13 19:38 [Linux-ia64] binary kernel module build flags John Kohl
2000-12-13 21:09 ` Jim Wilson [this message]
2000-12-14 14:36 ` E. Focht
2000-12-14 18:26 ` Uros Prestor
2000-12-14 20:31 ` Jim Wilson
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-105590678205827@msgid-missing \
--to=wilson@cygnus.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox