On Sun, 2005-10-23 at 11:03 +0100, Dave Airlie wrote:
> >
> > So, something like Get/Set/UnsetAttribute() perhaps.
> >
> > But also, thinking about the use of these regions for DMA, synchronization
> > is
> > important. I saw the SetFence() entrypoint, there's no way to retire these
> > fences, e
>
> I guess I don't see a problem with putting it in libdrm. I had just
> assumed that the user-mode portion would end up living in
> src/mesa/driver/dri/common or some place similar. There are some
> advantages to putting it in libdrm, though (e.g., easier for EXA to use it).
Well the X server
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dave Airlie wrote:
> I've been thinking a bit about this, and while I think Ian's work on the
> memory manager has merit I'm starting to think we are really putting the
> cart before the horse in some ways
>
> My thinking on this is that the memor
>
> So, something like Get/Set/UnsetAttribute() perhaps.
>
> But also, thinking about the use of these regions for DMA, synchronization is
> important. I saw the SetFence() entrypoint, there's no way to retire these
> fences, eg a FinishFence().
>
> You've probably seen this one:
>
> http://oss.s
Dave Airlie wrote:
I've been thinking a bit about this, and while I think Ian's work on the
memory manager has merit I'm starting to think we are really putting the
cart before the horse in some ways
My thinking on this is that the memory manager needs to live in libdrm,
not like the current
