On 2011.02.22 09:33:22 -0800, Eric Anholt wrote: > While I originally hacked it up this way where libdrm intuits what kind > of buffer it is from the name of the buffer, it's a bad way to design an > interface. We should really have a command that marks (an area) of a > buffer object as being a particular AUB type, and Mesa would use that > command to mark its buffers as appropriate. Particularly since we're > moving to streaming more of our state buffers into larger buffer > objects.
ok, if our plan is to move into larger buffer, current method is just hairy. Like I didn't hack up surface state and some others, coz it's twisted to convert current batch ending space usage into real bo for matching the name for trace block types. > > We also can't commit code to Mesa that just writes into some arbitrary > file based on an environment variable -- keep in mind that our Mesa > driver is loaded from the X Server which is running as root. yeah, I wasn't aware of this, any comment for how to dump the file? -- Open Source Technology Center, Intel ltd. $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
signature.asc
Description: Digital signature
_______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
