>Ramon van Handel wrote:
>> Is BIOS code relocatable like that ? I'm not sure...
>
>well, (optional) bioses are contained in their own (real-mode) segments
>"starting" at offset 0. as long as you stay in the same segment there
>shouldn't be any relocation problems.
Ok.
>> The page dirty bit should give some indication, look into this.
>
>look into this? I don't know where to look :)
>
>what function specified in plex86.h, user/user.h or user/plugin.h can I
>use for getting/setting the page dirty bit?
Hmm... at the moment, I don't believe there's a function for that ;).
>As far as I know, SDL doesn't provide hw accelerated functions itself,
>it provides the possibility to use OpenGL in combination with SDL, so
>you would also need to provide OpenGL calls.
Well, then we have an OpenGL compatible virtualised card. :)
Anyway, SDL supports blitting and the like.
>btw.. what happens when the guest (display driver) crashes during gfx
>output? this could affect host stability, right? would it be "wise" to
>allow guest code to invoke SDL in this way?
Yes... just provide a "rescue" key to kill the VM :).
>> >looking at the display framebuffer again, do we have a "nice" way to
>> >provide "video memory" to the guest? (it would be nice if I could
>>
>> Not yet, I'm still looking into this (it's more complicated than I thought,
>> and I have very little spare time at the moment. Should improve in a few
>> weeks...).
>
>ok, is there any good "workaround" for the moment?
Just copy for now, you can change it later.
-- Ramon
