From: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: Jesper Juhl <jesper.juhl@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
billm@melbpc.org.au, billm@suburbia.net
Subject: Re: Math-emu kills the kernel on Athlon64 X2
Date: Wed, 20 Sep 2006 01:48:40 +0100 [thread overview]
Message-ID: <1158713320.3098.15.camel@localhost.portugal> (raw)
In-Reply-To: <m3fyeof3c7.fsf@defiant.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1035 bytes --]
On Tue, 2006-09-19 at 14:28 +0200, Krzysztof Halasa wrote:
> Sergio Monteiro Basto <sergio@sergiomb.no-ip.org> writes:
> > I think, math emulation is for 486 and older. 486 DX2 was the first one
> > who have math co processor, on earlier processor it should be disable .
>
> Actually, 486 DX had built-in FPU as well. It was missing from 486SX
> (486SX + optional 487 FPU = 486DX).
>
> For 386(DX|SX) there were 387(DX|SX) (386SX used 16-bit bus).
>
> Many 32-bit motherboards had a socket for Weitek (3167 for 386DX or 4167
> for 486). I think I remember a board with 386DX and 287 socket as well.
>
> 486DX2 meant the external clock was half the internal.
Fine :), My (12 year old) 486DX2 already don't need Math-emu. I just
don't see how in a computer like that will be installed a kernel 2.6 .
So why code of math-emu isn't dropped ?
Btw I try install a kernel 2.4 in my DX2 and works but very very slow .
I think in this type of computer should be install a kernel 2.2 .
Thanks,
--
Sérgio M.B.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2166 bytes --]
next prev parent reply other threads:[~2006-09-20 0:49 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-18 22:18 Math-emu kills the kernel on Athlon64 X2 Jesper Juhl
2006-09-18 22:52 ` Linus Torvalds
2006-09-18 23:14 ` Jesper Juhl
2006-09-18 23:49 ` Linus Torvalds
2006-09-19 0:47 ` Jesper Juhl
2006-09-19 2:18 ` Linus Torvalds
2006-09-18 23:49 ` Sergio Monteiro Basto
2006-09-19 0:02 ` Jesper Juhl
2006-09-19 12:28 ` Krzysztof Halasa
2006-09-20 0:48 ` Sergio Monteiro Basto [this message]
2006-09-20 22:31 ` Krzysztof Halasa
2006-09-19 8:01 ` Andi Kleen
2006-09-19 8:31 ` Jesper Juhl
2006-09-19 21:14 ` Jesper Juhl
2006-09-19 22:01 ` Linus Torvalds
2006-09-19 22:16 ` Jesper Juhl
2006-09-19 22:44 ` Jesper Juhl
2006-10-03 2:16 ` [PATCH/RFC] " Randy Dunlap
2006-10-03 2:34 ` Linus Torvalds
2006-10-03 3:24 ` Randy Dunlap
2006-10-03 10:05 ` Andi Kleen
2006-10-03 14:54 ` Linus Torvalds
2006-10-03 10:11 ` [PATCH/RFC] Math-emu kills the kernel on Athlon64 X2 II -- it's terminally broken Andi Kleen
2006-10-03 11:53 ` Alan Cox
2006-10-03 14:48 ` Linus Torvalds
2006-10-03 4:38 ` [PATCH/RFC] Math-emu kills the kernel on Athlon64 X2 Randy Dunlap
2006-10-03 11:30 ` Alan Cox
2006-10-03 15:10 ` Linus Torvalds
2006-10-03 16:23 ` Randy Dunlap
2006-10-03 16:37 ` Linus Torvalds
2006-10-03 16:49 ` Randy Dunlap
2006-10-03 16:51 ` Linus Torvalds
2006-10-04 19:24 ` Jesper Juhl
2006-10-04 19:43 ` Linus Torvalds
2006-10-04 20:02 ` Jesper Juhl
2006-10-04 22:00 ` Alan Cox
2006-10-04 21:44 ` Andi Kleen
2006-09-20 8:16 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2006-09-20 8:15 linux
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=1158713320.3098.15.camel@localhost.portugal \
--to=sergio@sergiomb.no-ip.org \
--cc=billm@melbpc.org.au \
--cc=billm@suburbia.net \
--cc=jesper.juhl@gmail.com \
--cc=khc@pm.waw.pl \
--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 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.