Re: [Dri-devel] Radeon 7500, keyboard (shift, ctr, alt) problems?

2004-03-28 Thread Mike Mestnik
I have seen this also on my laptop(mach64) and my desktop(radeon). It just started happining recently. --- Daniele Boffi <[EMAIL PROTECTED]> wrote: > At the beginning I thought is was a hardware problem, even if it started > immediately after I upgraded to CVS radeon driver. But then, I noticed >

Re: [Dri-devel] mach64-0-0-7 branch and VBE TVOut. Patch included.

2004-03-28 Thread Mike Mestnik
He did respond you should be able to find his comments on the user list. IIRC He said that xv != tvout and that xv was in 0-0-7 and this seams to be the case. I think there is some dependant code missing from the tvout patch that also needs to be brought over. I used /linux/tvout-patches/mach64-

[Dri-devel] FYI: savage vast_speed_improvement

2004-03-28 Thread Marco Strack
Just checked out mesa/dri cvs and build the whole tree. And glxgears got from prior 400 to 490 fps on my t23 (1,1 ghz p3 mobile, supersavage). thats nearly 25 % faster ! good work --- This SF.Net email is sponsored by: IBM Linux Tutorial

[Dri-devel] Radeon 7500, keyboard (shift, ctr, alt) problems?

2004-03-28 Thread Daniele Boffi
At the beginning I thought is was a hardware problem, even if it started immediately after I upgraded to CVS radeon driver. But then, I noticed that the problem I am describing below doesn't show up in text mode (vt 1-6), so it must be related with X. The (pretty annoying) problem is the following

Re: [Dri-devel] mach64-0-0-7 branch and VBE TVOut. Patch included.

2004-03-28 Thread Anish Mistry
On Saturday 27 March 2004 09:55 pm, you wrote: > I'm glad too see it has worked for you. I have had problems with my > patch, may I ask how you use it and what you do to make it work? What I > did was use atitvout while in X and this worked but only if I didn't do > any mode changes or VT switche