From: aho450s AT nic DOT smsu DOT edu (Tony O'Bryan)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Calling real mode far procedures
Date: Sun, 29 Dec 1996 14:25:01 GMT
Organization: Southwest Missouri State University
Lines: 14
Message-ID: <32c67e0d.852043@ursa.smsu.edu>
References: <32c563f9 DOT 7993249 AT ursa DOT smsu DOT edu> <19961229 DOT 134952 DOT 8351 DOT 2 DOT chambersb AT juno DOT com>
NNTP-Posting-Host: forseti.i31.smsu.edu
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

On Sat, 28 Dec 1996 21:45:51 GMT, chambersb AT juno DOT com (Benjamin D
Chambers) wrote:

>If you do, it's card specific.  The only one that's standardized is the
>VGA, and then you can't use svga modes.  For svga, you need specs on each
>card :(

The interrupt call is a VESA standard.  VESA 1.1 includes a standard
call to retrieve the address of the bank-swapping interrupt which can
be called directly from a real mode program.  Calling the function in
this manner eliminates the overhead involved in an interrupt call and
significantly improves the performance of the bank swap.  However, the
direct call must be made to real mode code so I need a method of
directly calling a real mode far procedure.