[Nouveau] [PATCH] nvfx: fix nv3x fallout from state validation changes
Lucas Stach
dev at lynxeye.de
Mon Jan 30 10:35:00 PST 2012
Am Donnerstag, den 26.01.2012, 20:59 +0100 schrieb Patrice Mandin:
> Le Tue, 24 Jan 2012 09:54:31 +0100
> Lucas Stach <dev at lynxeye.de> a écrit:
>
> > From c998f732d42da5e962fe5da294493132c3e8dc5f Mon Sep 17 00:00:00 2001
> > From: Lucas Stach <dev at lynxeye.de>
> > Date: Tue, 24 Jan 2012 09:46:32 +0100
> > Subject: [PATCH] nvfx: fix nv3x fallout from state validation changes
> >
> > Apparently nv3x needs some curde hacks to work properly. This
> > is clearly not the right fix, but it's the behaviour of the old
> > code and fixes regressions seen by users.
>
> Hello,
>
> Sorry Lucas, but I finally found a test case I have forgotten, that
> would maybe need reverting your patches.
>
> In mesa-demos/src/demos you'll find fbo_firecube test program that have
> the scene misrenderered (the scene part that is rendered and used as
> texture on the cube).
>
> As far as I remember now, render temp stuff was used to handle fbo
> combinations supported on nv40 but not on nv30, or something like that.
>
Thanks for the hint. Now that I finally own a nv35 myself, I can
reproduce the issue and I'm investigating. I'm not yet sure why it
misrenders, normally we should just hit an assert in case of invalid
formats.
I will try to debug this, but I can't promise to get results before next
week, because FOSDEM wants my attention.
Thanks,
Lucas
More information about the Nouveau
mailing list