Will be a bit more complex than xterm/curses. One of the problem
is that using the VESA1 interface is needed (DMA restrictions), so
you need to get back the array given by the Gujin bootloader, describing
which I/O port to use to switch the 32/64K window at 0xA0000. You do not
want to go back to real-mode at every VESA1 page change.
(This array is already available with the current Gujin, using it is
Gujin native mode for VESA1 cards)
> [Of course, user *will* see you are only updating at 5fps... But it will
> be way beter than current slowness.]
And the only usual "fast changing" thing is the mouse, so either use a
hardware extension of the video card or direct PCI write for it only.
My main question was which bandwidth the standard DMA is able to do
for memory to memory copy, if it is too slow, do not even start
to code anything... got no answer. The PC DMA can only copy memory by
16 bit units - and I am not sure it will behave correctly with
PCI stalls.
> Are you going to create a patch?
Lets say, I start just after I finish Gujin; i.e. if you want to see
something before Linux 3.1, find someone else... I can still help a bit.
Etienne.
___________________________________________________________
Un nouveau Nokia Game commence.
Allez sur http://fr.yahoo.com/nokiagame avant le 3 novembre
pour participer ā cette aventure tous médias.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/