On Friday, March 30, 2012 5:33:07 pm David Wolfskill wrote:
On Fri, Mar 30, 2012 at 01:46:58PM -0400, John Baldwin wrote:
...
You can actually use that on 8 and 9 as well. I think it's a likely a bug
that it used VM_MEMATTR_UNCACHED in the first place and that it should have
been using
On Tue, Apr 03, 2012 at 08:55:34AM -0400, John Baldwin wrote:
...
You can actually use that on 8 and 9 as well. I think it's a likely a bug
that it used VM_MEMATTR_UNCACHED in the first place and that it should
have
been using VM_MEMATTR_UNCACHEABLE all along. (Which is why I've
I track stable/8, stable/9, and head on (different slices on) my laptop
on a daily basis. I share /usr/local among all of these: while I update
the installed ports on a daily basis, I'm unwilling to do that 3 times
daily. :-}
The x11/nvidia-driver port is one, however, that I've found helpful to
On Fri, 2012-03-30 at 06:18 -0700, David Wolfskill wrote:
I track stable/8, stable/9, and head on (different slices on) my laptop
on a daily basis. I share /usr/local among all of these: while I update
the installed ports on a daily basis, I'm unwilling to do that 3 times
daily. :-}
The
On Friday, March 30, 2012 9:18:33 am David Wolfskill wrote:
I track stable/8, stable/9, and head on (different slices on) my laptop
on a daily basis. I share /usr/local among all of these: while I update
the installed ports on a daily basis, I'm unwilling to do that 3 times
daily. :-}
The
On Fri, Mar 30, 2012 at 12:18:58PM -0400, John Baldwin wrote:
...
I've sent an e-mail to the NVIDIA driver author about how best to fix this.
You can just change the driver to use VM_MEMATTR_UNCACHEABLE instead of
VM_MEMATTR_UNCACHED for now.
Thanks; I'd need to make it conditional
On Friday, March 30, 2012 12:41:12 pm David Wolfskill wrote:
On Fri, Mar 30, 2012 at 12:18:58PM -0400, John Baldwin wrote:
...
I've sent an e-mail to the NVIDIA driver author about how best to fix
this.
You can just change the driver to use VM_MEMATTR_UNCACHEABLE instead of
On Fri, Mar 30, 2012 at 01:46:58PM -0400, John Baldwin wrote:
...
You can actually use that on 8 and 9 as well. I think it's a likely a bug
that it used VM_MEMATTR_UNCACHED in the first place and that it should have
been using VM_MEMATTR_UNCACHEABLE all along. (Which is why I've renamed
the
