Re: [Dri-devel] mach64_blit

2001-12-23 Thread Vladimir Dergachev
On Sat, 22 Dec 2001, Gareth Hughes wrote: > On Sat, Dec 22, 2001 at 06:45:54AM -0800, Peter Surda wrote: > > Hi! > > > > I took a look at the source of mach64-0-0-2-branch, noticed mach64_blit > > is defined, but not implemented yet. Any hints on how it's > > progressing? > > > > I also notic

Re: [Dri-devel] agp: what if memory is fragmented?

2001-12-23 Thread Gareth Hughes
On Fri, Dec 21, 2001 at 05:34:43PM -0800, Philip Brown wrote: > On Sat, Dec 22, 2001 at 02:30:14AM +0100, Alexander Stohr wrote: > > The GART is the paging unit of the AGP system. > > > > It deals nicely with fragmented chunks of page sized > > memory chunks. So you only need some sort of memory

RE: [Dri-devel] agp: what if memory is fragmented?

2001-12-23 Thread Sottek, Matthew J
>However, it does look like AGPIOC_ALLOCATE is broken. It only returns >the ->physical field of the resulting agp_memory structure. It doesn't >even look like this field is set for any chipsets other than the i810 >and i830. You don't need anything other than the "key". This isn't a general pu

Re: [Dri-devel] agp: what if memory is fragmented?

2001-12-23 Thread Philip Brown
On Sat, Dec 22, 2001 at 02:30:14AM +0100, Alexander Stohr wrote: > The GART is the paging unit of the AGP system. > > It deals nicely with fragmented chunks of page sized > memory chunks. So you only need some sort of memory > allocation and a way to determine eachs pages physical > adress to use

RE: [Dri-devel] agp: what if memory is fragmented?

2001-12-23 Thread Alexander Stohr
The GART is the paging unit of the AGP system. It deals nicely with fragmented chunks of page sized memory chunks. So you only need some sort of memory allocation and a way to determine eachs pages physical adress to use it for those GART purposes. You just need to ensure that your memory is per

Re: [Dri-devel] agp: what if memory is fragmented?

2001-12-23 Thread Philip Brown
On Sat, Dec 22, 2001 at 05:26:24PM +, Keith Whitwell wrote: > ... > Real contiguous memory is required for the agp *table* which is 4 bytes/page > of agp memory, or 64k for typical chipsets Occasionally a problem, I'm > told, but I've never seen it. My usage patterns are unusual, though.