From: Jason White <jasonw@ariel.ucs.unimelb.EDU.AU>
To: blinux-list@redhat.com
Subject: Re: processors question
Date: Sun, 13 Dec 1998 14:03:47 +1100 (AEDT) [thread overview]
Message-ID: <Pine.SUN.3.95.981213140107.22625C-100000@ariel.ucs.unimelb.EDU.AU> (raw)
In-Reply-To: <Pine.BSI.4.01.9812122052440.3282-100000@msn.globaldialog.com>
Read the Linux hardware compatibility HOWTO, especially the section on
processors, which mentions certain CPU's that contain bugs for which it
has not been possible to find a solution (apparently the kernel developers
have included features which avoid the bugs relevant to particular
processors).
prev parent reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
Jude Dashiell
` John Schucker
` Jason White [this message]
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=Pine.SUN.3.95.981213140107.22625C-100000@ariel.ucs.unimelb.EDU.AU \
--to=jasonw@ariel.ucs.unimelb.edu.au \
--cc=blinux-list@redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).