From owner-freebsd-hardware  Fri May 16 03:47:16 1997
Return-Path: <owner-hardware>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id DAA21601
          for hardware-outgoing; Fri, 16 May 1997 03:47:16 -0700 (PDT)
Received: from perki.connect.com.au (perki.connect.com.au [192.189.54.5])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA21594
          for <freebsd-hardware@freebsd.org>; Fri, 16 May 1997 03:47:10 -0700 (PDT)
Received: from nemeton.UUCP (Unemeton@localhost) by perki.connect.com.au with UUCP id UAA24593
  (8.8.5/IDA-1.6 for freebsd-hardware@freebsd.org); Fri, 16 May 1997 20:46:32 +1000 (EST)
Received: from localhost.nemeton.com.au (localhost.nemeton.com.au [127.0.0.1])
	by nemeton.com.au (8.8.5/8.8.5) with SMTP id UAA28290
	for <freebsd-hardware@freebsd.org>; Fri, 16 May 1997 20:40:19 +1000 (EST)
Message-Id: <199705161040.UAA28290@nemeton.com.au>
To: freebsd-hardware@freebsd.org
Subject: Cyrix 486DX2 and write through cache?
Date: Fri, 16 May 1997 20:40:19 +1000
From: Giles Lean <giles@nemeton.com.au>
Sender: owner-hardware@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


[This question has been asked before on the list, but I couldn't
 see an answer in the archive.]

Does anyone know of a way to force a Cyrix Cx486DX2 to use its
internal cache in write through mode rather than write back?

Even crash and burn testing would go faster if I could re-enable
the internal cache. :-)

Regards,

Giles