[Nouveau] RFC: gallium/nv50: get rid of the screen_init stateobj

Hi. There's not much to say here, just replacing the screen_init stateobj with direct pushbuffer emission. We don't need to store all the usless state from init, and the constant buffer relocations which currently don't work if the addresses change (because the method CB_DEF_SET isn't among them

Re: [Nouveau] RFC: gallium/nv50: get rid of the screen_init stateobj

On Sun, Mar 14, 2010 at 11:32 AM, Christoph Bumiller e0425...@student.tuwien.ac.at wrote: Hi. There's not much to say here, just replacing the screen_init stateobj with direct pushbuffer emission. We don't need to store all the usless state from init, and the constant buffer relocations

Re: [Nouveau] RFC: gallium/nv50: get rid of the screen_init stateobj

On 14.03.2010 13:03, Maarten Maathuis wrote: On Sun, Mar 14, 2010 at 11:32 AM, Christoph Bumiller e0425...@student.tuwien.ac.at wrote: Hi. There's not much to say here, just replacing the screen_init stateobj with direct pushbuffer emission. We don't need to store all the usless state

Re: [Nouveau] RFC: gallium/nv50: get rid of the screen_init stateobj

BEGIN_RING also does autobind, the rest seems ok. Maarten. On Sun, Mar 14, 2010 at 2:53 PM, Christoph Bumiller e0425...@student.tuwien.ac.at wrote: On 14.03.2010 13:03, Maarten Maathuis wrote: On Sun, Mar 14, 2010 at 11:32 AM, Christoph Bumiller e0425...@student.tuwien.ac.at wrote: Hi.