From: David E. <ege...@th...> - 2004-03-29 15:36:41
|
Now that my local kernel actually calls copyarea(), I see that my code was buggy... That is, the hardware needs to be told which way to do its memory copies if areas overlap. Think of memmove() versus memcpy(). Attached is the fix. Unfortunately, I think the fbcon layer is also buggy... (try opening a file with vim, and typing "5ddP" the copyarea()'s that get sent to the fb driver seem totally bogus...) -dte |