[Dri-devel] AW: [Dri-users] starting xawtv it says 'no overlay function'

2004-03-09 Thread Mario Premke
> > - starting xawtv it says 'no overlay function' (and something like: > > trouble with v4l-conf) and the content of the xawtv frame is > > scrumbled - I haven't had this behaviour before and didn't touch the > > XF86Config --- any hints ??? > don't know. What chip do you have? I can't see that w

AW: [Dri-devel] S3 SavageDDR

2003-12-22 Thread Mario Premke
Hello, > > I havn't seen my Xserver crash and restart yet. If you could find out > why it crashes (segmentation fault?) and where that would be very > helpful. For a start look at the end of your /var/log/XFree86.0.log. > When the Xserver crashed XFree86.0.log reported something like 'Couldn't in

[Dri-devel] S3 SavageDDR

2003-12-18 Thread Mario Premke
Hello, the new SavageDDR DRI driver compiles and seems to run. glxinfo doesn't show 'Indirect Rendering' any more, but starting q3demo or a 3D screensaver the X-Server crashes and restarts, is that what is meant by: ' ... - almost certain lockups on vt switches and when moving 3D windows ...' ?

AW: [Dri-devel] Compilation Error

2003-12-17 Thread Mario Premke
OTO -DCPP_PROGRAM="\"cpp\"" -DHAS_MERGE_CONSTANTS=`if gcc -m32 > -fmerge-constants -xc /dev/null /dev/null 2> > /dev/null 1> > /dev/null; then echo 1; else echo 0; fi` -c -o imake.o imake.c > gcc: cannot specify -o with -c or -S and multiple compilation

AW: [Dri-devel] Compilation Error

2003-12-17 Thread Mario Premke
ull; then echo 1; else echo 0; fi` -c -o imake.o imake.c gcc: cannot specify -o with -c or -S and multiple compilations make[2]: *** [imake.o] Error 1 make[2]: Leaving directory `/home/mapr/DRI-CVS/xc/xc/config/imake' make[1]: *** [imake.bootstrap] Error 2 make[1]: Leaving directory

[Dri-devel] Compilation Error

2003-12-17 Thread Mario Premke
Hello list, I made a CVS checkout and edited the host.def like it is described in the Compilation Guide. Now I get a compilation error - apparently because of combining the '-c' and '-o' compiler flags, what seems reasonable to me ... shouldn't it possibly compile in two steps [first with '-c' and