[Libdlo] [Fwd: Re: libtubecable 0.1.4]

[Rene Schickbauer]

Hi!

> thanks for your changes. I'll merge them into the git repository ASAP.

Thanks ;-)

> As you've found out yourself, the noisy junk during scrolling is just
> what happens to be in the framebuffer at the moment. Better to overwrite
> it.

Tried and failed by re-arranging the order in which is send the paint commands.

> And the idea with the horizontal scrolling is also quite nice, I
> guess it won't work at the same time together with vertical though?

Not really, now.

But i have quite a lot of experience in writing a tile-based display (from
my BlinkenSisters game). Can you give me a quick pointer on a few things:
* You add operations to a queue and then you call dl_cmd_sync() and send() -
what do these do? Why are there two commands?
* the "cs" handle is the queue handle, right?
* What is the exact memory layout used in the demo and how exactly are the
colors defined (for my demo, i did trial&error)
* how to load various 32x32 Pixel Bitmaps into the memory. Is there a
function i can just point to a Pixel datastream and have it uploaded to a
specific memory location?
* I'm not sure how the in-device copy command works. It's handle, source
address, dest adress and length, right.

If i manage to understand these things, i'd like to write a little 2-way
tile-based scrolling demo.

LLAP & LG
Rene