Christoph Bumiller
2010-Mar-14 10:32 UTC
[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 (not an address)) become effective. Thoughts, ack / nack ? Thanks, Christoph -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: 0001-nv50-get-rid-of-the-screen_init-stateobj.patch URL: <http://lists.freedesktop.org/archives/nouveau/attachments/20100314/4d363cf1/attachment-0001.ksh>
Maarten Maathuis
2010-Mar-14 12:03 UTC
[Nouveau] RFC: gallium/nv50: get rid of the screen_init stateobj
On Sun, Mar 14, 2010 at 11:32 AM, Christoph Bumiller <e0425955 at 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 which currently don't work if the > addresses change (because the method CB_DEF_SET isn't > among them (not an address)) become effective. > > Thoughts, ack / nack ? > Thanks, > ?Christoph > > > _______________________________________________ > Nouveau mailing list > Nouveau at lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/nouveau > >Perhaps add a BEGIN_RING_RELOC to libdrm? To make it more obvious. Maarten.