On Tue, 2005-01-18 at 00:38 -0500, Vladimir Dergachev wrote: > > Again on the bus itself, it's at 0 (overlapping RAM for AGP cycles only > > though) which is what you put in AGP_BASE_ADDR, but the engine "sees" it > > at MC_FB_LOCATION which is usually set right above the framebuffer. > > This is not right. MC_FB_LOCATION is where the engine thinks its > *framebuffer* is at. Which is correct as DRI driver puts both textures > and vertex buffer in the framebuffer.
Yup, the above is a typo, I was thinking MC_AGP_LOCATION and wrote MC_FB_LOCATION ... so much for writing emails before breakfast :) > r300_demo is simpler - it puts a texture into AGP space and instructs the > card to access it from there. > > The register the card thinks AGP space is at is MC_AGP_LOCATION and, > AFAIK, it should not overlap MC_FB_LOCATION or things will get really > screwed up. Yup. ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
