>> > That would be great. Whenever you want, we can begin by
>> > making some simple IO interface that will allow you to
>> > efficiently move data to/from the VM/driver.
>
>
>OK, what device would be a good choice for a first driver -
>maybe a hard drive? I'd imagine this would be the simplest
>one to do, since it can use simple read()/write() on the
>host side.
Try the keyboard. Easier. And you could make a simple serial driver (not
a real UART compatible, just to test) --- so when you do outb(0xff, 'a')
then
its prints 'a' on the screen, stuff like that. Then you can write some simple
demo programs that show off the system :)
I should really be coding again, but finding the time isn't easy... :(
[snip]
>Upon receiving this info, the framework can deliver this info
>to a callback to handle the special device. This way the
>framework can route information without knowing anything
>about the structure of the data, and only a few IO port
>instructions are needed for the data transfer.
Good system. I'd like to expand this to other events (physical memory,
interrupts).
Ramon
