From: Uros Prestor <uros@turbolinux.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] binary kernel module build flags
Date: Thu, 14 Dec 2000 18:26:50 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205844@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205824@msgid-missing>
On Thu, 14 Dec 2000, E. Focht wrote:
> Please don't drop the A-stepping support too early! Most of our machines
> and half of our processors are still A3 step! And they probably won't be
> upgraded before February 2001.
The support for A-stepping processors seriously limits the amount of
optimizations you can do. It's not just the workarounds in the kernel,
it's also the fact that you can't use optimized memory copy routines, for
example. You should really work with Intel to get your boxes upgraded.
> As far as I understand, Turbolinux boots the uniprocessor kernel on A-step
> CPUs but it's config file stored in the configs directory doesn't have
> A-stepping support enabled. The beta2 TurboLinux distribution raises
> serious problems, one must recompile kernel and toolchain in order to be
> able to work without crashing every few minutes on an A3 stepping
> CPU. And I'm not using X or GNOME...
The A-step support in Beta2 was included just to help with the
install. It was not thoroughly tested (we don't have any A-step boxes
anyway). The config files included with kernel-source are for the regular
kernels. The only difference for the install kernel was to enable the
A-step workarounds.
You are right that you need to recompile the kernel and the
toolchain. You should probably recompile the glibc as well (and remove
the optimized memory copy routines).
Uros
next prev parent reply other threads:[~2000-12-14 18:26 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
2000-12-14 14:36 ` E. Focht
2000-12-14 18:26 ` Uros Prestor [this message]
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-105590678205844@msgid-missing \
--to=uros@turbolinux.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