On Thu, 2009-03-26 at 16:15 +1100, Daniel Kasak wrote:
>
> So anyway, I'm running ecomorph ( compiz port for E17 ), and most of the
> effects are very slow and jumpy.
>
> I did a quick sysprof test while switching desktops, and it looks like
> it's all in memcpy:
>
> miClearToBackground
On Thu, Mar 26, 2009 at 3:15 PM, Daniel Kasak
wrote:
> Hi all.
>
> I've brought an old r200 card out of retirement to bring some bling to
> my work desktop. I was running xserver-1.5.something with an integrated
> nvidia card. I did an upgrade to xserver-1.6, mesa-7.4-rc1 and
> xf86-video-radeon-6
On Thu, 2009-03-26 at 01:36 -0400, Alex Deucher wrote:
> On 3/26/09, Daniel Kasak wrote:
> > Hi all.
> >
> > I've brought an old r200 card out of retirement to bring some bling to
> > my work desktop. I was running xserver-1.5.something with an integrated
> > nvidia card. I did an upgrade to xs
On 3/26/09, Daniel Kasak wrote:
> Hi all.
>
> I've brought an old r200 card out of retirement to bring some bling to
> my work desktop. I was running xserver-1.5.something with an integrated
> nvidia card. I did an upgrade to xserver-1.6, mesa-7.4-rc1 and
> xf86-video-radeon-6.12.0.
>
> I don
Hi all.
I've brought an old r200 card out of retirement to bring some bling to
my work desktop. I was running xserver-1.5.something with an integrated
nvidia card. I did an upgrade to xserver-1.6, mesa-7.4-rc1 and
xf86-video-radeon-6.12.0.
I don't have any figures for previous software on this ha
In trying to track down the memory leak in 20704, I found that the DRI2
drawable destroy routine doesn't seem to get called when new drawables
are created and old ones destroyed (as in the glViewport case in the
bug).
The GLX core code takes care of destroying drawables correctly though,
and even
Hello, Julien Cristau!
>>
>> is there a bug on bugs.freedesktop.org for this?
>
> Sounds like bug#17394.
Yes, here there is a message from Ubuntu list and it also refers to
#17394 in freedesktop-bugs:
http://www.mail-archive.com/ubuntu-b...@lists.ubuntu.com/msg1072399.html
--
Michael Pozhidaev.
On Tue, 24 Mar 2009 21:54:55 +0100
Tino Keitel wrote:
> On Tue, Mar 24, 2009 at 20:54:02 +0100, Florian Mickler wrote:
> > Hi!
> > The Intel Xorg driver works with Xinerama. I'm writing you this half
> > on my 22"-Monitor and half on my Laptop's LVDS.
>
> I assume you use RandR instead of Xinera
Colin Guthrie wrote:
> 'Twas brillig, and Tino Keitel at 25/03/09 06:46 did gyre and gimble:
>> On Tue, Mar 24, 2009 at 17:47:22 -0500, tsuraan wrote:
I assume you use RandR instead of Xinerama.
>>> Does RandR do monitor placement as well as the normal Resize and
>>> Rotate? I'll have to see
Dear All:
Recently I am using RandR1.3, I found a little confuse with RandR1.3
primary output definition.
What is this parameter for?
I use the command
xrandr --output VGA --primary
I found if the VGA occupied the IGA2, after using the command line
it occupied IGA1, see
On Wed, Mar 25, 2009 at 07:26:13 +, Colin Guthrie wrote:
> 'Twas brillig, and Tino Keitel at 25/03/09 06:46 did gyre and gimble:
[...]
> > "RandR" is an abbreviation for "Resize and Rotate".
>
> I think he knew that judging by what he wrote, but yes, randr 1.2/1.3
> can do placement too. Ju
'Twas brillig, and Tino Keitel at 25/03/09 06:46 did gyre and gimble:
> On Tue, Mar 24, 2009 at 17:47:22 -0500, tsuraan wrote:
>>> I assume you use RandR instead of Xinerama.
>> Does RandR do monitor placement as well as the normal Resize and
>> Rotate? I'll have to see if I have it enabled on my
12 matches
Mail list logo
