Patrick McNamara wrote: >>>> As it currently sits, the framebuffer driver is decent enough with the >>>> exception of full screen scrolling. That is very painful. >>> >>> A dirty fix for this would be to avoid PCI reads entirely. >> >> I would look at implementing a blit or shift primitive on the board >> instead. > > I guess, in a way, this is what HQ does for VGA text. The blit of the > font glyph is handled on card. We should be able to load an HQ program > as part of the fb driver to do "acceleration" of fill and copy_area, at > least. The copy_area call would still be best handled entirely in the > S3 as using HQ to do it would involve moving a lot of data over the > XP10<->S3 bridge.
I agree the ops should be done in S3. Rather than copying data around it could be interesting to have an offset for start-of-screen within the framebuffer. Depending on what entities in S3 access the memory it might not need a lot of extra gates, and it would make scrolling close to a no-op. //Peter _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
