video card compatibility list
Lin Tse Hsu
evfreek at yahoo.com
Fri Dec 10 02:13:29 UTC 2004
--- Joel Jaeggli <joelja at darkwing.uoregon.edu> wrote:
...
> the s3 trio64 is supported as are most videocards
> that were available 5
> years ago.
>
> If you look in /usr/X11R6/lib/X11/Cards you'll see
> quite a few s3
> chipsets.
>
I finally found the location of the README.<cards>
directory. I had to download and unpack all the .src
tarballs untill I reached the third one.
The path is:
xc/programs/Xserver/hw/xfree86/doc
but README.s3 or README.S3 is no longer present. So,
there is a fundamental difference between x.org and
XFree86. Searching for Trio64V+ in the directory
contents shows nothing of interest. So, just because
the doc file is missing does not necessarily mean that
the support has disappeared as well.
In another directory:
/home/eric/unpk/xc/programs/Xserver/hw/xfree86/drivers
the directory s3 is present. This means that some S3
chips should (could, since it could be dead code)
still be supported. The list:
/* supported chipsets */
static SymTabRec S3Chipsets[] = {
{ PCI_CHIP_964_0, "964-0"},
{ PCI_CHIP_964_1, "964-1"},
{ PCI_CHIP_968, "968" },
{ PCI_CHIP_TRIO, "Trio32/64" },
{ PCI_CHIP_AURORA64VP, "Aurora64V+" },
{ PCI_CHIP_TRIO64UVP, "Trio64UV+" },
{ PCI_CHIP_TRIO64V2_DXGX,
"Trio64V2/DX/GX" },
{ -1, NULL }
};
however, does not show the Trio64V+. But there are
some like it. The field is read in:
if (pEnt->device->chipset &&
*pEnt->device->chipset) {
pScrn->chipset =
pEnt->device->chipset;
pS3->Chipset =
xf86StringToToken(S3Chipsets, pScrn->chipset);
} else if (pEnt->device->chipID >= 0) {
pS3->Chipset = pEnt->device->chipID;
pScrn->chipset = (char
*)xf86TokenToString(S3Chipsets,
pS3->Chipset);
xf86DrvMsg(pScrn->scrnIndex, X_CONFIG,
"ChipID override: 0x%04X\n",
pS3->Chipset);
} else {
pS3->Chipset = pS3->PciInfo->chipType;
pScrn->chipset = (char
*)xf86TokenToString(S3Chipsets,
indicating that the card signature is somehow read,
and must have an exact match.
Is there any source of more authoritative
documentation, since I'm afraid that I don't really
understand the source code? Of course, all the
hackers say that the source is the documentation, but
if you've ever worked on projects with more than a
silly 10 KLOC, you know that this is not necessarily
true, since there may be dead ends, etc.
Thanks in advance for any suggestions.
__________________________________
Do you Yahoo!?
Jazz up your holiday email with celebrity designs. Learn more.
http://celebrity.mail.yahoo.com
More information about the users
mailing list