From: David Hollister <david@digitalaudioresources.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jim Roland <jroland@roland.net>, Jan Niehusmann <jan@gondor.com>,
linux-kernel@vger.kernel.org
Subject: Re: Athlon doesn't like Athlon optimisation?
Date: Sat, 01 Sep 2001 09:27:32 -0700 [thread overview]
Message-ID: <3B910C74.5030407@digitalaudioresources.org> (raw)
In-Reply-To: <E15dD2V-0005ER-00@the-village.bc.nu>
Alan Cox wrote:
>>I'm on 2.4.9. No overclocking. I applied the patch that somebody (sorry,
>>forgot who) posted yesterday for arch/i386/lib/mmx.c and rebuilt the kernel with
>>Athlon optimization. It now works.
>>
>
> Well not really. The patch posted turns off athlon optimisation even though
> you selected it
Well, that's what I thought, too, since that was the only file in the kernel
source where CONFIG_MK7 was defined. Somebody pointed out to me, though, that
there are other defines that are turned on if you use Athlon settings, like
(from arch/i386/config.in):
CONFIG_X86_GOOD_APIC
CONFIG_X86_USE_3DNOW
CONFIG_X86_PGE
Although, looking at arch/i386/config.in again right now, I see none of these
are Athlon specific. That's what I get for trusting somebody else instead of
looking into it myself.
Thanks.
--
David Hollister
Driversoft Engineering: http://devicedrivers.com
Digital Audio Resources: http://digitalaudioresources.org
next prev parent reply other threads:[~2001-09-01 16:27 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
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 [this message]
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=3B910C74.5030407@digitalaudioresources.org \
--to=david@digitalaudioresources.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jan@gondor.com \
--cc=jroland@roland.net \
--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.