Chapter 3. Getting Started 1In This Chapter

Chapter 3. Getting Started

1In This Chapter

• 
  initialize Glide
  
• 
  configure and initialize the hardware
  
• 
  manage multiple Voodoo Graphics subsystems
  
• 
  terminate cleanly
  
• 
  manage the display buffers
  
• 
  detect and respond to errors
  

2Starting Up

Glide provides several functions to initialize Glide and to detect and configure a Voodoo Graphics subsystem. Two routines, grSstQueryHardware() and grSstQueryBoards() detect the presence of Voodoo Graphics subsystems. Three functions, grGlideInit(), grSstSelect(), and grSstWinOpen(), initialize Glide and the hardware and must be called, in the order listed, before calling any other Glide routines (except grSstQueryHardware() and grSstQueryBoards()). Failing to do this will cause the system to operate in an undefined (and, most likely, undesirable) state.
typedef struct {
int num_sst;
GrSstConfig_t SSTs[MAX_NUM_SST];
} GrHwConfiguration;


FxBool grSstQueryBoards( GrHwConfiguration *hwConfig )


FxBool grSstQueryHardware( GrHwConfiguration *hwConfig )
grSstQueryBoards() determines the number of installed Voodoo Graphics subsystems and stores this number in hwConfig®num_sst. No other information is stored in the structure at this time; grSstQueryHardware() can be called after grGlideInit() to fill in the rest of the structure. grSstQueryBoards() is the only Glide routine that can be called before grGlideInit(); it does not change the state of any hardware, nor does it render any graphics.
grSstQueryHardware() detects the presence of one or more Voodoo Graphics subsystems and determines how they are configured. It should be called immediately after grGlideInit() but before any other Glide functions.

Download 6.22 Mb.

Share with your friends: