public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nicholas Knight <tegeran@home.com>
To: Arjan van de Ven <arjanv@redhat.com>,
	Chris Abbey <linux@cabbey.net>,
	linux-kernel@vger.kernel.org
Subject: Re: Athlon doesn't like Athlon optimisation?
Date: Fri, 31 Aug 2001 02:36:19 -0700	[thread overview]
Message-ID: <01083102361900.00249@c779218-a> (raw)
In-Reply-To: <Pine.LNX.4.30.0108302117150.16904-100000@anime.net> <Pine.LNX.4.33.0108302353380.4964-100000@tweedle.cabbey.net> <3B8F4A64.8B9DEDE4@redhat.com>
In-Reply-To: <3B8F4A64.8B9DEDE4@redhat.com>

On Friday 31 August 2001 01:27 am, Arjan van de Ven wrote:

<snip>

> Now I also wrote the 2 functions in question, and I am
> very convinced that they are correct. They also work on
> the vast majority of motherboards, and most of the failure
> cases are cheaper motherboards (or cheap PSU's).

Want cheap hardware?
Slot-A Athlon 800Mhz non-tbird
Soyo K7VIA motherboard, VIA KX133 chipset
Generic 300W power supply bought from mwave

and, for the other hardware:

1 DVD-ROM drive
1 Plextor PlexWriter CD-RW drive
1 IBM 75GXP 7200RPM 45GB ATA/100 drive
1 Promise ATA/100 HDD controller
1 350MB Western Digital Caviar drive, but this powers down completely 
when not in use
2 Generic 80mm case fans
1 low-end HSF unit with three small fans
1 GeForce2MX
1 stick of generic 256MB PC133 SDRAM that refuses to run at 133Mhz
1 ISA NIC
1 PCI NIC
1 floppy drive, sony I think, otherwise generic

I have never experienced problems with Athlon optimizations, and I 
*always* compile with them enabled.

Prehaps the key lies in Thunderbird vs Non-Thunderbird? When did these 
problems start showing up, and at what clock speeds? What motherboards? 
What chipsets?

>Greetings,
>     Arjan van de Ven

  reply	other threads:[~2001-08-31  9:37 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-31  2:42 Athlon doesn't like Athlon optimisation? Jan Niehusmann
2001-08-31  3:07 ` David Hollister
2001-08-31  3:34   ` Albert D. Cahalan
2001-08-31  3:50     ` Richard Gooch
2001-08-31  4:20     ` Dan Hollis
2001-08-31  5:05       ` Chris Abbey
2001-08-31  8:27         ` Arjan van de Ven
2001-08-31  9:36           ` Nicholas Knight [this message]
2001-08-31 14:17           ` David Hollister
2001-08-31  6:02       ` Paul G. Allen
2001-08-31  6:15         ` Steven Spence
2001-08-31 14:06         ` Alan Cox
2001-08-31  9:21       ` Phillip Susi
     [not found]       ` <l4nnm9.rqp.ln@schlich.user.dfncis.de>
2001-08-31 13:58         ` Athlon doesn't like Athlon optimisation? [PATCH] Radu-Adrian Feurdean
2001-08-31 14:00       ` Athlon doesn't like Athlon optimisation? Alan Cox
2001-08-31 20:37         ` Dan Hollis
2001-08-31 20:53           ` Alan Cox
2001-09-08 18:01             ` Eric W. Biederman
2001-08-31 20:53           ` Mike Fedyk
2001-08-31  8:08   ` Joerg Plate
2001-08-31 18:18   ` Tim Moore
2001-08-31 19:17     ` Bobby D. Bryant
2001-08-31 19:43       ` Tim Moore
2001-09-01 10:06   ` Jim Roland
2001-09-01 12:04     ` Joerg Plate
2001-09-01 14:39     ` David Hollister
2001-09-01 15:50       ` Alan Cox
2001-09-01 16:27         ` David Hollister
2001-09-03  8:03       ` Jim Roland
     [not found] <fa.kt7mv6v.qiq718@ifi.uio.no>
     [not found] ` <fa.j3okgqv.lmova7@ifi.uio.no>
2001-08-31 12:11   ` Dan Maas
  -- strict thread matches above, loose matches on Subject: below --
2001-09-03  8:13 Eric Olson
2001-09-03 15:55 ` Ghozlane Toumi
2001-09-04 10:19   ` Dan Hollis
2001-09-04  9:35 ` Matthew S . Hallacy
2001-09-05  5:21 Eric Olson
2001-09-05  9:59 ` Matthew S . Hallacy
2001-09-05 15:56 ` David Hollister
2001-09-05 14:22 noneuclidean
2001-09-05 17:37 ` Simen Thoresen
2001-09-05 18:07 ` Dan Hollis
2001-09-05 18:37 Eric Olson
2001-09-07  7:33 Jim Blomo
2001-09-07  8:00 ` Dan Hollis
2001-09-07  8:39 ` Andrzej Krzysztofowicz
2001-09-07 17:25   ` Mike Fedyk
2001-09-23 10:04 Jim Blomo

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=01083102361900.00249@c779218-a \
    --to=tegeran@home.com \
    --cc=arjanv@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@cabbey.net \
    /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