Re: [PATCH app/setxkbmap] Add $HOME/.xkb to default search path

2016-11-16 Thread Mihail Konev 
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

[RFC] Why Xorg waits for long time(200ms+) to invoke VT_RELDISP?

2016-11-16 Thread Yu Chen 
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 VT_RELDISP, which makes the kernel blocking at this flag to be
set.
May I know why Xorg takes 200ms+ before acking with VT_RELDISP?
Thanks very much.

More info please refer to:
https://bugzilla.kernel.org/show_bug.cgi?id=186211

thanks,
Yu
___
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

[PATCH app/setxkbmap] Add $HOME/.xkb to default search path

2016-11-16 Thread Mihail Konev 
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 @@
 #ifndef DFLT_XKB_CONFIG_ROOT
 #define DFLT_XKB_CONFIG_ROOT "/usr/share/X11/xkb"
 #endif
+#ifndef DFLT_XKB_CONFIG_HOME
+#define DFLT_XKB_CONFIG_HOME ".xkb"
+#endif
 #ifndef DFLT_XKB_RULES_FILE
 #define DFLT_XKB_RULES_FILE "base"
 #endif
@@ -394,6 +397,12 @@ parseArgs(int argc, char **argv)
 
 ok = True;
 addToList(, ".");
+{
+char *homepath = getenv("HOME");
+char *home_incl_path = malloc(strlen(homepath) + 1 + 
strlen(DFLT_XKB_CONFIG_HOME) + 1);
+sprintf(home_incl_path, "%s/%s", homepath, DFLT_XKB_CONFIG_HOME);
+addToList(, home_incl_path);
+}
 addToList(, DFLT_XKB_CONFIG_ROOT);
 for (i = 1; (i < argc) && ok; i++)
 {
-- 
2.9.2

___
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

Re: calibrate touchscreen

2016-11-16 Thread Peter Hutterer 
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 Transformation Matrix' a b c d e f g
> h i
> 
> without any error, NOTHING happens. no error, no change to the property.
> 
> BUT: when I start X, then aterm and after the aterm window is visible,
> i can succesfully apply the matrix with  "xinput set-prop 'my touch'
> 'Coordinate Transformation Matrix' a b c d e f g h i"
> 
> Is this intended behavior?

probably. By default the X server resets after the last client disconnects
and starts with a vanilla state. Try the -noreset flag to Xorg, or keep one
client connected enough until the rest of the desktop starts.

Cheers,
   Peter

> 
> re,
> Jens Harms
> 
> For the curious, i uploaded the full source:
> 
> git clone https://github.com/xtforever/xtcal.git
> 
> you can add as many calibration points as you wish, the least sqare
> algo will calculate the correct matrix.
> 
> 
> 2016-10-20 7:52 GMT+02:00 Peter Hutterer :
> 
> > On Wed, Oct 19, 2016 at 03:52:56PM +0200, Jens Harms wrote:
> > > Hi. I try to calibrate  a resisitive Touchscreen.
> > > The touchscreen is a bit rotatated (3-5 degree), therefore i can not use
> > > xinput_calibrator. I try to understand how the the evdev driver works.
> > >
> > > Do i need to set "Evdev Axis Calibration" and "Coordinate Transformation
> > > Matrix" ? Or is it sufficent to set the CTM alone?
> >
> > don't use the axis calibration, use the matrix only.
> >
> > > How are Touch coordinates calculated? Which transformations are applied
> > to
> > > the raw data?
> >
> > the matrix is a basic transformation matrix, so you can use your normal
> > rotational elements, etc. The values are normalized to [0, 1] where 1
> > represents "total width" or "total height".
> >
> > https://wiki.archlinux.org/index.php/Calibrating_Touchscreen
> > https://wiki.ubuntu.com/X/InputCoordinateTransformation
> >
> > Cheers,
> >Peter
> >

> ___
> 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

___
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

Re: [ANNOUNCE] xorg-server 1.19.0

2016-11-16 Thread Peter Hutterer 
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 expected, we have to wait for a server
release before we can release the drivers (yes, pre-releases are possible,
but these are not the most interesting drivers).

> What is the proper fix?
> When are new releases planned?

now that we have a server release, we can start releasing the drivers. I'll
be doing the input ones ove the next couple of days.

Cheers,
   Peter



> chips:
> 
> ct_driver.c: In function 'chipsBlockHandler':
> ct_driver.c:7477:5: error: too many arguments to function 
> 'pScreen->BlockHandler'
>  (*pScreen->BlockHandler) (BLOCKHANDLER_ARGS);
>  ^
> 
> i740:
> 
> i740_video.c: In function 'I740BlockHandler':
> i740_video.c:842:3: error: too many arguments to function 
> 'pScreen->BlockHandler'
>(*pScreen->BlockHandler) (BLOCKHANDLER_ARGS);
>^
> 
> qxl:
> 
> uxa-damage.c: In function 'uxa_damage_chars':
> uxa-damage.c:947:5: error: implicit declaration of function 
> 'QueryGlyphExtents' [-Werror=implicit-function-declaration]
>  QueryGlyphExtents(font, charinfo, n, );
>  ^
> 
> r128:
> 
> r128_driver.c:1550:5: error: too many arguments to function 
> 'pScreen->BlockHandler'
>  (*pScreen->BlockHandler) (BLOCKHANDLER_ARGS);
>  ^
> 
> sis:
> 
> sis_driver.c: In function 'SISBlockHandler':
> sis_driver.c:8257:5: error: too many arguments to function 
> 'pScreen->BlockHandler'
>  (*pScreen->BlockHandler) (BLOCKHANDLER_ARGS);
>  ^
> 
> tdfx:
> 
> tdfx_driver.c: In function 'TDFXBlockHandler':
> tdfx_driver.c:2668:5: error: too many arguments to function 
> 'pScreen->BlockHandler'
>  (*pScreen->BlockHandler) (BLOCKHANDLER_ARGS);
>  ^
> 
> amdgpu:
> 
> amdgpu_kms.c:522:2: error: too many arguments to function 
> 'pScreen->BlockHandler'
>   (*pScreen->BlockHandler) (BLOCKHANDLER_ARGS);
>   ^
> 
> glint:
> 
> glint_driver.c:3475:5: error: too many arguments to function 
> 'pScreen->BlockHandler'
>  (*pScreen->BlockHandler) (BLOCKHANDLER_ARGS);
>  ^
> 
> savage:
> 
> savage_dri.c: In function 'SAVAGEWakeupHandler':
> savage_dri.c:277:4: error: too many arguments to function 
> 'psav->pDRIInfo->wrap.WakeupHandler'
> (*psav->pDRIInfo->wrap.WakeupHandler) (WAKEUPHANDLER_ARGS);
> ^
> savage_dri.c: In function 'SAVAGEBlockHandler':
> savage_dri.c:321:4: error: too many arguments to function 
> 'psav->pDRIInfo->wrap.BlockHandler'
> (*psav->pDRIInfo->wrap.BlockHandler) (BLOCKHANDLER_ARGS);
> ^
> 
> xgi:
> 
> xgi_driver.c: In function 'XGIBlockHandler':
> xgi_driver.c:4503:5: error: too many arguments to function 
> 'pScreen->BlockHandler'
>  (*pScreen->BlockHandler) (BLOCKHANDLER_ARGS);
>  ^
> 
> ati:
> 
> radeon_kms.c:612:5: error: too many arguments to function 
> 'pScreen->BlockHandler'
>  (*pScreen->BlockHandler) (BLOCKHANDLER_ARGS);
>  ^
> 
> intel:
> 
> i810_video.c: In function 'I810BlockHandler':
> i810_video.c:1149:5: error: too many arguments to function 
> 'screen->BlockHandler'
>  (*screen->BlockHandler) (BLOCKHANDLER_ARGS);
>  ^
> 
> mga:
> 
> mga_driver.c: In function 'MGABlockHandler':
> mga_driver.c:4024:5: error: too many arguments to function 
> 'pScreen->BlockHandler'
>  (*pScreen->BlockHandler) (BLOCKHANDLER_ARGS);
>  ^
> 
> nv:
> 
> nv_driver.c: In function 'NVBlockHandler':
> nv_driver.c:1181:5: error: too many arguments to function 
> 'pScreen->BlockHandler'
>  (*pScreen->BlockHandler) (BLOCKHANDLER_ARGS);
>  ^
> 
> siliconmotion:
> 
> smi_video.c:2070:5: error: too many arguments to function 
> 'pScreen->BlockHandler'
>  (*pScreen->BlockHandler)(BLOCKHANDLER_ARGS);
>  ^
> 
> trident:
> 
> trident_driver.c: In function 'TRIDENTBlockHandler':
> trident_driver.c:617:5: error: too many arguments to function 
> 'pScreen->BlockHandler'
>  (*pScreen->BlockHandler) (BLOCKHANDLER_ARGS);
>  ^
> 
> 
> input-joystick:
> 
> jstk.c: In function 'jstkReadProc':
> jstk.c:128:17: error: implicit declaration of function 'RemoveEnabledDevice' 
> [-Werror=implicit-function-declaration]
>  RemoveEnabledDevice(pInfo->fd);
>  ^
> jstk.c:128:17: warning: nested extern declaration of 'RemoveEnabledDevice' 
> [-Wnested-externs]
> jstk.c: In function 'jstkDeviceControlProc':
> jstk.c:395:13: error: implicit declaration of function 'AddEnabledDevice' 
> [-Werror=implicit-function-declaration]
>  AddEnabledDevice(pInfo->fd);
>  ^
> 
> 
> input-keyboard:
> 
> kbd.c: In function 'KbdProc':
> kbd.c:386:2: error: implicit declaration of function 'AddEnabledDevice' 
> [-Werror=implicit-function-declaration]
>   AddEnabledDevice(pInfo->fd);
>   ^
> kbd.c:386:2: warning: nested extern declaration of 'AddEnabledDevice' 
> [-Wnested-externs]
>

Re: [ANNOUNCE] xorg-server 1.19.0

2016-11-16 Thread Thomas Klausner 
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), attached.

Not intel nor qxl though. Are releases planned for those?
 Thomas
commit 78d1138dd6e214a200ca66fa9e439ee3c9270ec8
Author: Adam Jackson 
Date:   Tue Jul 19 10:03:56 2016 -0400

Adapt Block/WakeupHandler signature for ABI 23

Signed-off-by: Adam Jackson 

diff --git a/src/compat-api.h b/src/compat-api.h
index 6bc946f..89976e4 100644
--- a/src/compat-api.h
+++ b/src/compat-api.h
@@ -75,8 +75,13 @@
 
 #define SCREEN_INIT_ARGS_DECL ScreenPtr pScreen, int argc, char **argv
 
+#if ABI_VIDEODRV_VERSION >= SET_ABI_VERSION(23, 0)
+#define BLOCKHANDLER_ARGS_DECL ScreenPtr arg, pointer pTimeout
+#define BLOCKHANDLER_ARGS arg, pTimeout
+#else
 #define BLOCKHANDLER_ARGS_DECL ScreenPtr arg, pointer pTimeout, pointer 
pReadmask
 #define BLOCKHANDLER_ARGS arg, pTimeout, pReadmask
+#endif
 
 #define CLOSE_SCREEN_ARGS_DECL ScreenPtr pScreen
 #define CLOSE_SCREEN_ARGS pScreen
commit b99390efcb55d7d4a68e8c595119c1af4426fc0b
Author: Adam Jackson 
Date:   Tue Jul 19 10:03:56 2016 -0400

Adapt Block/WakeupHandler signature for ABI 23

Signed-off-by: Adam Jackson 

diff --git a/src/compat-api.h b/src/compat-api.h
index 98ba435..44daea4 100644
--- a/src/compat-api.h
+++ b/src/compat-api.h
@@ -78,11 +78,19 @@
 
 #define SCREEN_INIT_ARGS_DECL ScreenPtr pScreen, int argc, char **argv
 
+#if ABI_VIDEODRV_VERSION >= SET_ABI_VERSION(23, 0)
+#define BLOCKHANDLER_ARGS_DECL ScreenPtr arg, pointer pTimeout
+#define BLOCKHANDLER_ARGS arg, pTimeout
+
+#define WAKEUPHANDLER_ARGS_DECL ScreenPtr arg, unsigned long result
+#define WAKEUPHANDLER_ARGS arg, result
+#else
 #define BLOCKHANDLER_ARGS_DECL ScreenPtr arg, pointer pTimeout, pointer 
pReadmask
 #define BLOCKHANDLER_ARGS arg, pTimeout, pReadmask
 
 #define WAKEUPHANDLER_ARGS_DECL ScreenPtr arg, unsigned long result, pointer 
read_mask
 #define WAKEUPHANDLER_ARGS arg, result, read_mask
+#endif
 
 #define CLOSE_SCREEN_ARGS_DECL ScreenPtr pScreen
 #define CLOSE_SCREEN_ARGS pScreen
___
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

Re: calibrate touchscreen

2016-11-16 Thread Jens Harms 
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 happens. no error, no change to the property.

BUT: when I start X, then aterm and after the aterm window is visible,
i can succesfully apply the matrix with  "xinput set-prop 'my touch'
'Coordinate Transformation Matrix' a b c d e f g h i"

Is this intended behavior?

re,
Jens Harms

For the curious, i uploaded the full source:

git clone https://github.com/xtforever/xtcal.git

you can add as many calibration points as you wish, the least sqare
algo will calculate the correct matrix.


2016-10-20 7:52 GMT+02:00 Peter Hutterer :

> On Wed, Oct 19, 2016 at 03:52:56PM +0200, Jens Harms wrote:
> > Hi. I try to calibrate  a resisitive Touchscreen.
> > The touchscreen is a bit rotatated (3-5 degree), therefore i can not use
> > xinput_calibrator. I try to understand how the the evdev driver works.
> >
> > Do i need to set "Evdev Axis Calibration" and "Coordinate Transformation
> > Matrix" ? Or is it sufficent to set the CTM alone?
>
> don't use the axis calibration, use the matrix only.
>
> > How are Touch coordinates calculated? Which transformations are applied
> to
> > the raw data?
>
> the matrix is a basic transformation matrix, so you can use your normal
> rotational elements, etc. The values are normalized to [0, 1] where 1
> represents "total width" or "total height".
>
> https://wiki.archlinux.org/index.php/Calibrating_Touchscreen
> https://wiki.ubuntu.com/X/InputCoordinateTransformation
>
> Cheers,
>Peter
>
___
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

Re: [PATCH xserver] Fix a segfault that occurs if xorg.conf.d is absent:

2016-11-16 Thread walter harms 


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 via the
> call tree:
> 
> xf86AutoConfig =>
>   listPossibleVideoDrivers =>
> xf86PlatformMatchDriver =>
>   xf86OutputClassDriverList
> 
> and xf86OutputClassDriverList attempts to traverse a linked list
> that is a member of the XF86ConfigRec struct pointed to by the
> global xf86configptr, which is NULL at this point because the
> XF86ConfigRec struct is only allocated (by xf86readConfigFile)
> AFTER the config file and directory have been successfully
> opened; the CONFIG_NOFILE return from xf86HandleConfigFile
> occurs BEFORE the call to xf86readConfigFile which allocates
> the XF86ConfigRec struct.
> 
> Rx: In read.c (for symmetry with xf86freeConfig, which already
> appears in this file), add a new function xf86allocateConfig
> which tests the value of xf86configptr and, if it's NULL,
> allocates the XF86ConfigRec struct and deposits the pointer
> in xf86configptr.  In xf86Parser.h, add a prototype for the
> new xf86allocateConfig function.
> 
> Back in read.c, #include "xf86Config.h".  In xf86readConfigFile,
> change the open-code call to calloc to a call to the new
> xf86allocateConfig function.
> 
> In xf86AutoConfig.c, add a call to the new xf86allocateConfig function
> to the beginning of xf86AutoConfig to make sure the XF86ConfigRec struct
> is allocated.
> 
> Signed-off-by: Ben Crocker 
> ---
>  hw/xfree86/common/xf86AutoConfig.c |  9 +
>  hw/xfree86/parser/read.c   | 16 +++-
>  hw/xfree86/parser/xf86Parser.h |  1 +
>  3 files changed, 25 insertions(+), 1 deletion(-)
> 
> diff --git a/hw/xfree86/common/xf86AutoConfig.c 
> b/hw/xfree86/common/xf86AutoConfig.c
> index 9402651..c3e17be 100644
> --- a/hw/xfree86/common/xf86AutoConfig.c
> +++ b/hw/xfree86/common/xf86AutoConfig.c
> @@ -149,6 +149,15 @@ xf86AutoConfig(void)
>  char buf[1024];
>  ConfigStatus ret;
>  
> +/* Make sure config rec is there */
> +if (xf86allocateConfig() != NULL) {
> +ret = CONFIG_OK;/* OK so far */
> +}
> +else {
> +xf86Msg(X_ERROR, "Couldn't allocate Config record.\n");
> +return FALSE;
> +}
> +


you can simplify with:

ret = CONFIG_OK;
if ( ! xf86allocateConfig() )
 {
   xf86Msg(X_ERROR, "Couldn't allocate Config record.\n");
return FALSE;
  }

you do not need to store the return value ?


>  listPossibleVideoDrivers(deviceList, 20);
>  
>  for (p = deviceList; *p; p++) {
> diff --git a/hw/xfree86/parser/read.c b/hw/xfree86/parser/read.c
> index ec038ae..d7e7312 100644
> --- a/hw/xfree86/parser/read.c
> +++ b/hw/xfree86/parser/read.c
> @@ -56,6 +56,7 @@
>  #include 
>  #endif
>  
> +#include "xf86Config.h"
>  #include "xf86Parser.h"
>  #include "xf86tokens.h"
>  #include "Configint.h"
> @@ -91,7 +92,7 @@ xf86readConfigFile(void)
>  int token;
>  XF86ConfigPtr ptr = NULL;
>  
> -if ((ptr = calloc(1, sizeof(XF86ConfigRec))) == NULL) {
> +if ((ptr = xf86allocateConfig()) == NULL) {
>  return NULL;
>  }
To improve readability:

XF86ConfigPtr ptr;

ptr=xf86allocateConfig();

if (!ptr)
 return NULL;


just my 2 cents,

re
 wh
>  
> @@ -270,6 +271,19 @@ xf86itemNotSublist(GenericListPtr list_1, GenericListPtr 
> list_2)
>  return (!(last_1 == last_2));
>  }
>  
> +/*
> + * Conditionally allocate config struct, but only allocate it
> + * if it's not already there.  In either event, return the pointer
> + * to the global config struct.
> + */
> +XF86ConfigPtr xf86allocateConfig(void)
> +{
> +if (!xf86configptr) {
> +xf86configptr = calloc(1, sizeof(XF86ConfigRec));
> +}
> +return xf86configptr;
> +}
> +
>  void
>  xf86freeConfig(XF86ConfigPtr p)
>  {
> diff --git a/hw/xfree86/parser/xf86Parser.h b/hw/xfree86/parser/xf86Parser.h
> index ff35846..9c4b403 100644
> --- a/hw/xfree86/parser/xf86Parser.h
> +++ b/hw/xfree86/parser/xf86Parser.h
> @@ -449,6 +449,7 @@ extern char *xf86openConfigDirFiles(const char *path, 
> const char *cmdline,
>  extern void xf86setBuiltinConfig(const char *config[]);
>  extern XF86ConfigPtr xf86readConfigFile(void);
>  extern void xf86closeConfigFile(void);
> +extern XF86ConfigPtr xf86allocateConfig(void);
>  extern void xf86freeConfig(XF86ConfigPtr p);
>  extern int xf86writeConfigFile(const char *, XF86ConfigPtr);
>  extern _X_EXPORT XF86ConfDevicePtr xf86findDevice(const char *ident,
___
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

Re: [ANNOUNCE] xorg-server 1.19.0

2016-11-16 Thread Thomas Klausner 
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 function 
'pScreen->BlockHandler'
 (*pScreen->BlockHandler) (BLOCKHANDLER_ARGS);
 ^

i740:

i740_video.c: In function 'I740BlockHandler':
i740_video.c:842:3: error: too many arguments to function 
'pScreen->BlockHandler'
   (*pScreen->BlockHandler) (BLOCKHANDLER_ARGS);
   ^

qxl:

uxa-damage.c: In function 'uxa_damage_chars':
uxa-damage.c:947:5: error: implicit declaration of function 'QueryGlyphExtents' 
[-Werror=implicit-function-declaration]
 QueryGlyphExtents(font, charinfo, n, );
 ^

r128:

r128_driver.c:1550:5: error: too many arguments to function 
'pScreen->BlockHandler'
 (*pScreen->BlockHandler) (BLOCKHANDLER_ARGS);
 ^

sis:

sis_driver.c: In function 'SISBlockHandler':
sis_driver.c:8257:5: error: too many arguments to function 
'pScreen->BlockHandler'
 (*pScreen->BlockHandler) (BLOCKHANDLER_ARGS);
 ^

tdfx:

tdfx_driver.c: In function 'TDFXBlockHandler':
tdfx_driver.c:2668:5: error: too many arguments to function 
'pScreen->BlockHandler'
 (*pScreen->BlockHandler) (BLOCKHANDLER_ARGS);
 ^

amdgpu:

amdgpu_kms.c:522:2: error: too many arguments to function 
'pScreen->BlockHandler'
  (*pScreen->BlockHandler) (BLOCKHANDLER_ARGS);
  ^

glint:

glint_driver.c:3475:5: error: too many arguments to function 
'pScreen->BlockHandler'
 (*pScreen->BlockHandler) (BLOCKHANDLER_ARGS);
 ^

savage:

savage_dri.c: In function 'SAVAGEWakeupHandler':
savage_dri.c:277:4: error: too many arguments to function 
'psav->pDRIInfo->wrap.WakeupHandler'
(*psav->pDRIInfo->wrap.WakeupHandler) (WAKEUPHANDLER_ARGS);
^
savage_dri.c: In function 'SAVAGEBlockHandler':
savage_dri.c:321:4: error: too many arguments to function 
'psav->pDRIInfo->wrap.BlockHandler'
(*psav->pDRIInfo->wrap.BlockHandler) (BLOCKHANDLER_ARGS);
^

xgi:

xgi_driver.c: In function 'XGIBlockHandler':
xgi_driver.c:4503:5: error: too many arguments to function 
'pScreen->BlockHandler'
 (*pScreen->BlockHandler) (BLOCKHANDLER_ARGS);
 ^

ati:

radeon_kms.c:612:5: error: too many arguments to function 
'pScreen->BlockHandler'
 (*pScreen->BlockHandler) (BLOCKHANDLER_ARGS);
 ^

intel:

i810_video.c: In function 'I810BlockHandler':
i810_video.c:1149:5: error: too many arguments to function 
'screen->BlockHandler'
 (*screen->BlockHandler) (BLOCKHANDLER_ARGS);
 ^

mga:

mga_driver.c: In function 'MGABlockHandler':
mga_driver.c:4024:5: error: too many arguments to function 
'pScreen->BlockHandler'
 (*pScreen->BlockHandler) (BLOCKHANDLER_ARGS);
 ^

nv:

nv_driver.c: In function 'NVBlockHandler':
nv_driver.c:1181:5: error: too many arguments to function 
'pScreen->BlockHandler'
 (*pScreen->BlockHandler) (BLOCKHANDLER_ARGS);
 ^

siliconmotion:

smi_video.c:2070:5: error: too many arguments to function 
'pScreen->BlockHandler'
 (*pScreen->BlockHandler)(BLOCKHANDLER_ARGS);
 ^

trident:

trident_driver.c: In function 'TRIDENTBlockHandler':
trident_driver.c:617:5: error: too many arguments to function 
'pScreen->BlockHandler'
 (*pScreen->BlockHandler) (BLOCKHANDLER_ARGS);
 ^


input-joystick:

jstk.c: In function 'jstkReadProc':
jstk.c:128:17: error: implicit declaration of function 'RemoveEnabledDevice' 
[-Werror=implicit-function-declaration]
 RemoveEnabledDevice(pInfo->fd);
 ^
jstk.c:128:17: warning: nested extern declaration of 'RemoveEnabledDevice' 
[-Wnested-externs]
jstk.c: In function 'jstkDeviceControlProc':
jstk.c:395:13: error: implicit declaration of function 'AddEnabledDevice' 
[-Werror=implicit-function-declaration]
 AddEnabledDevice(pInfo->fd);
 ^


input-keyboard:

kbd.c: In function 'KbdProc':
kbd.c:386:2: error: implicit declaration of function 'AddEnabledDevice' 
[-Werror=implicit-function-declaration]
  AddEnabledDevice(pInfo->fd);
  ^
kbd.c:386:2: warning: nested extern declaration of 'AddEnabledDevice' 
[-Wnested-externs]
kbd.c:400:7: error: implicit declaration of function 'RemoveEnabledDevice' 
[-Werror=implicit-function-declaration]
   RemoveEnabledDevice(pInfo->fd);
   ^


- End forwarded message -
___
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