From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: missing mxcsr initialization
Date: 27 Oct 2000 12:07:58 -0700 [thread overview]
Message-ID: <8tcjqe$8te$1@cesium.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10010262229330.864-100000@penguin.transmeta.com> <E13p7te-0004MB-00@the-village.bc.nu>
Followup to: <E13p7te-0004MB-00@the-village.bc.nu>
By author: Alan Cox <alan@lxorguk.ukuu.org.uk>
In newsgroup: linux.dev.kernel
> >
> > and it appears to work again, until it turns out that Cyrix has the same
> > issue, and then it ends up being the test from hell, where different
> > vendor tests all clash, and it gets increasingly difficult to add a new
> > thing later on sanely.
>
> And you end up with mtrr.c
>
Indeed.
>
> > No thank you. We'll just require fixed feature flags. Which can be turned
> > on as the features are enabled.
>
> That seems sensible
>
I'm working on the patch right now.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-10-27 19:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10010260835340.2335-100000@penguin.transmeta.com>
2000-10-27 0:39 ` missing mxcsr initialization Alan Cox
2000-10-27 5:35 ` Linus Torvalds
2000-10-27 11:42 ` Alan Cox
2000-10-27 19:07 ` H. Peter Anvin [this message]
[not found] <20001026021731.B23895@athlon.random>
2000-10-27 1:15 ` Alan Cox
2000-10-27 7:34 ` H. Peter Anvin
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='8tcjqe$8te$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@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