Am Mittwoch, den 03.08.2011, 22:55 -0700 schrieb Eric Anholt:
> On Wed, 27 Jul 2011 20:52:00 -0600, Brian Paul wrote:
> > On Wed, Jul 27, 2011 at 7:29 PM, Eric Anholt wrote:
> > > On Sat, 23 Jul 2011 11:58:22 -0600, Brian Paul
> > > wrote:
> > >> On Sat, Jul 23, 2011 at 9:14 AM, Eric Anholt wr
On Wed, 27 Jul 2011 20:52:00 -0600, Brian Paul wrote:
> On Wed, Jul 27, 2011 at 7:29 PM, Eric Anholt wrote:
> > On Sat, 23 Jul 2011 11:58:22 -0600, Brian Paul
> > wrote:
> >> On Sat, Jul 23, 2011 at 9:14 AM, Eric Anholt wrote:
> >> > On Fri, 22 Jul 2011 14:06:48 -0600, Brian Paul wrote:
> >>
On Wed, Jul 27, 2011 at 7:29 PM, Eric Anholt wrote:
> On Sat, 23 Jul 2011 11:58:22 -0600, Brian Paul wrote:
>> On Sat, Jul 23, 2011 at 9:14 AM, Eric Anholt wrote:
>> > On Fri, 22 Jul 2011 14:06:48 -0600, Brian Paul wrote:
>> >> On 07/22/2011 01:32 PM, Eric Anholt wrote:
>> >> > On Thu, 23 Jun 2
On Sat, 23 Jul 2011 11:58:22 -0600, Brian Paul wrote:
> On Sat, Jul 23, 2011 at 9:14 AM, Eric Anholt wrote:
> > On Fri, 22 Jul 2011 14:06:48 -0600, Brian Paul wrote:
> >> On 07/22/2011 01:32 PM, Eric Anholt wrote:
> >> > On Thu, 23 Jun 2011 19:08:51 -0600, Brian Paul wrote:
> >> >>
> >> >> I'd
On Sat, Jul 23, 2011 at 9:14 AM, Eric Anholt wrote:
> On Fri, 22 Jul 2011 14:06:48 -0600, Brian Paul wrote:
>> On 07/22/2011 01:32 PM, Eric Anholt wrote:
>> > On Thu, 23 Jun 2011 19:08:51 -0600, Brian Paul wrote:
>> >>
>> >> I'd like to overhaul the part of Mesa related to texture memory
>> >> r
On Fri, 22 Jul 2011 14:06:48 -0600, Brian Paul wrote:
> On 07/22/2011 01:32 PM, Eric Anholt wrote:
> > On Thu, 23 Jun 2011 19:08:51 -0600, Brian Paul 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
On 07/22/2011 01:32 PM, Eric Anholt wrote:
On Thu, 23 Jun 2011 19:08:51 -0600, Brian Paul 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 i
On Thu, 23 Jun 2011 19:08:51 -0600, Brian Paul 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
squash-merged.
On 07/18/2011 01:00 PM, Pekka Paalanen wrote:
On Mon, 18 Jul 2011 08:09:17 -0600
Brian Paul wrote:
On 07/15/2011 02:59 PM, Pekka Paalanen wrote:
On Fri, 15 Jul 2011 12:22:41 -0600
Brian Paul wrote:
On 07/15/2011 10:07 AM, Dave Airlie wrote:
On Fri, Jul 15, 2011 at 4:10 AM, Brian
Paul
On Mon, 18 Jul 2011 08:09:17 -0600
Brian Paul wrote:
> On 07/15/2011 02:59 PM, Pekka Paalanen wrote:
> > On Fri, 15 Jul 2011 12:22:41 -0600
> > Brian Paul wrote:
> >
> >> On 07/15/2011 10:07 AM, Dave Airlie wrote:
> >>> On Fri, Jul 15, 2011 at 4:10 AM, Brian
> >>> Paul wrote:
>
>
> >
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 wrote:
> On 07/15/2011 02:59 PM, Pekka Paalanen wrote:
>>
>> On Fri, 15 Jul 2011 12:22:41 -0600
>>
On 07/15/2011 02:59 PM, Pekka Paalanen wrote:
On Fri, 15 Jul 2011 12:22:41 -0600
Brian Paul wrote:
On 07/15/2011 10:07 AM, Dave Airlie wrote:
On Fri, Jul 15, 2011 at 4:10 AM, Brian
Paul wrote:
The map-texture-image-v4 branch that I just pushed implements
this change. It really cleaned t
On Fri, 15 Jul 2011 12:22:41 -0600
Brian Paul wrote:
> On 07/15/2011 10:07 AM, Dave Airlie wrote:
> > On Fri, Jul 15, 2011 at 4:10 AM, Brian
> > Paul wrote:
> >>
> >>
> >> The map-texture-image-v4 branch that I just pushed implements
> >> this change. It really cleaned things up for the better
On Fri, Jul 15, 2011 at 2:22 PM, Brian Paul wrote:
> On 07/15/2011 10:07 AM, Dave Airlie wrote:
>>
>> On Fri, Jul 15, 2011 at 4:10 AM, Brian Paul
>> wrote:
>>>
>>> On Thu, Jun 23, 2011 at 7:08 PM, Brian Paul wrote:
I'd like to overhaul the part of Mesa related to texture memory
re
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 Paul
>> wrote:
>>> On Thu, Jun 23, 2011 at 7:08 PM, Brian Paul wrote:
I'd like to overhaul the part of Mesa related to texture memory
reading/writing.
>>
- Original Message -
> On 07/15/2011 10:07 AM, Dave Airlie wrote:
> > On Fri, Jul 15, 2011 at 4:10 AM, Brian Paul
> > wrote:
> >> On Thu, Jun 23, 2011 at 7:08 PM, Brian Paul
> >> wrote:
> >>>
> >>> I'd like to overhaul the part of Mesa related to texture memory
> >>> reading/writing.
>
On 07/15/2011 10:07 AM, Dave Airlie wrote:
On Fri, Jul 15, 2011 at 4:10 AM, Brian Paul wrote:
On Thu, Jun 23, 2011 at 7:08 PM, Brian Paul 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 Fri, Jul 15, 2011 at 4:10 AM, Brian Paul wrote:
> On Thu, Jun 23, 2011 at 7:08 PM, Brian Paul 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 text
On Thu, Jun 23, 2011 at 7:08 PM, Brian Paul 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 region of
On 06/24/2011 11:27 AM, Eric Anholt wrote:
On Thu, 23 Jun 2011 19:08:51 -0600, Brian Paul 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 spac
On Thu, 23 Jun 2011 19:08:51 -0600, Brian Paul 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 r
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 region of interest (ROI). Reading/writing
* texels outside of the ROI is
22 matches
Mail list logo