On Thu, Oct 16, 2003 at 09:29:36AM +0100, Keith Whitwell wrote: > > 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'm thinking that I should just ignore the problem because I doubt many > > people will upgrade the ddx driver and keep the old 3D driver. Any > > better ideas? > > Does the kernel have the information you need?
Not at the moment. I can change the ddx to pass the information to the drm. > We've added 'GetParam' ioctls > in the past to query these sorts of details, as the interface is easier to > deal with than the X protocol extension used to talk to the DDX driver. If it > doesn't have the information, you could also consider adding a 'SetParam' > ioctl so that the DDX driver can tell the kernel at init time. Ok. I can do it without a SetParam ioctl because the mga drm init struct already includes a field for the chip type. I'll just have to make the drm handle the new G550 chip type and add the GetParam ioctl stuff. -- Ville Syrjälä [EMAIL PROTECTED] http://www.sci.fi/~syrjala/ ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
