Re: [Mesa3d-dev] perrtblend merge

2010-01-27 Thread Keith Whitwell
Roland, This is looking good too - feel free to merge when ready. Ketih On Tue, 2010-01-26 at 08:03 -0800, Roland Scheidegger wrote: > Oh, I should have added the PIPE_CAP bits (even if not supported) to all > drivers. Good catch. I'll do that for the other drivers now. > > Roland > > (btw, I

Re: [Mesa3d-dev] perrtblend merge

2010-01-26 Thread Christoph Bumiller
On 26.01.2010 18:16, Keith Whitwell wrote: > On Tue, 2010-01-26 at 09:05 -0800, Christoph Bumiller wrote: > >> On 26.01.2010 17:03, Roland Scheidegger wrote: >> >>> Oh, I should have added the PIPE_CAP bits (even if not supported) to all >>> drivers. Good catch. I'll do that for the other d

Re: [Mesa3d-dev] perrtblend merge

2010-01-26 Thread Keith Whitwell
On Tue, 2010-01-26 at 09:05 -0800, Christoph Bumiller wrote: > On 26.01.2010 17:03, Roland Scheidegger wrote: > > Oh, I should have added the PIPE_CAP bits (even if not supported) to all > > drivers. Good catch. I'll do that for the other drivers now. > > > > > Ohhh sorry, I wanted to push the n

Re: [Mesa3d-dev] perrtblend merge

2010-01-26 Thread Jakob Bornecrantz
On 26 jan 2010, at 17.05, Christoph Bumiller wrote: > On 26.01.2010 17:03, Roland Scheidegger wrote: >> Oh, I should have added the PIPE_CAP bits (even if not supported) >> to all >> drivers. Good catch. I'll do that for the other drivers now. >> >> > Ohhh sorry, I wanted to push the nv50 support

Re: [Mesa3d-dev] perrtblend merge

2010-01-26 Thread Christoph Bumiller
On 26.01.2010 17:03, Roland Scheidegger wrote: > Oh, I should have added the PIPE_CAP bits (even if not supported) to all > drivers. Good catch. I'll do that for the other drivers now. > > Ohhh sorry, I wanted to push the nv50 support for separate blend to the perrtblend branch and accidentally

Re: [Mesa3d-dev] perrtblend merge

2010-01-26 Thread Alex Deucher
On Tue, Jan 26, 2010 at 11:03 AM, Roland Scheidegger wrote: > Oh, I should have added the PIPE_CAP bits (even if not supported) to all > drivers. Good catch. I'll do that for the other drivers now. > > Roland > > (btw, I think r500 could do separate colormasks, but not separate blend > enables, an

Re: [Mesa3d-dev] perrtblend merge

2010-01-26 Thread Roland Scheidegger
Oh, I should have added the PIPE_CAP bits (even if not supported) to all drivers. Good catch. I'll do that for the other drivers now. Roland (btw, I think r500 could do separate colormasks, but not separate blend enables, and there might be more hardware like that. However, this is not exposed by

Re: [Mesa3d-dev] perrtblend merge

2010-01-26 Thread Corbin Simpson
Yeah, r300 doesn't but r600 does. I've read through the branch, and the r300g patch looks perfect. I've pushed another patch on top for the pipe caps, to avoid post-merge cleanups for myself. On Tue, Jan 26, 2010 at 7:00 AM, Alex Deucher wrote: > On Tue, Jan 26, 2010 at 9:44 AM, Roland Scheidegge

Re: [Mesa3d-dev] perrtblend merge

2010-01-26 Thread Alex Deucher
On Tue, Jan 26, 2010 at 9:44 AM, Roland Scheidegger wrote: > Hi, > > I'm planning on merging this branch to master soon. > This will make it possible to do per render target blend enables, > colormasks, and also per rendertarget blend funcs (with a different CAP > bit for the latter, and this one

[Mesa3d-dev] perrtblend merge

2010-01-26 Thread Roland Scheidegger
Hi, I'm planning on merging this branch to master soon. This will make it possible to do per render target blend enables, colormasks, and also per rendertarget blend funcs (with a different CAP bit for the latter, and this one isn't actually used in mesa state tracker yet). None of the drivers oth