Ramon van Handel wrote:
>
> Whoops those are only byte/word port ops.
> Something like this should work (untested):
>
> static inline long inportl(short port)
> {
> long ret;
> asm volatile ("inl (%%dx),%%eax":"=a" (ret):"d" (port));
> return ret;
> }
>
> static inline void outportl(short port, long value)
> {
> asm volatile ("outl %%eax,(%%dx)"::"d" (port), "a" (value));
> }
yep, it works... I've got a vidtest plugin & an extra function in the
virtcode guest for testing purposes and I can now from the guest:
open a ptc console in a specific x,y resolution (ARGB8888 format)
close the console
do a complete update of the console with pixels from the guest
(ptc==OpenPTC @ www.gaffer.org/ptc)
only "problem" I currently have is that after opening the ptc console
it's window is also made active, is there a way to make the plex86 gui
active after I have opened the ptc console?
---
Jeroen
- 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
- RE: video driver protocol Drew Northup
- Re: video driver protocol Wouter Coene
- Re: video driver protocol Jeroen Janssen
