Mistake, sorry.
Of course this is useless alone.
___
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: https://lists.x.org/mailman/listinfo/xorg-devel
Hi all,
Currently I'm evaluating the suspend/resume speed on my laptop,
and it was found the switching from Graphic Mode to text mode vt has taken more
than 200ms, and according to the ftrace result, after Xorg received
the signal from kernel, it waits for 200ms+ until finally issue the
ioctl
Signed-off-by: Mihail Konev
BugLink: https://github.com/xkbcommon/libxkbcommon/issues/40
---
setxkbmap.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/setxkbmap.c b/setxkbmap.c
index cf0f02d6e704..f5b9f637a136 100644
--- a/setxkbmap.c
+++ b/setxkbmap.c
@@ -50,6 +50,9
On Wed, Nov 16, 2016 at 04:41:55PM +0100, Jens Harms wrote:
> Hello, i created a simple calibration widget to calculate the CTM but
> xinput refused to apply the CTM.
> When i start X without any X Application running and then (over ssh shell)
> type
>
> xinput set-prop 'my touch' 'Coordinate
On Wed, Nov 16, 2016 at 02:18:29PM +0100, Thomas Klausner wrote:
> The release breaks most currently existing graphics driver releases
> and two input driver releases (details below).
yes, a driver released for an older X server is not guaranteed to work with
a newer x server. that's usually
On Wed, Nov 16, 2016 at 02:18:29PM +0100, Thomas Klausner wrote:
> The release breaks most currently existing graphics driver releases
> and two input driver releases (details below).
Most of the drivers are fixed with one of two patches that I found in
some of the repositories (by Adam Jackson),
Hello, i created a simple calibration widget to calculate the CTM but
xinput refused to apply the CTM.
When i start X without any X Application running and then (over ssh shell)
type
xinput set-prop 'my touch' 'Coordinate Transformation Matrix' a b c d e f g
h i
without any error, NOTHING
Am 15.11.2016 22:34, schrieb Ben Crocker:
> In InitOutput, if xf86HandleConfigFile returns CONFIG_NOFILE
> (which it does if no config file or directory is present), the
> autoconfig flag is set, causing xf86AutoConfig to be called
> later on.
>
> xf86AutoConfig calls xf86OutputClassDriverList
The release breaks most currently existing graphics driver releases
and two input driver releases (details below).
What is the proper fix?
When are new releases planned?
Thanks,
Thomas
chips:
ct_driver.c: In function 'chipsBlockHandler':
ct_driver.c:7477:5: error: too many arguments to