On Fri, 27 Nov 1998 17:20:49 -0500 (EST), Todd Vierling wrote:
>On Thu, 26 Nov 1998, Michael VanLoon wrote:
>
>: >What do the CYRIX_CACHE_[REALLY_]WORKS defines mean? And what are =
they
>: >supposed to do besides changing the message? I think we need someone
>: >more knowing than us to answer the question :-)
>
>: The CYRIX_CACHE_WORKS setting was for enabling the paranoid mode on =
386
>: motherboards, so you got some benefit, but it was still fairly safe on
>: most decent motherboards.
>:=20
>: The CYRIX_CACHE_REALLY_WORKS setting was for enabling the full-caching
>: mode on boards that didn't set it up correctly in the BIOS, but where
>: hardware support worked (or where there weren't any bus-master devices
>: in the system and you were willing to run in "risky" mode).
>
>If these exist, they should be made into kernel options and put into =
GENERIC
>(albeit commented out) with comments indicating what they do.

I just looked for CYRIX_CACHE in the /sys/arch/i386 tree, and it seems
it's only in /sys/arch/i386/i386/machdep.c in the piece of code that
prints the message.=20

So I'd suggest that the code is removed except for the 'UNCHANGED'
message. This message is ok, because it tells us 486DLC users that the
cache setting is left to the motherboard and that NetBSD does'nt try
to do anything better (I don't suppose anyone will be optimizing
NetBSD for this old cpu?)

Anders
- running NetBSD 1.3.2/i386 on an 8 MB 486DLC-40 machine as Internet
gateway, file server and for hacking.