> > a) should it work? (given I don't really care about backwards compat)
> > b) do I still need to use glxMesaAllocateMemory and friends?
>
> It'd probably work fine, it's still a bit of a hack though.  Maybe it's time
> to really do the work on a proper manager?  I'm at a point where I can put a
> bit of time into that.

Oh I know it'd be a hack, but it would be for a job I'm working on, its
definitely not something I'd like to give back...

I'm definitely thinking we need to take Ian's DriMemoryManagerDesign
document and start thinking throught the issues.. it needs to be expanded
to be able to manage all graphics memory, VRAM and AGP, including
framebuffers and all that stuff, every driver using should allocate via
it, no more X 2D memory manager and all that .. being able to resize
framebuffers etc by dropping all the clobberable blocks, and moving other
stuff around would be a good start...

Dave.

-- 
David Airlie, Software Engineer
http://www.skynet.ie/~airlied / airlied at skynet.ie
Linux kernel - DRI, VAX / pam_smb / ILUG



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO September
19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
--
_______________________________________________
Dri-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to