Ville Syrjälä wrote:
My previous comment on irc about anisotropic filtering needing two mip
levels was crap. Fortunately I've since managed to figure out the real
details.

The good news is that G550 doesn't have any problems with anisotropic
filtering.

The bad news is that G4x0 chips need both texture units to pull it off.
Both units must be programmed with the same parameters or the chip will
lock up. So G4x0 can't do anisotropic filtering with dual texturing :(

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? 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.


Keith



-------------------------------------------------------
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

Reply via email to