From: Iain T. <Iai...@nt...> - 2001-03-04 19:06:39
|
On Sun, 4 Mar 2001 dr...@ar... wrote: > On Sun, Mar 04, 2001 at 06:01:11AM +0000, Iain Thomas wrote: > > On Sun, 4 Mar 2001 dr...@ar... wrote: > > > Then around February 28th (and again up through today), I updated to > > > the latest DRI CVS, and forgot to make a backup of my old tree > > > (OOPS!). > > Just to say that cvs update can also transform your tree to another > > version; you can step back day-by-day to find a release that works. > > I'll be fairly quiet about my Radeon and KT7-RAID working fine because I > > haven't updated my CVS tree for a while, and am taking the driver from the > > GATOS CVS- me want video-in to work... > Would you mind saying a date at which your drivers worked? I have > tried January 15th again, and I distinctly remember it compiling and > working just fine the last time, but somehow it seems that CVS has > changed its mind about when exactly January 15th is, and with such a > big tree I could understand it messing something like this up. Could > be user error, though. Well, last change I've got (looking at CVS/Entries) is Wed Feb 14 16:36:10 2001. > Anyway, with each day backing up meaning a 5-minute CVS checkout plus > 30 minute build plus 5-10 minutes testing time, I just don't have the > time to mess around with it (but I will anyway ;) ). And even assuming > I found a date that did work, the goal of the DRI project is > (obviously) to get the most recent drivers to work, not the ones from > a while back, unless your development cycle is running in reverse. I'm > now checking out January 14th and working my way back; I'll report > back with results. I am currently building the latest CVS trunk; I will trivially report on my findings. Initially with the non-GATOS driver, but I'll probably switch back to that one- unless the DRI code has the GATOS/Theatre support. Thinking about this... What exactly do you do to the Theatre chip on mode switches? It kills xawtv- scaling works, however, it's as if I'd hit Pause on my video player... > To the other reply to my first mail, current drivers say AGP 1x, > regardless of 4x enabled or disabled in BIOS. Old drivers reported AGP > 2x, and that was all my old board could handle anyway. Mine also say AGP 2x, never seen 1x, nor 4x. I'm not too into 3D stuff (well, I may well spend some time getting HalfLife/Counterstrike working, and since sindows has started refusing to boot at all, I'll be updating wine also... Where's that TransGaming patch?) Not before been bothered about AGP4x, as I view it mostly as marketing guff, and I already have a 64M card, which seems to have enough texture space for Chromium... Of course, it could be that the VIA chipset has problems with AGP 1x mode, but is fine in AGP 2x.... Have you got AGP Driving control set to anything (BIOS), or any of the wait-states enabled (I just have Fast Writes, and Enhance Chip Performance selected, with BIOS rev WW). -- Regards, Iai...@di.... My website: http://www.warwick.ac.uk/~csuli/ XMMS now playing: The first night |