I forgot to CC the mesa3d list. Perhaps I should just reply to the list
itself. Since we're all going to get these emails anyway, why bother sending
them to our personal email accounts?
Dee
-----Original Message-----
From: [email protected]
To: [email protected]
Sent: Mon, 6 Apr 2009 8:22 pm
Subject: Re: Gallium HW Drivers & DRI/DRM
Ok, I'm starting to get a slight understanding of wheat's going on. I won't
understand much more until I dive into the codebase a bit more. So, which
branch should I be working on porting? Perhaps gallium-mesa-7.4? Or is there
another one that's a better candidate or more of a mainline tree?
Dee
-----Original Message-----
From: Michel Dänzer <[email protected]>
To: Dee Sharpe <[email protected]>
Cc: [email protected]
Sent: Mon, 6 Apr 2009 8:20 am
Subject: Re: Gallium HW Drivers & DRI/DRM
On Mon, 2009-04-06 at 08:04 -0500, Dee Sharpe wrote:
> Our persistent memory objects are called 'areas', but they're located
> in main memory, is that an issue?
Shouldn't be.
> Also, does this mean that agp access should be initialized in winsys?
Probably.
> I'm assuming that the drivers have their own ways of handling VRAM.
No, resource management is one of the things abstracted from the drivers
themselves in the winsys modules.
--
Earthling Michel
Dänzer | http://www.vmware.com
Libre software enthusiast | Debian, X and DRI developer
The Average US Credit Score is 692. See Yours in Just 2 Easy Steps!
------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
Mesa3d-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
