Jeroen Janssen wrote:
> I was wondering about the (non-cpu) hardware emulation/virtualisation,
> etc.
> This includes:
> * display card
> * disk drive
> * network card
> * sound card
> * etc
>
> Are there any plans on rewriting certain things so it can be more easily
> extended?
>
> We still need some kind of generic guest <-> host communication system
> for guest os specific (hardware) drivers.
Sure, we need special guest OS specific drivers and such a guest<->host
interface. We talked about this a little before. This is a great area
for people to help out in, since its very modular. How about as soon
as plex86 can run Linux, I'll add an interface for plugins to register
these services with plex86 and transfer data? Then developers can
work in parallel on these components. I've been holding out for
having at least one real OS running.
> Also, I haven't had the time yet to work on it, but I was thinking about
> a "growable" harddisk (so if you create a new harddisk image with size 2
> Gig, you'll end with an initial harddisk file of a couple of Kb's that
> "grows" as soon as something is written to a sector.)
Can't Linux handle having "holes" in a file already?
> Maybe, we can make a "TODO" list with stuff that "only" you/people who
> have "deep" knowledge of the virtualisation process can work on and
> things "others" also can work on (I've got the feeling that there a few
> people doing "all" the work, because "others" (like me) sometimes think
> they need to know a lot about the virtualisation process. If we could
> make a list of things that don't require "deep" knowledge of
> virtualisation then it might be easier for people like me to start
> working on parts of plex86). .. hope this makes sence?
OK, this can be done. There really are a lot of areas to help
out in. I will begin and maintain a TODO list soon. I think the
"critical mass" point is plex86 running Linux, which I believe should
be soon.
-Kevin
