Eliminate all references to xgifb and donttrustpdc.

The references to xgifb are clearly hold-overs from the SiS driver.
It should be clear that the places the refered to "xgifb" actually
meant "sisfb".  Note the reference to 2.4 kernels. :)
This commit is contained in:
Ian Romanick
2006-11-17 14:16:44 -08:00
parent df9d640b6e
commit 800620339d
2 changed files with 0 additions and 27 deletions

View File

@@ -887,13 +887,6 @@ typedef struct {
int xgi6326yfilterstrong;
int xgi6326tvplug;
int xgi6326fscadjust;
BOOL xgifbfound;
BOOL donttrustpdc; /* Don't trust the detected PDC */
unsigned char xgifbpdc, xgifbpdca;
unsigned char xgifblcda;
int xgifbscalelcd;
unsigned long xgifbspecialtiming;
BOOL xgifb_haveemi;
int EMI;
int NoYV12; /* Disable Xv YV12 support (old series) */

View File

@@ -2576,26 +2576,6 @@ XGIPreInit(ScrnInfoPtr pScrn, int flags)
}
}
/* Now check if xgifb is loaded. Since xgifb only supports
* the 300 and 315 series, we only do this for these chips.
* We use this for checking where xgifb starts its memory
* heap in order to automatically detect the correct MaxXFBMem
* setting (which normally is given by the option of the same name).
* Under kernel 2.4.y, that only works if xgifb is completely
* running, ie with a video mode because the fbdev will not be
* installed otherwise. Under 2.5 and later, xgifb will install
* the framebuffer device in any way and running it with mode=none
* is no longer supported (or necessary).
*/
pXGI->donttrustpdc = FALSE;
pXGI->xgifbpdc = 0xff;
pXGI->xgifbpdca = 0xff;
pXGI->xgifblcda = 0xff;
pXGI->xgifbscalelcd = -1;
pXGI->xgifbspecialtiming = CUT_NONE;
pXGI->xgifb_haveemi = FALSE;
pXGI->xgifbfound = FALSE;
/*
* The first thing we should figure out is the depth, bpp, etc.