home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.windows.x.i386unix
- Path: sparky!uunet!think.com!enterpoop.mit.edu!bloom-picayune.mit.edu!athena.mit.edu!dmatic
- From: dmatic@athena.mit.edu (Davor Matic)
- Subject: Re: X386 on Hercules and X386 bugs and suggestions
- Message-ID: <1992Dec22.145458.5285@athena.mit.edu>
- Sender: news@athena.mit.edu (News system)
- Nntp-Posting-Host: alfredo.mit.edu
- Organization: Massachusetts Institute of Technology
- References: <1992Dec21.132332.11450@cbnewsj.cb.att.com> <1992Dec21.175647.9279@athena.mit.edu> <JTSILLA.92Dec21143009@damon.ccs.northeastern.edu>
- Date: Tue, 22 Dec 1992 14:54:58 GMT
- Lines: 24
-
-
- I have started "MACROIZING" the mfb code, and am almost done. It isn't
- all that much work. One needs to change about 15 files all together.
- The way I did it, I introduced three macros:
-
- *MAPW(pdsp) = *MAPR(psrc);
-
- *MAPRW(pdst) &= ~0L;
-
- This is an example of what they do. MAPR maps a pointer from a
- virtual frame to the physical frame, and can set the WRITE direction
- to the bank where pdst points to. MAPR maps a pointer from a virtual
- frame to the physical frame, and can set the READ direction to the
- bank where src points to. MAPRW does the same thing, except for
- setting the direction of the bank to READ-WRITE. I think this should
- be general enough to handle VGA boards in mono mode with banking.
- For my Hercules card, I need only one sort of MAP's though.
-
- If anyone has done anything similar to mfb, I'd apprechiate some
- comments and suggestions on what might go wrong. I'm not sure
- if this will work, and haven't started debugging yet. If anyone
- wants to help, you are more than welcome.
-
- Davor
-