On Wednesday 16 March 2005 07:53, Marcel Moreaux wrote: > On Tue, Mar 15, 2005 at 11:28:59PM -0500, Daniel Phillips wrote: > > Hmm, and force the command ringbuffer to be physically contiguous? > > In that case, I'd say don't bother with the 8 entry lists, just let > > the ringbuffer be a huge thing that can only initialize at boot. > > Because after a Linux kernel has been running for a while, you > > can't be sure of successfully getting even 2 physically contiguous > > pages, let alone a whole bunch. > > Would this prohibit compiling the ogl DRM as a Linux kernel module? > Modules aren't necessarily loaded at boot (and, technically, if they > are, they are loaded after userspace activity, so memory may be > fragmented already).
Exactly. I think the correct solution is to supply a list of physical pages for the command ring buffer, and let it be physically discontiguous. And implement that in an update, because after all, it's not so bad to require the video to be initialized early. Regards, Daniel _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
