Now I need to change the ddx driver to tell the 3D driver if the chipset is a G550. But this causes some compatibility problems. The 3D driver doesn't have a version number so the ddx doesn't know if the 3D driver can handle the new G550 chipset type. Which means that a combination of a new ddx and an old 3D driver won't work. A new 3D driver and an old ddx will work without problems because the G550 doesn't seem to mind being programmed like a G4x0.
I had a patch that I sent out once upon a time that handled all of this. The intention was to allow the driver to give accurate card information for glGetString( GL_RENDERER ), but it had many other uses as well. Basically, I bumped the DDX minor version and had the DDX pass the PCI vendor, ID, subsystem vendor, and subsystem ID to the DRI driver.
I had a Python script that would generate a table based on pci.ids. I added some utility functions to common/util.c to search the table and return the record for a given PCI information tuple. The record had two data fields (other than the ID / vendor values). One was the card's name. The other was specified by the driver (as a parameter to the Python script). In the radeon driver I used this to specify whether or not the card had a TCL unit. For MGA I used it to specify whether the card was G200 or G400. It would be trivial to modify that to differentiate between G200, G400, or G450.
The code in common/util.c was smart enough to give a reasonable record with partial information (i.e., only a PCI ID) for backwards compatibility.
Is it worth reviving that patch in some form?
------------------------------------------------------- This SF.net email is sponsored by OSDN developer relations Here's your chance to show off your extensive product knowledge We want to know what you know. Tell us and you have a chance to win $100 http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54 _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
