As Brian F. Feldman wrote ...
> On Sun, 5 Sep 1999, Randall Hopper wrote:
>
> > Mike Smith:
> > |> Also, I wonder if you've seen/heard of an MTRR patch for 3.2-RELEASE
> > |
> > |You could try to backport the two sets of commits I just made to the
> > |-stable branch, but you might be better off moving to -stable or to
> > |3.3-RELEASE.
> >
> > Ok, I might try that. From Brian's message, it sounds like he's made some
> > commits for MTRR. Would I need those as well (or are your commits the work
> > he spoke of).
>
> It may be worth specifying that k6_mem.c should be disabled in RELENG_3 pending
> further investigation of problems with the MTRR interfeace (i.e. that it can
> corrupt other memory...) For now, it's unsafe.
Maybe I'm missing the point here, but as a AMD user I'm interested anyway:
'should be disabled', does that mean one has to 'hand hack' to disable it?
Stable being -stable I'd have guessed it should be disabled by default
if it is not 100% working like it should.
TIA
--
| / o / / _ Arnhem, The Netherlands - Powered by FreeBSD -
|/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
