Am Mittwoch, den 03.08.2011, 22:55 -0700 schrieb Eric Anholt:
On Wed, 27 Jul 2011 20:52:00 -0600, Brian Paul brian.e.p...@gmail.com wrote:
On Wed, Jul 27, 2011 at 7:29 PM, Eric Anholt e...@anholt.net wrote:
On Sat, 23 Jul 2011 11:58:22 -0600, Brian Paul brian.e.p...@gmail.com
wrote:
On Wed, 27 Jul 2011 20:52:00 -0600, Brian Paul brian.e.p...@gmail.com wrote:
On Wed, Jul 27, 2011 at 7:29 PM, Eric Anholt e...@anholt.net wrote:
On Sat, 23 Jul 2011 11:58:22 -0600, Brian Paul brian.e.p...@gmail.com
wrote:
On Sat, Jul 23, 2011 at 9:14 AM, Eric Anholt e...@anholt.net wrote:
On Sat, 23 Jul 2011 11:58:22 -0600, Brian Paul brian.e.p...@gmail.com wrote:
On Sat, Jul 23, 2011 at 9:14 AM, Eric Anholt e...@anholt.net wrote:
On Fri, 22 Jul 2011 14:06:48 -0600, Brian Paul bri...@vmware.com wrote:
On 07/22/2011 01:32 PM, Eric Anholt wrote:
On Thu, 23 Jun 2011 19:08:51
On Wed, Jul 27, 2011 at 7:29 PM, Eric Anholt e...@anholt.net wrote:
On Sat, 23 Jul 2011 11:58:22 -0600, Brian Paul brian.e.p...@gmail.com wrote:
On Sat, Jul 23, 2011 at 9:14 AM, Eric Anholt e...@anholt.net wrote:
On Fri, 22 Jul 2011 14:06:48 -0600, Brian Paul bri...@vmware.com wrote:
On
On Fri, 22 Jul 2011 14:06:48 -0600, Brian Paul bri...@vmware.com wrote:
On 07/22/2011 01:32 PM, Eric Anholt wrote:
On Thu, 23 Jun 2011 19:08:51 -0600, Brian Paulbri...@vmware.com wrote:
I'd like to overhaul the part of Mesa related to texture memory
reading/writing.
OK, I'm taking a
On Sat, Jul 23, 2011 at 9:14 AM, Eric Anholt e...@anholt.net wrote:
On Fri, 22 Jul 2011 14:06:48 -0600, Brian Paul bri...@vmware.com wrote:
On 07/22/2011 01:32 PM, Eric Anholt wrote:
On Thu, 23 Jun 2011 19:08:51 -0600, Brian Paulbri...@vmware.com wrote:
I'd like to overhaul the part of
On Thu, 23 Jun 2011 19:08:51 -0600, Brian Paul bri...@vmware.com wrote:
I'd like to overhaul the part of Mesa related to texture memory
reading/writing.
OK, I'm taking a look at map-texture-image-v4. I like what I'm seeing
overall, I just want to be sure that this isn't something that gets
On 07/22/2011 01:32 PM, Eric Anholt wrote:
On Thu, 23 Jun 2011 19:08:51 -0600, Brian Paulbri...@vmware.com wrote:
I'd like to overhaul the part of Mesa related to texture memory
reading/writing.
OK, I'm taking a look at map-texture-image-v4. I like what I'm seeing
overall, I just want to
On 07/15/2011 02:59 PM, Pekka Paalanen wrote:
On Fri, 15 Jul 2011 12:22:41 -0600
Brian Paulbri...@vmware.com wrote:
On 07/15/2011 10:07 AM, Dave Airlie wrote:
On Fri, Jul 15, 2011 at 4:10 AM, Brian
Paulbrian.e.p...@gmail.com wrote:
The map-texture-image-v4 branch that I just pushed
The classic nouveau driver supports nv04, nv1x, nv2x IIRC. I'm
definitely not the right person for the job, but I'll look at it if
nobody else can.
~ C.
On Mon, Jul 18, 2011 at 7:09 AM, Brian Paul bri...@vmware.com wrote:
On 07/15/2011 02:59 PM, Pekka Paalanen wrote:
On Fri, 15 Jul 2011
On 07/18/2011 01:00 PM, Pekka Paalanen wrote:
On Mon, 18 Jul 2011 08:09:17 -0600
Brian Paulbri...@vmware.com wrote:
On 07/15/2011 02:59 PM, Pekka Paalanen wrote:
On Fri, 15 Jul 2011 12:22:41 -0600
Brian Paulbri...@vmware.com wrote:
On 07/15/2011 10:07 AM, Dave Airlie wrote:
On Fri, Jul
On Fri, Jul 15, 2011 at 4:10 AM, Brian Paul brian.e.p...@gmail.com wrote:
On Thu, Jun 23, 2011 at 7:08 PM, Brian Paul bri...@vmware.com wrote:
I'd like to overhaul the part of Mesa related to texture memory
reading/writing.
The basic idea would be to add two new driver functions:
/**
*
On 07/15/2011 10:07 AM, Dave Airlie wrote:
On Fri, Jul 15, 2011 at 4:10 AM, Brian Paulbrian.e.p...@gmail.com wrote:
On Thu, Jun 23, 2011 at 7:08 PM, Brian Paulbri...@vmware.com wrote:
I'd like to overhaul the part of Mesa related to texture memory
reading/writing.
The basic idea would be
- Original Message -
On 07/15/2011 10:07 AM, Dave Airlie wrote:
On Fri, Jul 15, 2011 at 4:10 AM, Brian Paulbrian.e.p...@gmail.com
wrote:
On Thu, Jun 23, 2011 at 7:08 PM, Brian Paulbri...@vmware.com
wrote:
I'd like to overhaul the part of Mesa related to texture memory
On 07/15/2011 11:22 AM, Brian Paul wrote:
On 07/15/2011 10:07 AM, Dave Airlie wrote:
On Fri, Jul 15, 2011 at 4:10 AM, Brian Paulbrian.e.p...@gmail.com
wrote:
On Thu, Jun 23, 2011 at 7:08 PM, Brian Paulbri...@vmware.com wrote:
I'd like to overhaul the part of Mesa related to texture memory
On Fri, Jul 15, 2011 at 2:22 PM, Brian Paul bri...@vmware.com wrote:
On 07/15/2011 10:07 AM, Dave Airlie wrote:
On Fri, Jul 15, 2011 at 4:10 AM, Brian Paulbrian.e.p...@gmail.com
wrote:
On Thu, Jun 23, 2011 at 7:08 PM, Brian Paulbri...@vmware.com wrote:
I'd like to overhaul the part of
On Fri, 15 Jul 2011 12:22:41 -0600
Brian Paul bri...@vmware.com wrote:
On 07/15/2011 10:07 AM, Dave Airlie wrote:
On Fri, Jul 15, 2011 at 4:10 AM, Brian
Paulbrian.e.p...@gmail.com wrote:
The map-texture-image-v4 branch that I just pushed implements
this change. It really cleaned
On Thu, Jun 23, 2011 at 7:08 PM, Brian Paul bri...@vmware.com wrote:
I'd like to overhaul the part of Mesa related to texture memory
reading/writing.
The basic idea would be to add two new driver functions:
/**
* Map a 2D slice of a texture image into user space.
* (x,y,w,h) defines a
On Thu, 23 Jun 2011 19:08:51 -0600, Brian Paul bri...@vmware.com wrote:
I'd like to overhaul the part of Mesa related to texture memory
reading/writing.
The basic idea would be to add two new driver functions:
/**
* Map a 2D slice of a texture image into user space.
* (x,y,w,h)
On 06/24/2011 11:27 AM, Eric Anholt wrote:
On Thu, 23 Jun 2011 19:08:51 -0600, Brian Paulbri...@vmware.com wrote:
I'd like to overhaul the part of Mesa related to texture memory
reading/writing.
The basic idea would be to add two new driver functions:
/**
* Map a 2D slice of a texture
20 matches
Mail list logo
