Date: Thu, 31 Jan 2002 16:24:48 -0800 From: Terry Lambert <tlambert2@mindspring.com> To: "Cameron, Frank" <Cameron@ctc.com> Cc: 'Kenneth Culver' <culverk@yumyumyum.org>, David Malone <dwmalone@maths.tcd.ie>, "'freebsd-bugs@freebsd.org'" <freebsd-bugs@FreeBSD.ORG>, "'freebsd-current@freebsd.org'" <freebsd-current@FreeBSD.ORG> Subject: Re: AMD AGP Bug Message-ID: <3C59E050.6564C115@mindspring.com> References: <7925FCEF327F984DB5885285256F0D3AC9446F@nsc-mail1.nsc.ctc.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"Cameron, Frank" wrote: > From what was posted on the linux-kernel list the problem is the OS > doing the wrong thing not the hardware. I originally asked the > question (albeit not worded as clearly as I should have) because if > Microsoft and Linux programmers made the same mistake, might > FreeBSD have also. No. FreeBSD does not make active use of 4M pages for anything other than the initial kernel text and data, which is obvious, if you look at /sys/i386/machdep.c. For Linux and Windows, the obvious thing is to not map the memory into an aperture marked cacheable and in a 4M page; it's a coding problem with the use of 4M pages, when memory in them is allocated to AGP. This still doesn't get around the other bug, which happens if you use 4M pages certain obviously useful ways, without waving a dead chicken over certain things. 8-). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3C59E050.6564C115>