I'm just wondering if rather than specify all the CACHED and MAPPABLE and SHAREABLE flags we make the BO interface in terms of CPU and GPU operations..
So we define CPU_READ - cpu needs to read from this buffer CPU_WRITE - cpu need to write to the buffer CPU_POOL - cpu wants to use the buffer for suballocs GPU_READ - gpu reads GPU_WRITE - gpu writes (GPU_EXEC??) - batchbuffers? (maybe buffers that need relocs.. not sure) We can then let the drivers internally decide what types of buffer to use and not expose the flags mess to userspace. Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie Linux kernel - DRI, VAX / pam_smb / ILUG ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
