] But first, ADVRAM is again something else which has to be added, and second,
] it is only useful for moving large blocks, like when loading from disk
] (directly into VRAM). It's nice, but when loading the speed doesn't really
] matter. In all other cases, using the VDP is much better, since it can
] execute commands independantly from the processor, which can do other stuff.
] And third, VDP commands can have various dimensions. To do that using direct
] VRAM access is difficult and requires complex routines. I doubt it will be
] alot faster. And don't forget, it requires processor power, while the
] VDP-commands don't.
I have to disagree completely on this matter. The VDP command set is very
limited. You can only draw or copy rectangular blocks or draw a straight line
using the VDP. For all other operations, for example drawing a circle, you
need to make a separate pset per pixel!. This is very slow. It is slow when
you use the pset operation of the VDP and it is slow when you do it by
writing the vram via the VDP. However, having direct access to the VRAM from
the CPU will make it very fast.
Now that you know of one possible application where you really gain from
having ADVRAM (even on [EMAIL PROTECTED]), I leave it entirely up to your
imagination, fantasy and creativity to come up with many other ideas and
applications.
Kind regards,
Alex Wulms
--
Visit The MSX Plaza (http://www.inter.nl.net/users/A.P.Wulms) for info
on XelaSoft, Merlasoft, Quadrivium, XSA Disk images, the MSX Hardware list,
SD-Snatcher on fMSX, documentation and lots more.
****
MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED]
and put "unsubscribe msx [EMAIL PROTECTED]" (without the quotes) in
the body (not the subject) of the message.
Problems? contact [EMAIL PROTECTED]
More information on MSX can be found in the following places:
The MSX faq: http://www.faq.msxnet.org/
The MSX newsgroup: comp.sys.msx
The MSX IRC channel: #MSX on Undernet
****
