Re: Current tinderbox regression (xserver)
On Mon, Sep 14, 2009 at 07:56:51AM +0200, Werner LEMBERG wrote: http://tinderbox.x.org/builds/2009-09-13-/logs/xserver/#build In file included from dmx.c:61: /home/cjb/xorg-build/include/X11/extensions/dmxext.h:69: error: expected specifier-qualifier-list before 'XRectangle' Fixed, sorry about that. http://cgit.freedesktop.org/xorg/xserver/commit/?id=e85775aa64d1e9322c82090a26256af5e1fede0a Are such fixes reflected in the supermodule? How do I update properly? The 7.5 supermodule is on .900 which doesn't have the dmx fixes in yet. Best is to wait for RC1 if you want it done automatically. However, note that the supermodule simple records the commit of the submodules, nothing else. So you can simply go into xserver and run git pull (switch to the master branch first though). next time you run git submodule update it'll set you back onto the recorded commit. Cheers, Peter ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: getting XI error codes - implicit declaration issue
On Fri, Sep 11, 2009 at 04:19:46PM +0200, Christian Beier wrote:
Hi there,
there seems to be a little issue with the way one registers for XInput
error codes: if i'm not totally wrong, these are defined nowhere, but
dynamically generated and one has to get the actual values via macros
like BadDevice(). But: (at least with git master xorg) this one
evaluates to _xibaddevice(), defined in libXi/src/XExtInt.c, which in
turn seems to be a private symbol in libxi, as i get 'implicit
declaration of function _xibaddevice' warnings while compiling my app.
while it seems to work okay, shouldn the _xibaddevice declaration made
public or the macro be turned into a function?
something like this should do?
From 570af989a542621e94ca756a9bee09f4f04586cc Mon Sep 17 00:00:00 2001
From: Peter Hutterer peter.hutte...@who-t.net
Date: Mon, 14 Sep 2009 16:34:18 +1000
Subject: [PATCH] Declare _xibad* functions before the Bad* macros.
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
include/X11/extensions/XInput.h |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/include/X11/extensions/XInput.h b/include/X11/extensions/XInput.h
index 561465c..b17f388 100644
--- a/include/X11/extensions/XInput.h
+++ b/include/X11/extensions/XInput.h
@@ -159,6 +159,11 @@ SOFTWARE.
extern C {
#endif
extern int _XiGetDevicePresenceNotifyEvent(Display *);
+extern void _xibaddevice( Display *dpy, int *error);
+extern void _xibadclass( Display *dpy, int *error);
+extern void _xibadevent( Display *dpy, int *error);
+extern void _xibadmode( Display *dpy, int *error);
+extern void _xidevicebusy( Display *dpy, int *error);
#if defined(__cplusplus) || defined(c_plusplus)
}
#endif
--
1.6.3.rc1.2.g0164.dirty
Cheers,
Peter
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
Re: LeftOf in monitor section is not completely honored
Dnia poniedziałek, 14 września 2009, Csillag Kristof napisał: [...] Am I doing something wrong? (I have attached the xorg.conf.) Or is this a bug? Since it can be worked around by executing xrandr manually, this is not as bad as the twitching image problem, or the random pixels problem, or the lack of support for the 3rd and 4th head of the FireMV 2400, but still, it is annoying. I've read a part of your xorg.conf and I think that you should try to rename the identifiers of yout monitor secions to DVI-0 and DVI-1 respectively. -- Łukasz Maśko GG: 2441498_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające Nie umiem zainstalować Debiana ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Issues with X Server Compilation on Virtual box
We are undergraduate students trying to install X Server on virtual box. We have installed all required packages. After running the startx command, we got the following error in the log: (++) Using config file: /etc/X11/xorg.conf dlopen: /opt/MPX//lib/xorg/modules/drivers/vboxvideo_drv.so: undefined symbol: resVgaShared (EE) Failed to load /opt/MPX//lib/xorg/modules/drivers/vboxvideo_drv.so (EE) Failed to load module vboxvideo (loader failed, 7) (EE) No drivers available. Fatal server error: no screens found To get the vboxvideo driver, we also compiled virtualbox and did a symbolic link to the certain .so drivers... But it din't help. I'll be obliged with any help on this. Thanks. -- Take care and Keep caring, Pratik :) ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Issues with X Server Compilation on Virtual box
Hi, On Mon, Sep 14, 2009 at 12:11:23PM +0200, ext mrinal nargunde wrote: We are undergraduate students trying to install X Server on virtual box. We have installed all required packages. After running the startx command, we got the following error in the log: (++) Using config file: /etc/X11/xorg.conf dlopen: /opt/MPX//lib/xorg/modules/drivers/vboxvideo_drv.so: undefined symbol: resVgaShared (EE) Failed to load /opt/MPX//lib/xorg/modules/drivers/vboxvideo_drv.so (EE) Failed to load module vboxvideo (loader failed, 7) (EE) No drivers available. Fatal server error: no screens found To get the vboxvideo driver, we also compiled virtualbox and did a symbolic link to the certain .so drivers... But it din't help. Your vboxvideo driver is not aware already about the removal of RAC, that we've done recently. Where are the sources of the driver (and is there some reason for the driver doesn't live on freedesktop.org?)? It's pretty easy to fix this issue. Tiago ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
[ANNOUNCE] xorg-server 1.6.99.901 (1.7 RC1)
The first release candidate for the X.Org X Server 1.7 is now available. This means the server ABI is now frozen. A number of fixes went in since the snapshot. A set of patches resurrected Xdmx which now builds again. More patches will follow to make it work better, right now it's still a bit flaky. Other patches are all over the place, fixing various bugs in number of subsystems. Many thanks to all contributors. Currently we have 7 bugs on the 1.7 tracker bug: [http://bugs.freedesktop.org/showdependencytree.cgi?id=23613hide_resolved=1] 13932: pointer cannot move across screens in zaphod mode 16509: Leak in xf86XVDestroyWindow 19470: any X11 client can crash Xvfb 20500: Record extension not sending event 23286: Memory leak caused by 100x100 glyphs 23705: xserver 1.7.0rc0 uses wrong dimensions 23755: X does not work on Alpha Pick your favourite and fix it. Alternatively, test this release and report bugs so we can work towards a stable final release. If you have patches to propose for 1.7 please send them to xorg-devel for public review. GIT MASTER IS STILL FROZEN. DO NOT COMMIT. No-one has proposed any larger features that need to go in immediately, so I'm taking advantage of it to make my life easier and save me cherry-picking. If you have a large feature that needs to go into master immediately, let me know and we will branch off. Expect at least one more release candidate before the final server release. Cheers, Peter Alan Coopersmith (3): compiler.h: include string.h before using memmove() xfree86: Change default font path to match configure.ac's --default-font-path. Update xorg.conf man page sample for changes in Xorg 1.7 Daniel Stone (1): fbdevhw: Test for graphics:fb%d as well as graphics/fb%d Eamon Walsh (1): Fix warning: left-hand operand of comma expression has no effect Jeremy Huddleston (6): XQuartz: Use --with-launchd-id-prefix for consistency with xinit XQuartz: Check the DISPLAY environment variable to see if the socket at startup is ours. If not, ignore it and fork/exec startx. XQuartz: Fix a strcpy/strcmp typo XQuartz: pbproxy: 64bit fixes: Properly process an array of Atoms XQuartz: Fix warning: function declaration isn’t a prototype noise XQuartz: launchd: Fallback on :0 if prefix:0 gives an error for the socket name Kevin E Martin (2): dmx: Make description match default option. Include X11/extensions/dmx.h and remove _DMX_SERVER_ define. Martin-Éric Racine (2): Added comment with the PCI device ID of Geode SCx200 series. Use lowercase PCI vendor ID for NSC. Michel Dänzer (2): EXA: Stop hiding solid or gradient pictures from the driver. EXA: Only take special code path for 1x1 fill for pixmaps. Peter Hutterer (32): dix: remove dixLookupResource - we don't have any users left. dix: GetKeyboardValuatorEvents doesn't recurse anymore - fix comment. kdrive: remove xkb member from KdKeyboardInfo dix: remove unused and half-broken code to restore original classes. kdrive: fix sdl build by removing old keySymsRec references. dix: auto-float SD's with SendCoreEvents false Xnest: set the default pointer accel to the host's values (#10013) kdrive: output meaningful error message for HAL devices. xfree86: remove now unused xf86CrtcShadowClear dix: Remove two _X_EXPORT defines from the function definition. Xext: don't try to initialize XTEST device properties if they failed. xkb: split effectiveGroup calculation into separate utility function. dmx: include xkbsrv.h to silence compiler. dmx: switch lnx-input and usb-input over to xkb-only. dmx: XkbComponentNamesRec doesn't have a keymap field anymore. dmx: fix two calls to InitKeyboardDeviceStruct. dmx: fix up dmxKeyCodeToKeySym for XKB-only. dmx: fix dmxKeySymToKeyCode to work with mandatory XKB. dmx: get the state from XKB for dmxCheckSpecialKeys dmx: compiler warning fix (mixed declarations + code) dmx: remove dmx-internal event queue. dmx: include xfixes lib, reshuffle include order to resolve linker errors. dmx: Default rules are now base, not xfree86 dmx: formatting fix to improve readability dmx: purge DMX EQ leftovers dmx: Remove some dead code. configure: re-enable dmx build (default=auto) dix: FindChildForEvent needs init child to None. xfree86: fix VT_WAITACTIVE control flow (#11477) xkb: drop key presses for already repeating keys. (#23889) dmx: use top_builddir, not top_srcdir to get libxfixes.la xserver 1.6.99.901 (xserver 1.7 RC1) Soeren Sandmann (1): Add xoff and yoff to drawable-x and drawable-y in create_bits_picture(). Tiago Vignatti (3): xfree86: vgaarb: close and cleanup vga arbiter Revert Make sys.c use compiler.h unaligned access functions shave: use CC tag
exa/nouveau segfault
Hello, I use xorg-server/xf86-video-nouveau/nouveau-drm/mesa/libdrm et.al. from git.freedesktop.org. [A 2-3 days update solved the trouble with console switching, always restarting Xorg/gdm. Great relief.] Since 1-2 weeks ago I keep getting this segfault whenever launching windows except x11vnc/xterm/mplayer. Also using gtk+/glib from git.gnome.org. Backtrace: 0: /usr/bin/Xorg (xorg_backtrace+0x28) [0x46b5a8] 1: /usr/bin/Xorg (0x40+0x76e65) [0x476e65] 2: /lib/libpthread.so.0 (0x7fc0aeb23000+0xed40) [0x7fc0aeb31d40] 3: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7fc0abbde000+0x4552b) [0x7fc0abc2352b] 4: /usr/lib/xorg/modules/libexa.so (0x7fc0aa155000+0xf02c) [0x7fc0aa16402c] 5: /usr/lib/xorg/modules/libexa.so (0x7fc0aa155000+0xfe4d) [0x7fc0aa164e4d] 6: /usr/bin/Xorg (0x40+0xdec9d) [0x4dec9d] 7: /usr/bin/Xorg (0x40+0xd178e) [0x4d178e] 8: /usr/bin/Xorg (0x40+0x37954) [0x437954] 9: /usr/bin/Xorg (0x40+0x24f5a) [0x424f5a] 10: /lib/libc.so.6 (__libc_start_main+0xe6) [0x7fc0ad753a26] 11: /usr/bin/Xorg (0x40+0x24b19) [0x424b19] Segmentation fault at address 0xc Fatal server error: Caught signal 11 (Segmentation fault). Server aborting --- Thanks for any help, S. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: exa/nouveau segfault
On Mon, Sep 14, 2009 at 12:27 PM, Sebastian Glita gls...@yahoo.com wrote: Hello, I use xorg-server/xf86-video-nouveau/nouveau-drm/mesa/libdrm et.al. from git.freedesktop.org. [A 2-3 days update solved the trouble with console switching, always restarting Xorg/gdm. Great relief.] Since 1-2 weeks ago I keep getting this segfault whenever launching windows except x11vnc/xterm/mplayer. Also using gtk+/glib from git.gnome.org. Backtrace: 0: /usr/bin/Xorg (xorg_backtrace+0x28) [0x46b5a8] 1: /usr/bin/Xorg (0x40+0x76e65) [0x476e65] 2: /lib/libpthread.so.0 (0x7fc0aeb23000+0xed40) [0x7fc0aeb31d40] 3: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7fc0abbde000+0x4552b) [0x7fc0abc2352b] 4: /usr/lib/xorg/modules/libexa.so (0x7fc0aa155000+0xf02c) [0x7fc0aa16402c] 5: /usr/lib/xorg/modules/libexa.so (0x7fc0aa155000+0xfe4d) [0x7fc0aa164e4d] 6: /usr/bin/Xorg (0x40+0xdec9d) [0x4dec9d] 7: /usr/bin/Xorg (0x40+0xd178e) [0x4d178e] 8: /usr/bin/Xorg (0x40+0x37954) [0x437954] 9: /usr/bin/Xorg (0x40+0x24f5a) [0x424f5a] 10: /lib/libc.so.6 (__libc_start_main+0xe6) [0x7fc0ad753a26] 11: /usr/bin/Xorg (0x40+0x24b19) [0x424b19] Segmentation fault at address 0xc Fatal server error: Caught signal 11 (Segmentation fault). Server aborting --- Thanks for any help, S. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg A proper backtrace made with gdb would help, some debug symbols would be useful too, at least for nouveau. Maarten. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: xinerama/xrandr
According to Nvidia's driver readme guide, they support rotation with Xrandr. The driver supports rotation with the extension when 'Option RandRRotation' is enabled in the X config file. Perhaps, they do not support all of the abilities of the new Xrandr... such as virtual screen size or spanning multiple displays. At this point, my goal (tomorrow) will be to set all 3 screens on separate X screens and apply the rotation through Xrandr. Allowing for 3 separate desktops that are compositable. I think that's as close as the current code will allow me to get. FWIW you only need xrandr to do on-the-fly rotation changes. I have two monitors set up as two X11 screens on a single nVidia GPU, one is normal and the other is rotated 90 degrees to portrait mode, and I don't use xrandr. I run compiz-fusion 3D accelerated on both screens. I can't recall whether this is compatible with TwinView/Xinerama to create a combined desktop though. All I had to do was add this to xorg.conf: Section Screen ... Option Rotate left EndSection I have disabled DynamicTwinView in the Device section though, which I think disables xrandr. I think it may have been required for this to work, but I can't remember for certain now. Good luck! Cheers, Adam. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: getting XI error codes - implicit declaration issue
On Mon, 14 Sep 2009 16:35:42 +1000
Peter Hutterer peter.hutte...@who-t.net wrote:
On Fri, Sep 11, 2009 at 04:19:46PM +0200, Christian Beier wrote:
Hi there,
there seems to be a little issue with the way one registers for XInput
error codes: if i'm not totally wrong, these are defined nowhere, but
dynamically generated and one has to get the actual values via macros
like BadDevice(). But: (at least with git master xorg) this one
evaluates to _xibaddevice(), defined in libXi/src/XExtInt.c, which in
turn seems to be a private symbol in libxi, as i get 'implicit
declaration of function _xibaddevice' warnings while compiling my app.
while it seems to work okay, shouldn the _xibaddevice declaration made
public or the macro be turned into a function?
something like this should do?
yep, it does.
cheers,
christian
From 570af989a542621e94ca756a9bee09f4f04586cc Mon Sep 17 00:00:00 2001
From: Peter Hutterer peter.hutte...@who-t.net
Date: Mon, 14 Sep 2009 16:34:18 +1000
Subject: [PATCH] Declare _xibad* functions before the Bad* macros.
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
include/X11/extensions/XInput.h |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/include/X11/extensions/XInput.h b/include/X11/extensions/XInput.h
index 561465c..b17f388 100644
--- a/include/X11/extensions/XInput.h
+++ b/include/X11/extensions/XInput.h
@@ -159,6 +159,11 @@ SOFTWARE.
extern C {
#endif
extern int _XiGetDevicePresenceNotifyEvent(Display *);
+extern void _xibaddevice( Display *dpy, int *error);
+extern void _xibadclass( Display *dpy, int *error);
+extern void _xibadevent( Display *dpy, int *error);
+extern void _xibadmode( Display *dpy, int *error);
+extern void _xidevicebusy( Display *dpy, int *error);
#if defined(__cplusplus) || defined(c_plusplus)
}
#endif
--
1.6.3.rc1.2.g0164.dirty
Cheers,
Peter
--
what is, is;
what is not is possible.
signature.asc
Description: PGP signature
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
Re: getting XI error codes - implicit declaration issue
On Mon, Sep 14, 2009 at 02:26:26PM +0200, Christian Beier wrote:
On Mon, 14 Sep 2009 16:35:42 +1000
Peter Hutterer peter.hutte...@who-t.net wrote:
On Fri, Sep 11, 2009 at 04:19:46PM +0200, Christian Beier wrote:
Hi there,
there seems to be a little issue with the way one registers for XInput
error codes: if i'm not totally wrong, these are defined nowhere, but
dynamically generated and one has to get the actual values via macros
like BadDevice(). But: (at least with git master xorg) this one
evaluates to _xibaddevice(), defined in libXi/src/XExtInt.c, which in
turn seems to be a private symbol in libxi, as i get 'implicit
declaration of function _xibaddevice' warnings while compiling my app.
while it seems to work okay, shouldn the _xibaddevice declaration made
public or the macro be turned into a function?
something like this should do?
yep, it does.
pushed, thanks for testing.
Cheers,
Peter
From 570af989a542621e94ca756a9bee09f4f04586cc Mon Sep 17 00:00:00 2001
From: Peter Hutterer peter.hutte...@who-t.net
Date: Mon, 14 Sep 2009 16:34:18 +1000
Subject: [PATCH] Declare _xibad* functions before the Bad* macros.
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
include/X11/extensions/XInput.h |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/include/X11/extensions/XInput.h
b/include/X11/extensions/XInput.h
index 561465c..b17f388 100644
--- a/include/X11/extensions/XInput.h
+++ b/include/X11/extensions/XInput.h
@@ -159,6 +159,11 @@ SOFTWARE.
extern C {
#endif
extern int _XiGetDevicePresenceNotifyEvent(Display *);
+extern void _xibaddevice( Display *dpy, int *error);
+extern void _xibadclass( Display *dpy, int *error);
+extern void _xibadevent( Display *dpy, int *error);
+extern void _xibadmode( Display *dpy, int *error);
+extern void _xidevicebusy( Display *dpy, int *error);
#if defined(__cplusplus) || defined(c_plusplus)
}
#endif
--
1.6.3.rc1.2.g0164.dirty
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
Re: twitching image
On Sun, Sep 13, 2009 at 9:27 PM, Csillag Kristofcsillag.kris...@united-consult.hu wrote: Alex Deucher wrote: This is likely display watermark or pll related. What is a display watermark? All of the memory clients on the GPU (display controllers, 2D, 3D, overlays, etc.) contend for memory bandwidth from the memory controller. If the display controllers are starved, you end up with underflow which can manifest as sparkling or blanking of the display at certain times. To avoid this, you need to properly set up the display fifos and priority levels. This tends to be more evident on DVI since the signal is digital. Also, IGP chips are more prone to watermark problems since they are sharing memory bandwidth with the rest of the system. Please try xf86-video-ati from git master as that has proper watermark setup implemented and support for fractional feedback dividers. I will do this tomorrow; just one question until then: if this has anything to do with the driver, then how is it possible that the frequency of the problem can be influenced by changing the DVI cabling I use? low quality DVI cables can causes problems, but if the same cable works on other systems, it's probably driver related. If you are still having problems with master, please try: Option DisplayPriority HIGH in the device section of your config. I have already tried that, and it did not help. You need git master. Alex ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: xinerama/xrandr
On 09/14/2009 09:31 AM, Tippett, Matthew wrote: Hi. I'll talk about the generic RANDR and Xinerama situation. I'll leave other domain experts fill in any NV specifics. RANDR currently allows both static and dynamic configuration of position and rotation for 'individual' head mode. This doesn't matter how many GPUs or heads you have. You don't have the 'unified desktop' experience and can't move the windows between heads. If you have a randr capable setup and only one head (multiple outputs) per GPU, you can have a '2+1' config. For Xinerama mode, you can statically configure randr modes through xorg.conf. The randr extension is turned off when xinerama is enabled. So it really depends what you want to do. If your intent is to use one screen with near static (and immovable content) like a mailer or something similar, the non-xinerama mode may do what you need. Although there has historically been talk of deprecating Xinerama, it is currently the only way to configure multiple cards into a single desktop. If you checkout the recent phoronix articles, you can see that 24 displays are possible. (The video is 4 head with static randr without xinerama, but the same as a single head with static randr xinerama can achieve the same thing). Regards... Matthew That actually helps greatly, it's pretty much what I've been figuring out through trial and error - but it helps to hear it outright. I've noticed there seems to be no word on when Xinerama will be deprecated and what will replace that functionality. I guess it's something I'll have to keep an eye on... Thanks again Daniel ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Issues with X Server Compilation on Virtual box
What operating system are you running in Virtual Box? mrinal nargunde wrote: We are undergraduate students trying to install X Server on virtual box. We have installed all required packages. After running the startx command, we got the following error in the log: ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: generic touchscreen calibration
Søren Hauberg wrote: Hi, 2009/9/10 Tias t...@ulyssis.org: In the end, I had to hack up the ancient tkxinput because it was the only device independent calibrator (it uses Xinput to read the coordinates). On the other hand, I was impressed by the simplicity of the calibrator that Soren Hauberg sent to this list in july (thread titled 'Evdev touchscreen calibration?'), although it was written for usbtouchscreen driven devices specifically. I figured that a generic calibration program should be device independent when reading calibration data, and device dependent in how to use the data. I've adapted Soren's calibrator to do exactly this: it reads the current calibration from Xinput. When the usbtouchscreen driver is used, it dynamically changes the calibration. Otherwise it prints the new calibration data in xorg.conf format on stdout. Other actions would be possible too, like rewriting the xorg.conf directly, maybe even use some new evdev/Xinput2 goodness ? It's been quite a while since I was working on this (I changed job, so I never got to finish this), so my comments might not actually be true. First, I'd like to add that I'm glad you're spending time on resurecting my old code. Thanks :-) Second, part of this code was added before the 'evdev' X11 driver got support for touchscreens. This driver allows you to set the calibration parameters at run-time without making changes to xorg.conf (hence no restart of X). I think the calibration tool should use this instead of working with xorg.conf. Wauw, it would be great to use this new 'evdev' functionality! Where can I find out the details about this ? Or could somebody provide a code sample or something ? Thanks, Tias ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: generic touchscreen calibration
On Mon, Sep 14, 2009 at 12:26 PM, Tias t...@ulyssis.org wrote: Søren Hauberg wrote: Hi, 2009/9/10 Tias t...@ulyssis.org: In the end, I had to hack up the ancient tkxinput because it was the only device independent calibrator (it uses Xinput to read the coordinates). On the other hand, I was impressed by the simplicity of the calibrator that Soren Hauberg sent to this list in july (thread titled 'Evdev touchscreen calibration?'), although it was written for usbtouchscreen driven devices specifically. I figured that a generic calibration program should be device independent when reading calibration data, and device dependent in how to use the data. I've adapted Soren's calibrator to do exactly this: it reads the current calibration from Xinput. When the usbtouchscreen driver is used, it dynamically changes the calibration. Otherwise it prints the new calibration data in xorg.conf format on stdout. Other actions would be possible too, like rewriting the xorg.conf directly, maybe even use some new evdev/Xinput2 goodness ? It's been quite a while since I was working on this (I changed job, so I never got to finish this), so my comments might not actually be true. First, I'd like to add that I'm glad you're spending time on resurecting my old code. Thanks :-) Second, part of this code was added before the 'evdev' X11 driver got support for touchscreens. This driver allows you to set the calibration parameters at run-time without making changes to xorg.conf (hence no restart of X). I think the calibration tool should use this instead of working with xorg.conf. Wauw, it would be great to use this new 'evdev' functionality! Where can I find out the details about this ? Or could somebody provide a code sample or something ? It makes use of the XI Properties support in newer servers. See the SUPPORTED PROPERTIES section in evdev(4) for the property names. You can then use the xinput tool to adjust the properties at run time. You could probably look at the xinput source code for inspiration on adjusting the properties from a new gui app. -- Dan ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
