> > 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). > > ok, I'll have a go at this tonight when I'm home. > > To see if I understand things a bit I collected the information/semi > code that I'll probably end up using ok, I wrote a small plugin to see if I understand things a little bit and it seems to work :) I "only" have a bit of a problem with the guest/virtcode/ example program that I would like to modify with some testcode. I would like to modify it with some port I/O. however I'm not familiar with the GCC ASM syntax and I *think* I can not use any standard library functions. Can somebody provide me with a function that outputs a DWORD to a port? --- Jeroen Janssen
- Re: video driver protocol Jeroen Janssen
- Re: video driver protocol Elmar Haneke
- Re: video driver protocol Jeroen Janssen
- Re: video driver protocol Andrew Stewart
- Re: video driver protocol Elmar Haneke
- Re: video driver protocol Wouter Coene
- Re: video driver protocol Ramon van Handel
- Re: video driver protocol Jeroen Janssen
- Re: video driver protocol Ramon van Handel
- Re: video driver protocol Jeroen Janssen
- Re: video driver protocol Jeroen Janssen
- Re: video driver protocol Ramon van Handel
- Re: video driver protocol Ramon van Handel
- Re: video driver protocol Jeroen Janssen
- Re: video driver protocol Ramon van Handel
- Re: video driver protocol Jeroen Janssen
- Re: video driver protocol Ramon van Handel
- Re: video driver protocol Jeroen Janssen
- Re: video driver protocol Eric Laberge
- Re: video driver protocol Ramon van Handel
- Re: video driver protocol Jeroen Janssen
