I'll do it in a moment.
Marek
On Fri, Oct 25, 2013 at 11:25 PM, Ilia Mirkin wrote:
> Thanks, Marek. Could someone with commit access pick this up? Let me
> know if you'd like me to reformat/resend/create a git tree/whatever.
>
> -ilia
>
> On Sun, Oct 13, 2013 at 9:16 AM, Marek Olšák wrote:
>>
Thanks, Marek. Could someone with commit access pick this up? Let me
know if you'd like me to reformat/resend/create a git tree/whatever.
-ilia
On Sun, Oct 13, 2013 at 9:16 AM, Marek Olšák wrote:
> For the series:
>
> Reviewed-by: Marek Olšák
>
> Marek
>
> On Sun, Oct 13, 2013 at 3:43 AM, Ili
For the series:
Reviewed-by: Marek Olšák
Marek
On Sun, Oct 13, 2013 at 3:43 AM, Ilia Mirkin wrote:
> ping
>
> On Fri, Oct 4, 2013 at 4:32 AM, Ilia Mirkin wrote:
>> This CAP will determine whether ARB_framebuffer_object can be enabled.
>> The nv30 driver does not allow mixing swizzled and line
ping
On Fri, Oct 4, 2013 at 4:32 AM, Ilia Mirkin wrote:
> This CAP will determine whether ARB_framebuffer_object can be enabled.
> The nv30 driver does not allow mixing swizzled and linear zsbuf/cbuf
> textures.
>
> Signed-off-by: Ilia Mirkin
> ---
> src/gallium/docs/source/screen.rst
This CAP will determine whether ARB_framebuffer_object can be enabled.
The nv30 driver does not allow mixing swizzled and linear zsbuf/cbuf
textures.
Signed-off-by: Ilia Mirkin
---
src/gallium/docs/source/screen.rst | 3 +++
src/gallium/drivers/freedreno/freedreno_screen.c | 1 +
s
Ok I guess it makes sense to keep PIPE_CAP_MIXED_COLORBUFFER_FORMATS
then in addition to the new cap bits (as at least r300 should be able to
benefit from it).
Roland
Am 09.09.2013 15:01, schrieb Marek Olšák:
> On r300, colorbuffers can have different pitches, therefore each of
> them can be of a
On r300, colorbuffers can have different pitches, therefore each of
them can be of arbitrary size. Other than that, there is a separate
framebuffer width and height state, which applies to all colorbuffers
(it's usually set to the minimum of all widths and heights as in
OpenGL).
r300 doesn't suppo
Am 09.09.2013 13:55, schrieb Erik Faye-Lund:
> On Mon, Sep 9, 2013 at 1:31 PM, Roland Scheidegger wrote:
>> I'm not really convinced of this idea.
>> There's already PIPE_CAP_MIXED_COLORBUFFER_FORMATS which is sort of
>> similar - a "requirement" of ARB_fbo, but it isn't used to determine
>> suppo
On Mon, Sep 9, 2013 at 1:31 PM, Roland Scheidegger wrote:
> I'm not really convinced of this idea.
> There's already PIPE_CAP_MIXED_COLORBUFFER_FORMATS which is sort of
> similar - a "requirement" of ARB_fbo, but it isn't used to determine
> support of ARB_fbo or not (my guess is drivers want to a
I'm not really convinced of this idea.
There's already PIPE_CAP_MIXED_COLORBUFFER_FORMATS which is sort of
similar - a "requirement" of ARB_fbo, but it isn't used to determine
support of ARB_fbo or not (my guess is drivers want to advertize ARB_fbo
even if they can't do it, and ARB_fbo doesn't real
This CAP will determine whether ARB_framebuffer_object can be enabled.
The nv30 driver does not allow mixing swizzled and linear zsbuf/cbufs.
Signed-off-by: Ilia Mirkin
---
Christoph, this is what I understood you suggested I do. Hopefully I got it
right. I've split this up into two patches, one
11 matches
Mail list logo
