>> But that's no problem; after all, you can specify in plex86.conf how much
>> physical memory is allocated in total for the guest... what does it matter
>> where the memory comes from ?
>
>well, I imagine that if an "enduser" configures plex86 to have 16Mb
>physical memory, he expects 16 Mb to be "available" and doesn't want to
>be bothered with the fact that he "actually" will have 12 Mb available,
>because our video driver allocates 4Mb physical memory
This is a matter of good documentation. Don't worry about it :)
>well, I was hoping we could establish an official "plex86 host<->guest
>interface port". (every guest os specific device driver will need some
>ports, so why not have plex86 manage a generic port that plugins can
>register a callback for (IS it possible for multiple plugins to register
>a callback on the SAME ports?) ->
No, that isn't possible. That would be a bug, anyway (IO port conflicts are
not allowed!). It would also mean lousy performance. However, I guess we
could reserve a range of I/O ports for plex86 use, but for now it's not so
important which port you pick (make it a plugin command line option if you
wish).
-- Ramon
