From: "Indan Zupancic" <indan@nul.nu>
To: "Rene Herman" <rene.herman@gmail.com>
Cc: "Ingo Molnar" <mingo@elte.hu>,
teresa@kvitka.net, "Andi Kleen" <andi@firstfloor.org>,
"Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>,
"CK Mailinglist" <ck@vds.kolivas.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
dmitry.torokhov@gmail.com, dtor@mail.ru
Subject: OT: enabling Xcomposite [was: Linux Kernel cfs scheduler and xorg kbd]
Date: Mon, 6 Aug 2007 20:26:35 +0200 (CEST) [thread overview]
Message-ID: <50209.81.207.0.53.1186424795.squirrel@secure.samage.net> (raw)
In-Reply-To: <46B75E8E.1040305@gmail.com>
On Mon, August 6, 2007 19:46, Rene Herman wrote:
> On 08/06/2007 05:19 PM, Indan Zupancic wrote:
>
> [ Yes, OT, I'll shelve it after this ]
Me too, and I wonder if we should've dropped a bunch of CCs...
>
>> Anyway, if you want to experience a shock, try enabling xcomposite and
>> run xcompmgr -a or something. It's so wonderfully smooth (even though
>> some rendering seems slower than before, it's really worth it for me).
>
> Don't believe I can -- using a Matrox Millenium G550 (driver mga) and
> nothing I do seems to have an effect.
Well, as far as I know adding the following to your xorg.conf should be enough:
Section "Extensions"
Option "Composite" "enable"
EndSection
and then to enable it at runtime start a composite manager.
Reading the mga manpage it seems you need to add
Option "AccelMethod" "EXA"
to the driver section. (Though it says EXA is possibly unstable.)
Run "xdpyinfo | grep Composite" to see if it works or not.
But as you said, getting off-topic, so if the above doesn't work sent a
private mail, or go to the xorg mailinglist.
Greetings,
Indan
next prev parent reply other threads:[~2007-08-06 18:26 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 20:25 Linux Kernel cfs scheduler and xorg kbd <::.. Teresa_II ..::>
2007-07-30 22:49 ` Michal Piotrowski
2007-08-01 6:48 ` Ingo Molnar
2007-08-01 11:31 ` Andi Kleen
2007-08-01 11:01 ` Rene Herman
2007-08-01 12:34 ` Indan Zupancic
2007-08-01 12:50 ` Rene Herman
2007-08-01 13:07 ` Indan Zupancic
2007-08-01 13:26 ` Rene Herman
2007-08-01 13:33 ` <:::.. TeresaII ..:::>
2007-08-01 13:58 ` Rene Herman
2007-08-01 14:44 ` <::.. Teresa_II ..::>
2007-08-01 15:00 ` [ck] " Matthew Hawkins
2007-08-01 15:53 ` <::.. Teresa_II ..::>
2007-08-02 7:11 ` Sébastien Dugué
2007-08-02 12:22 ` Rene Herman
2007-08-02 13:18 ` Indan Zupancic
2007-08-01 15:06 ` Indan Zupancic
2007-08-01 15:09 ` Ingo Molnar
2007-08-01 15:13 ` Rene Herman
2007-08-01 15:20 ` Ingo Molnar
2007-08-01 15:19 ` Rene Herman
2007-08-01 15:26 ` Indan Zupancic
2007-08-06 7:12 ` Ingo Molnar
2007-08-06 13:10 ` Rene Herman
2007-08-06 15:19 ` Indan Zupancic
2007-08-06 17:46 ` Rene Herman
2007-08-06 18:26 ` Indan Zupancic [this message]
2007-08-07 4:40 ` Kyle Moffett
2007-08-07 6:05 ` Arjan van de Ven
2007-08-07 10:17 ` Indan Zupancic
2007-08-07 13:15 ` Rene Herman
2007-08-09 21:14 ` Mark Lord
2007-07-31 11:18 ` [ck] " <::.. Teresa_II ..::>
2007-07-31 11:42 ` <::.. Teresa_II ..::>
2007-07-31 14:27 ` Ingo Molnar
2007-07-31 16:39 ` <::.. Teresa_II ..::>
2007-07-31 15:06 ` Rene Herman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50209.81.207.0.53.1186424795.squirrel@secure.samage.net \
--to=indan@nul.nu \
--cc=andi@firstfloor.org \
--cc=ck@vds.kolivas.org \
--cc=dmitry.torokhov@gmail.com \
--cc=dtor@mail.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=mingo@elte.hu \
--cc=rene.herman@gmail.com \
--cc=teresa@kvitka.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®