Hi, 2008/11/1 <[EMAIL PROTECTED]>: [...] > > Setting resolution works flawlessly now. By using glxgears it got 98% cpu > usage - which is about the same > as when using vesa.
Right, but that's an issue with the 3d driver (mesa), not with openchrome. > While I'm disappointed about this (i got higher framerate and way less cpu > usage by comilling on my own) How did you compile the driver (IOW: what flags/options/etc did you use)? > you can consider the bug "fixed", as my main problem is solved. Ok, but I'll wait for the others to report whether it works ok now. > > If I can contribute anything by testing, mail me. Thank you very much for > your packaging work! If you want to test something you can take a look at the package in experimental (but beware of some issues when using XAA with the version of xorg in experimental: http://www.openchrome.org/trac/ticket/263) > > Mathieu Cheers, -- Raphael Geissert - Debian Maintainer www.debian.org - get.debian.net Tallulah Bankhead - "If I had to live my life again, I'd make the same mistakes, only sooner." -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
