On Sad, 2004-09-11 at 00:10, Jon Smirl wrote: > I'm counting on Ian to provide the memory management code. I haven't > even looked at it very much. The point is simply that we have to have > something, you just can't support multiple heads without minimal > memory management and fbdev doesn't currently have any memory > management. Since the plan is for a mode setting command to take a > path unto user space via hotplug it may be possible for all memory > management code to exist in user space. The basic point is that the > memory management code must be unified.
DRI's memory allocator needs are very different to the others. That probably means the kernel API should be very simple and push most of the allocation to user space for rendering work. You want "give me 4Mb" in kernel , but you don't want allocation for textures in kernel (just profile the via driver). fbdev does btw have memory management, quite a bit of it for some multihead cards. ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
