Mail Archives: djgpp/1996/12/18/15:31:50
From: | jmcc AT m5 DOT vi DOT ri DOT cmu DOT edu (Jason Mcmullan)
|
Newsgroups: | comp.os.msdos.djgpp
|
Subject: | Trapping IOport accesses under DJGPP
|
Date: | 18 Dec 1996 15:34:03 GMT
|
Organization: | Carnegie-Mellon University, School of Computer Science
|
Lines: | 24
|
Message-ID: | <5992tb$1n3@cantaloupe.srv.cs.cmu.edu>
|
NNTP-Posting-Host: | m5.vi.ri.cmu.edu
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
Hi there! I was wondering if anyone knew the what the best way is
to trap ioport accesses from a running DJGPP program, ie:
1) Lock out all video I/O ports and memory addresses
2) call int86 for a video BIOS call
3) on each I/O access, catch the trap,
unlock the port, perform the access,
re-lock the port, and scribble down
(in memory) what happened
4) after the int86 call completes,
dump all the I/O accesses to a file
(I'm working on an automated system to create Linux GGI
video drivers from card BIOSes, and this seems like the
best way to do so)
--
Jason McMullan - Research Programmer, Robotics Institute, CMU
Me: http://www.ul.cs.cmu.edu/~jmcc
Linux GGI: http://synergy.caltech.edu/~ggi
- Raw text -