??? When did you get to see output corruption? Can you send me your
rewrite for testing? (Though Aranym should suffice for testing, really)
I was testing with vga256 and pretty much any line edit operation which
calls copyarea or fillrect causes a corrupt output (i.e. anything besides
special cases like full lines). Am I the only one seeing that?
No, I was also seeing that - forgot about it because I only did full line
scrolls on the recent tests.
I attached the 8 plane version, it still needs some more cleanups. The 2
and 4 plane version will look similiar and I propably going to merge them
at some point to use one template to produce the 3 versions.
Looks good - the fillrect and copyarea coide should have taken care of
odd/even problems, I probably just got some offsets wrong there. For
my simple test purposes, I rarely hit that code (otherwise the printk()
would have been gone).
Go ahead with the rewrite - it can still be optimized if needs be.
I killed the movep stuff, I'm not sure it still is really a win (maybe at
68000 times it was, but on a 68060 it certainly isn't), some operations
should be even considerably faster now (e.g. odd<->even copy).
The kernel started out on 030, and Andreas wouldn't have written it if it
didn't speed things up there. For emulation and 060 we can probably drop
it. My only rationale for using it was to start from something that had
worked at some time in the past :-)
I don't see a big difference in speed in ARAnyM; need to test on the real
hardware for that.
Michael
-
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
