1. I've downloaded you source code microwin-frye-nanosteve.1.tar.bz2,
and readed it, I found you make a lot of change from v0.89.
Can you describle the concept of your work simply? So I can
understand your code easily. Where should I start it?
2. You said "except stipples and dashlists are still broken",
I want to know do you still working on it? And do you have a
schedule to release it? Is the following address still available
in the future?
http://frye.com/~aaron/microwin-frye-nanosteve.1.tar.bz2

Aaron J. Grier wrote:
On Mon, Jan 21, 2008 at 10:44:43PM +0800, Lazy Fox wrote:
Many people said that the efficiency of the NanoX is not high enough.
They said the functions which draw lines and polygon can be optimized.
But I don't know how to improve it. Can somebody tell me how, and show
me some source code.

adding driver-level linedraw, clipping, and blit code has sped up my
25MHz target significantly.  there were also some speedups made for text
draw which were merged into the tree a few years back.

I've put a tarball of the our branch at
http://frye.com/~aaron/microwin-frye-nanosteve.1.tar.bz2 .

I have been working on merging with CVS and porting our local hacks
(including fast linedraw) to other framebuffer devices.  I'm almost
there except stipples and dashlists are still broken.


--
┏━━━━━━━━━━━━━━━━━━━━━━━━┓
┃菩提本无树,明镜亦非台。本来无一物,何处惹尘埃。┃
┗━━━━━━━━━━━━━━━━━━━━━━━━┛


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to