VESA Video Modes

Intro

I really wish setting VESA resolutions was as easy as setting a standard video mode. Unfortunately, reality is against us! Back in the old days of Video Cards there was a lot of technological advancements happening. Each big company had its own idea of what abilities should be in the card, and what should be the correct process in making it easy to utilize and program. What turned out was a programmers nightmare! Each company ended up selling a card that was completely incompatible with its competition. FINALLY in 1989, VESA was born. They are the Video Electronic Standard Association. We will be dealing specifically with VESA VBE or Video Bios Extensions. This allows each card to have its own unique set of capabilities, but the VBE creates another level of abstraction between the programmer and the hardware. This creates a nice interface for the programmer which can use the VBE to get information about whatever card is available.

Detecting VESA Availability

First off, lets figure out which (if any) VESA version is available. To do this, we will create a structure to hold some card information.

C [Show Plain Code]:
  1. typedef struct VBE_VgaInfo   
  2. {
  3.     char VESASignature[4];
  4.     short VESAVersion;
  5.     char *OemStringPtr;
  6.     ulong Capabilities;
  7.     ulong VideoModePtr;
  8.     short TotalMemory;
  9.    
  10.     //VBE 2.0
  11.     short OemSoftwareRev;
  12.     char *OemVendorNamePtr;
  13.     char *OemProductNamePtr;
  14.     char *OemProductRevPtr;
  15.     char reserved[222];
  16.     char OemData[256];
  17. };

This is the structure used to hold information about the VESA Graphics information. To start off we will only be using the VESASignature,Version and TotalMemory variables. Later on as we make our code more detailed we can decide wether to support the other structure members. Lets create a function that determines if VESA is available and if so, what version!

C [Show Plain Code]:
  1. VBE_VgaInfo vesainfo;
  2. long VESAVerMaj,VESAVerMin;
  3.  
  4. int Video::Detect_VESA()
  5. {
  6.     __dpmi_regs r;
  7.     strncpy(vesainfo.VESASignature,"VESA",4); <font color="black">//or VBE2</font>
  8.     r.x.ax=0x4F00;
  9.     r.x.di=__tb&0x0f;
  10.     r.x.es=(__tb >>4)&0xFFFF;
  11.     dosmemput(&vesainfo,sizeof(vesainfo),__tb);
  12.     __dpmi_int(0×10,&r);
  13.     dosmemget(__tb,sizeof(vesainfo),&vesainfo);
  14.     if(r.h.ah||strncmp("VESA",vesainfo.VESASignature,4)||vesainfo.VESAVersion <0×100)
  15.     {
  16.        return 0; //VESA NOT present
  17.     }
  18.     
  19.     VESAVerMaj=vesainfo.VESAVersion >>8;
  20.     VESAVerMin=vesainfo.VESAVersion & 0x0f;
  21.     if(VESAVerMaj > 2.0)
  22.     {
  23.        GetPMInterface();
  24.        Bankptr = &Video::SetBankAlt;
  25.     }
  26.     else
  27.     {
  28.        Bankptr = &Video::SetBankBIOS;
  29.     }
  30.  
  31.     return 1;
  32. }

This code is to be used in DJGPP, but the same principle applies to normal C++. We use the bios function 0x4F00. We will set ax=4F00 and set ES:DI to a far pointer to our little structure we have created. When we call interrupt 0×10 (video interrupt), the result will be located in ax. If ax=4F00 after the call, then VESA functions are supported, any other number will be interpreted as no. Our structure will be filled in after the call. Notice that we are filling in vesainfo.VESASignature with “VESA” before calling the interrupt. This tells the BIOS that we are requesting VESA information, VESA 2.0 items WILL NOT BE FILLED IN! The new standard is to fill in the signature with “VBE2″ so that all VESA 2+ information will be filled in! Also notice that we are setting a function pointer Bankptr. This is used in the MoveMemVESABanked function. If we have access to the protected mode information (VESA 2.+) then we can use a different function for bank switching that doesn’t need to go through the BIOS. That function is SetBankAlt, and the much slower one is SetBankBIOS.

C [Show Plain Code]:
  1. void Video::PrintVESAInfo()
  2. {
  3.     char buffer[255];
  4.     short modes[255];
  5.     long temp;
  6.     short t;
  7.  
  8.     cout<<"VESA "<<VESAVerMaj<<"."<<VESAVerMin<<endl;
  9.     cout<<"Video Memory: "<<dec<<(long)(vesainfo.TotalMemory*64)<<"k"<<endl;
  10.  
  11.     temp=vesainfo.OemStringPtr;
  12.     t = __dpmi_segment_to_descriptor((temp>>16));
  13.     movedata(t,(temp&0xFFFF),_my_ds(),(int)&buffer,255);
  14.     cout<<buffer<<endl;
  15.  
  16.     temp=vesainfo.OemVendorNamePtr;
  17.     t = __dpmi_segment_to_descriptor(temp>>16);
  18.     movedata(t,(temp&0xFFFF),_my_ds(),(int)&buffer,255);
  19.     cout<<buffer<<endl;
  20.  
  21.     temp=vesainfo.OemProductNamePtr;
  22.     t = __dpmi_segment_to_descriptor(temp>>16);
  23.     movedata(t,(temp&0xFFFF),_my_ds(),(int)&buffer,255);
  24.     cout<<buffer<<endl;
  25.  
  26.     temp=vesainfo.OemProductRevPtr;
  27.     t = __dpmi_segment_to_descriptor(temp>>16);
  28.     movedata(t,(temp&0xFFFF),_my_ds(),(int)&buffer,255);
  29.     cout<<buffer<<endl;
  30. }

This function prints out all the extended OEM VESA information that is available when you fill in the signature with VBE2.

Getting Supported Modes

Now that we know a little about the card, we will create a function that fetches VESA video mode information. This function in order to be truly useful, must request information from the system about the video mode we have switched to. Remember that VESA modes are larger than 65536 bytes and will require bank switching to update the screen or use the linear frame buffer. To do this properly we must know the some screen information, foremost being the granularity of memory. This structure is as follows:

C [Show Plain Code]:
  1. typedef struct VBE_ModeInfo
  2. {
  3.     short ModeAttributes;
  4.     char WinAAttributes;
  5.     char WinBAttributes;
  6.     short WinGranularity;
  7.     short WinSize;
  8.     ushort WinASegment;
  9.     ushort WinBSegment;
  10.     void *WinFuncPtr;
  11.     short BytesPerScanLine;
  12.     short XRes;
  13.     short YRes;
  14.     char XCharSize;
  15.     char YCharSize;
  16.     char NumberOfPlanes;
  17.     char BitsPerPixel;
  18.     char NumberOfBanks;
  19.     char MemoryModel;
  20.     char BankSize;
  21.     char NumberOfImagePages;
  22.     char res1;
  23.     char RedMaskSize;
  24.     char RedFieldPosition;
  25.     char GreenMaskSize;
  26.     char GreenFieldPosition;
  27.     char BlueMaskSize;
  28.     char BlueFieldPosition;
  29.     char RsvedMaskSize;
  30.     char RsvedFieldPosition;
  31.    
  32.     //VBE 2.0</font>
  33.     ulong PhysBasePtr;
  34.     ulong OffScreenMemOffset;
  35.     short OffScreenMemSize;
  36.    
  37.     //VBE 2.1</font>
  38.     short LinbytesPerScanLine;
  39.     char BankNumberOfImagePages;
  40.     char LinNumberOfImagePages;
  41.     char LinRedMaskSize;
  42.     char LinRedFieldPosition;
  43.     char LingreenMaskSize;
  44.     char LinGreenFieldPosition;
  45.     char LinBlueMaskSize;
  46.     char LinBlueFieldPosition;
  47.     char LinRsvdMaskSize;
  48.     char LinRsvdFieldPosition;
  49.     char res2[194];
  50. };
  51. VBE_ModeInfo modeinfo;

Pretty darn huge isn't it! Now that we know this structure, here is a function that utilizes it. We are going to be using this function in conjunction with another one to fetch all available video modes supplied by the VESA, then save mode information to a dynamically allocated structure so we only have to bother the VESA one time per mode when we start up.

C [Show Plain Code]:
  1. int Video::GetVESAModeInfo(short mode)
  2. {
  3.     __dpmi_regs r;
  4.     r.x.ax=0x4F01;
  5.     r.x.cx=mode;
  6.     r.x.di=__tb & 0x0F;
  7.     r.x.es=(__tb >>4)&0xFFFF;
  8.     __dpmi_int(0x10,&r);
  9.     dosmemget(__tb,sizeof(modeinfo),&modeinfo);
  10.     if(r.h.ah)
  11.     {
  12.        return 0; <font color="black">//failure!
  13.     }
  14.     return 1;
  15. }

This little section is programmed for DJGPP. It uses a temporary buffer that is already created called tb that is located in lower memory. All we need to know is that our huge mode structure will be filled in correctly after calling this routine. What we really need this function for is to know the granularity of the video mode we specified. Think of granularity as how large the memory chunks are. We need to fetch this vital mode information in order for our memory moving routines to work correctly. Here's the function that utilizes the above function and structure to get all available VESA modes according to the VESA supplier.

C [Show Plain Code]:
  1. void Video::GetAvailableVESAModes()
  2. {
  3.     long temp;
  4.     short t,*m,count=0;
  5.     temp=vesainfo.VideoModePtr;
  6.  
  7.     m=(short *)MK_FP(temp>>16,temp&0xFFFF);
  8.  
  9.     while(m[count] != -1)
  10.     {
  11.      count++;
  12.     }
  13.    
  14.     NumberOfModes = count;
  15.     cout<<NumberOfModes<<" Video Modes Available\n";
  16.     Modes = new short[NumberOfModes];
  17.     if(Modes ==NULL)
  18.     {
  19.       cout<<"Error allocating Mode Number Listing!\n";
  20.     }
  21.    
  22.     for(temp=0;temp<NumberOfModes;temp++)
  23.     {
  24.        Modes[temp]=m[temp];
  25.     }
  26.    
  27.     ModeList = new VBE_ModeInfo[NumberOfModes];
  28.     if(ModeList == NULL)
  29.     {
  30.        cout<<"Error allocating ModeList!\n";
  31.     }
  32.    
  33.     for(count=0;count<NumberOfModes;count++)
  34.     {
  35.         GetVESAModeInfo(Modes[count]);
  36.         memmove(&ModeList[count],&modeinfo,sizeof(VBE_ModeInfo));
  37.     }
  38. }
  39.  
  40. void * Video::MK_FP(unsigned short seg, unsigned short ofs)
  41. {
  42.     if(!(_crt0_startup_flags & _CRT0_FLAG_NEARPTR))
  43.      if(!__djgpp_nearptr_enable())
  44.             return (void*)0;
  45.     return (void *)(seg*16+ofs+__djgpp_conventional_base);
  46.  }

In order for this function to work, you must have Modes declared as a short pointer. This function is a must for anyone who wants to support as many modes as the video card can handle. VESA no longer requires manufacturers to follow any guidelines for video mode numbers, so VESA came up with a way to give the programmer a list of available video modes. We fetch the video modes by setting our pointer to the one given to us by the VESA, save them in a list (Modes) with the list terminating with -1, and then get video mode information for each one. This is only done one time during the program, so it is really nice when you need mode information quick, it'll be there waiting for you! Following is the protected mode version of the Make File Pointer function used with standard Real-Mode C.

Setting VESA Modes

Without any further delay, lets go into the function that actually changes the Video Mode. As you can see, we have a lot more options to keep track of compared to normal VGA resolutions!

C [Show Plain Code]:
  1. unsigned short Video::GetModeIndex(short Xres,short Yres,short Depth)
  2. {
  3.     unsigned short temp=666;
  4.     for(short count=0;count<NumberOfModes;count++)
  5.     {
  6.       if((ModeList[count].XRes == Xres) &&
  7.          (ModeList[count].YRes == Yres) &&
  8.          (ModeList[count].BitsPerPixel == Depth))
  9.         {
  10.           temp=count;
  11.         }
  12.     }
  13.     return temp;
  14. }
  15.  
  16. void Video::VESAMode(short index)
  17. {
  18.     __dpmi_regs r;
  19.     memset(&r,0,sizeof(__dpmi_regs));
  20.     r.x.ax=0x4F02;
  21.     r.x.bx=Modes[index];
  22.     UsingLinearFrameBuffer(index);
  23.  
  24.     if(LinearFrameBuffer)
  25.     {
  26.       r.x.bx+=0x4000; //bit 14 0100 0000 0000 0000
  27.     }
  28.  
  29.     if(!ClearMem)
  30.     {
  31.      r.x.bx+=0x8000; //bit 15 1000 0000 0000 0000
  32.     }
  33.  
  34.     __dpmi_int(0x10,&r);
  35.  
  36.     if(r.x.ax !=0x004f)
  37.     {
  38.      VideoMode(80,25,8);
  39.         cout<<"Failure to set VESA video mode "<<hex<<Modes[index]<<endl;
  40.         sleep(4);
  41.         RevertToSavedModeData();
  42.         VideoMode(Screen_Width,Screen_Height,Screen_BitsPerPixel);
  43.     }
  44.     VideoModeIndex=index;
  45.     CurrentVideoMode=Modes[VideoModeIndex];
  46.     Screen_Width  = ModeList[VideoModeIndex].XRes;
  47.     Screen_Height = ModeList[VideoModeIndex].YRes;
  48.     Screen_Size   = Screen_Width*Screen_Height;
  49.     XCenter = (Screen_Width>>1);
  50.     YCenter = (Screen_Height>>1);
  51.    
  52.     //Only used when no LFB is present
  53.     NumberOfBanks=Screen_Size>>16;
  54.     MemAfterBanks=Screen_Size&65535;
  55.     if(LinearFrameBuffer)
  56.     {
  57.      MapLFB(index);
  58.         Move2Vid=&Video::MoveMemStandard;
  59.     }
  60.     else
  61.     {
  62.       Move2Vid = &Video::MoveMemVESABanked;
  63.     }
  64.  
  65.     SaveModeData(); //success so save!
  66.     cout<<"Current mode = "<<CurrentVideoMode<<endl;
  67. }

Our VESAMode function changed quite a bit since our last version of this tutorial for those that read it. Notice that this function is also getting passed an index number. Again, this index is the index into our supported video mode listing (Modes). All of our saved video mode information is saved under the ModeList list. Ok, from the top we start setting up our registers for our interrupt, setting ax to 0x4f02, bx to our mode number, we then test to see if that mode supports a Linear Frame Buffer by calling UsingLinearFrameBuffer. That function sets the class variable LinearFrameBuffer. It is supported if it is set to one, and no if it is set to 0. We then turn on bit 14 accordingly. We can also choose if we want VGA ram erased or saved after the modeswitch by setting bit 15 and using the class variable ClearMem. We then generate our interrupt using __dpmi_int. We then check to see if we were successful in switching modes. If we weren't we switch to text mode and spit out an error message, sleep 4 seconds, then switch to our previously saved video mode. Do whatever you like in the instance a switch mode fails. We then set a bunch of screen class variables. If we are in a mode that supports a LFB, we then call MapLFB which makes the Linear Frame Buffer accessible to us. We also set our Move2Vid function pointer to one of two functions. MoveMemStandard is used when we have access to a LFB, and MoveMemVESABanked is used when we must do bank switching. When it is all said and done, we call SaveModeData so if the next switch fails, we can revert to this previous mode! Here's a quick listing of what some of those other functions are:

C [Show Plain Code]:
  1. void Video::UsingLinearFrameBuffer(short index)
  2. {
  3.     if(ModeList[index].ModeAttributes & 0x80)
  4.     {
  5.         LinearFrameBuffer = 1;
  6.         cout<<hex<<Modes[index]<<"h uses a LFB"<<dec<<endl;
  7.     }
  8.     else      
  9.     {
  10.      LinearFrameBuffer = 0;
  11.     }
  12. }
  13.  
  14. void Video::SaveModeData()
  15. {
  16.     savedmode = CurrentVideoMode;
  17.     savedxres = Screen_Width;
  18.     savedyres = Screen_Height;
  19.     saveddepth= Screen_BitsPerPixel;
  20.     savedindex= VideoModeIndex;
  21. }
  22.  
  23. void Video::RevertToSavedModeData()
  24. {
  25.     CurrentVideoMode   = savedmode;
  26.     Screen_Width       = savedxres;
  27.     Screen_Height      = savedyres;
  28.     Screen_BitsPerPixel= saveddepth;
  29.     VideoModeIndex     = savedindex;
  30. }

These really aren't that hard to decypher. UsingLinearFrameBuffer tests the ModeAttributes attribute in the modeinfo structure for the video mode, testing to see if the correct bit is set, setting LinearFrameBuffer accordingly. SaveModeData and RevertToSavedModeData I HOPE are self explaining :) Now onto using that darn Linear Frame Buffer!

Using the Linear Frame Buffer

The Linear Frame Buffer was made available in VESA 2.0. Prior, the VESA Video RAM was larger than 65536 bytes, so in order to access Video RAM that was larger, special proceedures were used. Bank switching let the programmer have access to all of Video RAM. The big problem was that bank switching was really slow! A Linear Frame Buffer allows the programmer to treat Video RAM as one continuous array, just like in good old 320x200!! It is not only easier, but faster!

C [Show Plain Code]:
  1. //In Class constructor
  2.  
  3.  my_video_ds=__dpmi_allocate_ldt_descriptors(1);
  4.  __dpmi_set_segment_base_address(my_video_ds,0xA000+__djgpp_conventional_base);
  5.  __dpmi_set_segment_limit(my_video_ds,2000000);
  6.  
  7. void Video::MapLFB(short index)
  8. {
  9.     __dpmi_meminfo info;
  10.     info.size=vesainfo.TotalMemory<<16;
  11.     cout<<"Mapping "<<info.size<<" bytes for Linear Frame Buffer"<<endl;
  12.     info.address=(unsigned long)ModeList[index].PhysBasePtr;
  13.     cout<<"Pointer to LFB = "<<hex<<ModeList[index].PhysBasePtr<<"h"<<dec<<endl;
  14.     if(__dpmi_physical_address_mapping(&info)!=0)
  15.     {
  16.         cout<<"Can't map Linear Frame Buffer!\n";
  17.     }
  18.  
  19.  
  20.     __dpmi_free_ldt_descriptor(my_video_ds); //allocated in constructor so erase
  21.     my_video_ds=__dpmi_allocate_ldt_descriptors(1);
  22.     __dpmi_set_segment_base_address(my_video_ds,info.address);
  23.     __dpmi_set_segment_limit(my_video_ds,info.size-1);
  24.     cout<<"Base address = "<<hex<<info.address<<dec<<endl;
  25.  
  26.     video_screen=(unsigned char *)((unsigned long)info.address+__djgpp_conventional_base);
  27. }

Before we even think about using the Linear Frame Buffer, we have to map it into our addressable space. We accomplish this by getting the pointer to it from the modeinfo structure for the video mode we want to use. We don't actually have to be in the mode for this function, just have our modeinfo list filled in correctly. We use index as an index (how genius) into our list. Remember that when we do switch to the video mode, before or after this function, we have to set the LFB bit in the mode attribute. This should be taken care of automatically if we used our cool VESAMode function! After this function exits, it reassigns our video_screen pointer to point to the Linear Frame Buffer in our addressable region! Now we can treat it as normal VGA ram with NO limitations!! The last portion of the code that uses my_video_ds is for those that don't like to directly access video ram as if it was a linear array and use farpoke or farpeek. my_video_ds provides access to video ram for those functions.

Using the Protected Mode Information

C [Show Plain Code]:
  1. typedef struct PM_Int
  2. {
  3.     unsigned short SetWindow Packed;
  4.     unsigned short SetDisplayStart Packed;
  5.     unsigned short SetPalette Packed;
  6.     unsigned short IOPrivInfo Packed;
  7. };
  8.  
  9. void (*pm_bank)(char);
  10. void (*pm_setstart)(char);
  11. void (*pm_setpalette)(char);
  12. PM_Int* pm_info;
  13.  
  14. void Video::GetPMInterface()
  15. {
  16.     __dpmi_regs regs;
  17.     regs.x.ax=0x4F0A;
  18.     regs.x.bx=0;
  19.     __dpmi_int(0x10,&regs);
  20.     if(regs.h.ah)
  21.     {
  22.       cout<<"\nError gaining access to VESA Protected Mode Interface!\n";
  23.     }
  24.     if(pm_info != NULL)
  25.     {
  26.      free(pm_info);
  27.     }
  28.     pm_info = (PM_Int *)malloc(regs.x.cx);
  29.     _go32_dpmi_lock_data(pm_info,regs.x.cx);
  30.     dosmemget((regs.x.es*16)+regs.x.di,regs.x.cx,pm_info);
  31.     pm_bank     = (void*)((char*)pm_info+pm_info->SetWindow);
  32.     pm_setstart = (void*)((char*)pm_info+pm_info->SetDisplayStart);
  33.     pm_setpalette=(void*)((char*)pm_info+pm_info->SetPalette);
  34.  
  35.     return;
  36. }

Using BIOS functions are notoriously slow, so the VESA BIOS provides us with some faster means of getting stuff done. Probably the most important is the pm_bank switch function that can switch VESA video banks without having to go through the BIOS! The structure that is filled in by the BIOS or actually pointed to by the BIOS actually tells us how far from that structure in memory each function resides, hence the wierdo routine for setting the function pointers!

There we have it. For more information on accessing a specific bank or moving memory to Video Ram using an Offscreen Buffer please take a look here.

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>