linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: tegeran@home.com
Cc: VDA@port.imtp.ilyichevsk.odessa.ua (VDA),
	brian@worldcontrol.com, linux-kernel@vger.kernel.org
Subject: Re: Re[2]: Athlon: Try this (was: Re: Athlon bug stomping #2)
Date: Thu, 20 Sep 2001 13:34:52 +0100 (BST)	[thread overview]
Message-ID: <E15k32a-0005BW-00@the-village.bc.nu> (raw)
In-Reply-To: <01091920173800.01212@c779218-a> from "Nicholas Knight" at Sep 19, 2001 08:17:38 PM

> It seems the 3DNow! copy routines have issues with the southbridge chip 
> in the KT133A, this results in performances degrading while playing for a 
> while. Re-compile your kernel without 3DNow! instructions to avoid the 
> problem, and wait for newer kernels with better support for 3DNow! / 
> KT133A.> 

I have no data of any kind to remotely substantiate that claim. I would
have expected to see such data if it existed.

Alan

  reply	other threads:[~2001-09-20 12:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-13 12:31 Athlon bug stomping #2 VDA
2001-09-14  2:56 ` Roberto Jung Drebes
2001-09-14  4:02   ` Chris Vandomelen
2001-09-14  5:51     ` Eric W. Biederman
2001-09-14  7:34       ` Roberto Jung Drebes
2001-09-14  8:27         ` Athlon: Try this (was: Re: Athlon bug stomping #2) Roberto Jung Drebes
2001-09-14 18:19           ` Byron Stanoszek
2001-09-15 18:00             ` Liakakis Kostas
2001-09-15 20:28               ` VDA
2001-09-15  7:15           ` brian
2001-09-19  1:30             ` brian
2001-09-19 13:10             ` Re[2]: " VDA
2001-09-19 23:56               ` Nicholas Knight
2001-09-20  3:17                 ` Nicholas Knight
2001-09-20 12:34                   ` Alan Cox [this message]
2001-09-16 21:53           ` Carsten Leonhardt
2001-09-19  3:55             ` Dan Hollis
2001-09-14  9:26         ` Jeff Lightfoot

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=E15k32a-0005BW-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=VDA@port.imtp.ilyichevsk.odessa.ua \
    --cc=brian@worldcontrol.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tegeran@home.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 NNTP newsgroup(s).