Changing radeon KMS cs+gem ioctl to merge read & write domain

2009-10-21 Thread Jerome Glisse
Hi, I think we should merge the read & write domain of radeon KMS into a single domains information. I don't think there is a good reason for separate read & write domain, we did copy intel model for that and intel use this mostly for cache coherency & cache flushing as far as i understand. We mak

Re: Changing radeon KMS cs+gem ioctl to merge read & write domain

2009-10-21 Thread Corbin Simpson
On 10/21/2009 03:49 PM, Jerome Glisse wrote: > Hi, > > I think we should merge the read & write domain of radeon KMS > into a single domains information. I don't think there is a > good reason for separate read & write domain, we did copy intel > model for that and intel use this mostly for cache

Re: Changing radeon KMS cs+gem ioctl to merge read & write domain

2009-10-22 Thread Jerome Glisse
On Wed, 2009-10-21 at 18:49 -0700, Corbin Simpson wrote: > On 10/21/2009 03:49 PM, Jerome Glisse wrote: > > Hi, > > > > I think we should merge the read & write domain of radeon KMS > > into a single domains information. I don't think there is a > > good reason for separate read & write domain, we

Re: Changing radeon KMS cs+gem ioctl to merge read & write domain

2009-10-25 Thread Dave Airlie
On Thu, Oct 22, 2009 at 8:49 AM, Jerome Glisse wrote: > Hi, > > I think we should merge the read & write domain of radeon KMS > into a single domains information. I don't think there is a > good reason for separate read & write domain, we did copy intel > model for that and intel use this mostly f

Re: Changing radeon KMS cs+gem ioctl to merge read & write domain

2009-10-26 Thread Jerome Glisse
On Mon, 2009-10-26 at 12:12 +1000, Dave Airlie wrote: > On Thu, Oct 22, 2009 at 8:49 AM, Jerome Glisse wrote: > > Hi, > > > > I think we should merge the read & write domain of radeon KMS > > into a single domains information. I don't think there is a > > good reason for separate read & write doma