e to the reasons you outline very nicely.
Also note, that for the X target, the directbuffer _is_ in main memory, so
that you could as well use it. (However as you can't probe, if you are in X,
...)
: - if you do 32bit or 16bit access, some hardware cannot do this.
Note, that this also ap
> i am especially interested in if
> ggiPutBox from memory(malloc) to visual
> is equally fast then
> ggiCrossBlit from memory-target to visual
> (memory(malloc) and memory-target and visual are all
> the same format. 640x480x8 linear)
This shouldn't make much difference, as long as format is the
On Tue, Feb 01, 2000 at 10:40:10AM +0100, Erik Thiele wrote:
> i'd like to contribute a little bit of GGI documentation.
>
> please view
>
> http://www.erikyyy.de/noshine/ggi/
>
> and please correct me if i am wrong!
>
i am especially interested in if
ggiPu
On Mon, Jan 31, 2000 at 11:43:52PM +0100, Andreas Beck wrote:
> > if directbuffer fill it with memcpy but memcpy does 32 bit stuff.
> > (rep movsl) but directbuffer maybe 16bit limited on old vga hardware
> > how to deal with this.
>
> First of all, check the "align" and "noaccess" members.
> I
> if directbuffer fill it with memcpy but memcpy does 32 bit stuff.
> (rep movsl) but directbuffer maybe 16bit limited on old vga hardware
> how to deal with this.
First of all, check the "align" and "noaccess" members.
If no restrictions are set, go ahead, use memcpy.
> do not have memcpy 16b
hi
if directbuffer
fill it with memcpy
but memcpy does 32 bit stuff. (rep movsl)
but directbuffer maybe 16bit limited on old vga hardware
how to deal with this.
do not have memcpy 16bit.
for(...)...
is very bad code if you look at the asm.
how deal with this issue ?
cu
erik
--
Name: Eri
