umm, Adrian Cox ([EMAIL PROTECTED]) did some work on a multihead 69030
driver for my company a while back . I dont know if it ever got integarted into
the main tree, and AFAIK it may only work with our custom board ;-), but its
worth asking him about.
Yours,
Rob Taylor
-Original Message
I though i should point out that you already have a volunteer to set up a bug
database: Kurt Wall ( see
http://www.xfree86.org/pipermail/xpert/2002-May/017211.html ).
Yours,
Rob Taylor
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf
Of Mike A. Harris
This is all very well, but i sent patches to [EMAIL PROTECTED] nearly 3 weeks
ago and i've had nothing back apart from an automatic response! does *ANYONE*
read it?
Yours
Rob Taylor
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf
Of Dr Andrew C
I've seen bugs like this in the matrox drivers before. As i recall its a bug in
handling caching bitmaps in video memory (the cached bitmap is only accessible
to one of the pipes). try a newer matrox driver (from their site) if no luck
mail a bug report to matrox.
Rob
-Original
Even if you don't want the functionality of being able to touch both
touchscreens at once theres a bug in xfree86 to do with shifting the focus
between screens on single presses ( the current shifing code assumes that i'll
be able to ignore a move and go one round the main internal event loop
here's a context patch to make the default background black (i'm workinng on an
embedded device and the flash of moire was just too messy ;)
Rob
--- xc/programs/Xserver/dix/window.cMon Jan 28 15:45:50 2002
+++ xc.orig/programs/Xserver/dix/window.c Wed Jan 17 22:36:44 2001
@@ -114,12
of XNextEvent.
Has anyone got any ideas why this isn't working? Could it be a window manger
issue?
Thanks to anyone who can help, this has me completely bamboozled!
Rob Taylor
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo
