From: Chris Wedgwood <cw@f00f.org>
To: Joseph Carter <knghtbrd@debian.org>
Cc: Aaron Tiensivu <mojomofo@mojomofo.com>, linux-kernel@vger.kernel.org
Subject: Re: REVISED: Experimentation with Athlon and fast_page_copy
Date: Sat, 5 May 2001 15:51:13 +1200 [thread overview]
Message-ID: <20010505155113.D29451@metastasis.f00f.org> (raw)
In-Reply-To: <E14vmpN-000822-00@the-village.bc.nu> <006e01c0d4e9$3c0bd210$0300a8c0@methusela> <20010504172657.B14969@debian.org>
In-Reply-To: <20010504172657.B14969@debian.org>; from knghtbrd@debian.org on Fri, May 04, 2001 at 05:26:57PM -0700
On Fri, May 04, 2001 at 05:26:57PM -0700, Joseph Carter wrote:
I don't see how they figure, but in case there was any doubt I
have a VIA KT133A/686B board (Abit KT7A) and don't experience
anything resembling disk corruption unless the box crashes for
some other reason. I do seem to be experiencing AGP problems in
spades, but my disks at least are fine.
I too seem no disk problems whatsoever (nothing really interesting
there, many people do not) but am also seeing AGP problems.
In fact, I had to disable AGP to stop X locking the box hard... yet
agpgart and the video driver (NVidia[1]) both claim to support the
chipset -- does anyone actually have this working?)
--cw
[1] Yeah, close source, blah blah blah. Right now it works for me,
and it works _VERY_ well.
next prev parent reply other threads:[~2001-05-05 3:51 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-04 17:22 REVISED: Experimentation with Athlon and fast_page_copy Seth Goldberg
2001-05-04 19:48 ` Brian Gerst
2001-05-04 21:09 ` Alan Cox
2001-05-04 22:26 ` Aaron Tiensivu
2001-05-04 18:10 ` Bobby D. Bryant
2001-05-05 6:43 ` John R Lenton
2001-05-05 7:20 ` Alan Cox
2001-05-07 1:26 ` John R Lenton
2001-05-07 1:30 ` Jeremy
2001-05-05 0:26 ` Joseph Carter
2001-05-05 3:51 ` Chris Wedgwood [this message]
2001-05-05 4:08 ` Seth Goldberg
[not found] ` <20010505163204.A29622@metastasis.f00f.org>
2001-05-05 5:03 ` Athlon and fast_page_copy: What's it worth ? :) Seth Goldberg
2001-05-05 6:20 ` Mark Hahn
2001-05-05 9:15 ` Tom Leete
2001-05-05 7:17 ` Alan Cox
2001-05-05 14:19 ` Jonathan Morton
2001-05-05 14:41 ` Alan Cox
2001-05-05 15:17 ` Jonathan Morton
2001-05-08 21:16 ` Arjan van de Ven
2001-05-05 5:45 ` REVISED: Experimentation with Athlon and fast_page_copy Joseph Carter
2001-05-09 2:11 ` Tom Leete
2001-05-09 8:49 ` Alan Cox
2001-05-09 11:38 ` Tom Leete
2001-05-09 12:38 ` Alan Cox
2001-05-09 13:02 ` Tom Leete
-- strict thread matches above, loose matches on Subject: below --
2001-05-04 19:14 Manfred Spraul
2001-05-04 19:30 ` Seth Goldberg
2001-05-04 21:43 ` Alan Cox
2001-05-08 21:15 ` Arjan van de Ven
2001-05-05 2:28 Dieter Nützel
2001-05-05 7:13 ` Alan Cox
2001-05-09 23:56 ` Dieter Nützel
2001-05-05 17:34 Jeremy
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=20010505155113.D29451@metastasis.f00f.org \
--to=cw@f00f.org \
--cc=knghtbrd@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mojomofo@mojomofo.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