Imported Functions only

This implementation provides the greatest code reuse of the source objects 
already created and used elsewhere by the vendors. It also provides the 
performance needed in programming the timing-sensitive chip sets. 
Importing code also allows the vendor to call VIDEO BIOS as as means of 
implementing the exported function. This can be achieved only from a 
shared library. A flat .PMI file will not call VIDEOPMI's entry point. 
Provided that the shared library exports the "Load Adapter" API and 
conforms to the META-PMI definition, this method also allows for modifying 
VIDEOPMI's function by chaining into its calling table. 

The drawback to this method is that the imported objects' source code is 
developed for a specific hardware and operating system platform and has to 
be ported to a new platform. Another drawback is that the imported binary 
object may introduce execution violations unless it is thoroughly tested.