Date: Wed, 08 Mar 2000 10:00:06 -0800 From: Mike Smith <msmith@freebsd.org> To: Coleman Kane <cokane@one.net> Cc: Roman Shterenzon <roman@ksl.co.il>, green@freebsd.org, stable@freebsd.org Subject: Re: K6-MTRRs Message-ID: <200003081800.KAA03550@mass.cdrom.com> In-Reply-To: Your message of "Wed, 08 Mar 2000 12:38:38 EST." <20000308123838.C20193@evil.2y.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> Roman Shterenzon had the audacity to say: > > What models/revisions seem to be broken? > > I *think* that K6-2 mtrr works. > > > > That's the impression I was under. I have gotten no information from AMD to say > that the MTRRs on their K6-2 line don't work. The only things I know of is that > the first-gen chips didn't have them, and the code checks for that. Are you sure > that it isn't some interpretation problem with the tech docs? If the original K6's don't have memory range registers, how could we have tested them and discovered they didn't work? At any rate, you're encouraged to talk to the author/maintainer of the code, Brian Feldman (copied). If you can make it work, wonderful. > > On Mon, 6 Mar 2000, Mike Smith wrote: > > > > > > Well, I know that they are different form those on the PII/III line, > > > > and that there are only two. I think that they are implemented in some > > > > windows drivers and programs. Maybe whoever is in charge of it could > > > > contact me, I have some AMD tech docs and maybe I could take a crack at > > > > it. > > > > > > I'm not sure I follow you. We have implemented support for the K6 memory > > > range registers, and having done so, discovered that they don't behave > > > like they should. Thus, support was disabled for these CPUs. There's > > > nothing more to do, as far as I'm aware - the hardware itself is broken. > > > > > > > --cokane > > > > > > > > Mike Smith had the audacity to say: > > > > > > I know that the k6 mtrr code is broken. Who is actively working on > > > > > > this? I have been messing with it and know that it screws up the > > > > > > framebuffer writes in xfree86 4.0. It prevents the writes of certain > > > > > > parts of the pixel values. > > > > > > > > > > Evidence suggests that the problem is actually in the K6 itself. > > > > > > > > > > -- > > > > > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > > > > > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > > > > > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com > > > > > > > > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > > with "unsubscribe freebsd-stable" in the body of the message > > > > > > -- > > > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > > > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > > > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-stable" in the body of the message > > > > > > > --Roman Shterenzon, UNIX System Administrator and Consultant > > [ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ] > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200003081800.KAA03550>