<idr> To do that we're going to "port" the *OLD* 500TX driver to DRI. :) <anholt> 500tx is a what? <idr> anholt: The GLINT before the MX. ... <idr> anholt: It should be *much* faster. The Delta does all the geometry setup. This is the mode the current gamma driver uses. <anholt> hmm <idr> Part of this work may lead into making some updates to the gamma driver. Does anyone have *any* docs for any of the GLINT chips? <idr> Even the old leaked TI docs for the Permedia2 would be helpful. :)
Sven Luther did some DRI work a while back for permedia/2/3 and he is currently working on a 2D driver for the new wildcat VP cards. I think 3dlabs is pretty good about giving databooks out to developers, at least they used to be. You might just want to ask them.
Also there is the tdlabs-0-0-1-branch branch in cvs http://www.geocrawler.com/archives/3/680/2002/8/0/9462918/ http://www.mail-archive.com/[EMAIL PROTECTED]/msg08196.html
I'm aware of Sven's work, and I have been in contact with him. I haven't persued getting docs form 3dlabs yet, but I may do so in the future. IBM's lawyers are *VERY* picky, so getting docs under NDA for use in open-source projects is *VERY* difficult for IBMers. I still don't have R100 or R200 docs, and I've been working on those drivers for over a year and a half. :(
<idr> fxkuehl: I have a Savage/IX (or something similar) in my ThinkPad T21. ... <anholt> so is the savage4 the same sort of thing as a savage mx/ix? ... <idr> anholt: I believe so.
Actually the savage mx/ix chips are based on the old savage3D core, while the DRI driver is for savage4/prosavage cores. I don't know how similar they are and whether the driver S3/VIA released will work on the older savage3D based chips like the mx or ix. they might need a separate driver much like the radeon r100 vs. r200.
Are you sure about that? Once-upon-a-time I tried to get the old Utah-GLX driver to work on it but had no luck at all. I was still pretty green back then, but it didn't seem like the chips were very compatible. The chip that I have, according to WinS3ID is "Savage/IX w/MV (294)". The chip ID is 0x8c12, subvendor 0x1014, subdevice 0x017f. This same chip is in all the IBM T20 & T21 laptops AFAIK.
It's interesting that there's not even 3D acceleration for this particular chip in Windows. That would be a nice open-source coup. :)
In any case, I would really *NOT* like to see another driver end up like the r100 / r200 driver. The MGA driver, where multiple chips in the same family are supported by the same binary, is a much better model to follow, IMHO. My plan with the 500TX driver is to eventually merge it with the gamma driver and re-name that driver to glint. gamma is a very bad name for that driver since the gamma isn't even really used! Looking at the existing 500TX code, the existing gamma code, and Sven's work in the tdlabs branch, it seems like the drivers for all the chips in the GLINT family should be quite similar. That family may be the poster child for a unified driver architecture. :)
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
