[ANNOUNCE] xf86-input-synaptics 1.1.1
Main issues fixed: - avoiding allocations during the signal handler. - several 64 bit property issues with synclient - The driver tries to detect the touchpad model and adjusts the edge values accordingly. This addresses issues where edge scrolling appeared to be broken on certain touchpad models (ALPS, appletouch) due to incorrect RightEdge values. Cheers, Peter Adam Jackson (1): Allocate the timer early so we don't try to malloc it within a sigio handler. Eygene Ryabinkin (1): PS/2 interface: sense multifinger taps on FingerHigh (#21427) Peter Hutterer (13): Don't fail when building against server 1.5 synclient: fix 32-bit integer handling on 64 bit machines. synclient: fix 64 bit issues for float properties. Fix typo, missing : ps2comm: fix typo in debug statement. man: document left-handed TapButton awkwardness. Only try to free the timer if it's actually there. Add TouchpadModel specifier and scale the edges accordingly. (#21214) If QueryHardware failed, return that failure and clean up. Shut up valgrind warnings about uninitialized variables. eventcomm: force boolean values for has_left, has_right, etc. synclient: up max value for AccelFactor to 1.0 synaptics 1.1.1 git tag: xf86-input-synaptics-1.1.1 http://xorg.freedesktop.org/archive/individual/driver/xf86-input-synaptics-1.1.1.tar.bz2 MD5: c6ffee3c08c509a01cb3d4230b83ff00 xf86-input-synaptics-1.1.1.tar.bz2 SHA1: 74488a3d3ffc747e36761abac96cc96fee786c48 xf86-input-synaptics-1.1.1.tar.bz2 http://xorg.freedesktop.org/archive/individual/driver/xf86-input-synaptics-1.1.1.tar.gz MD5: fc541eb6d72be0c4a2365f4bad2121a8 xf86-input-synaptics-1.1.1.tar.gz SHA1: a47aff9833e3c0c5d1327abf0066fb151eaa65bf xf86-input-synaptics-1.1.1.tar.gz pgpSOc9kNVthz.pgp Description: PGP signature ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Setting resolution of external monitor
Op 20-05-09 13:09, Oliver Block schreef: Dear Éric, On Wed, May 20, 2009 at 11:49:30AM +0200, Éric Piel wrote: [...] From what I understand you want panning. I would do it with this command: xrandr --output PANEL --mode 1680x1050 --panning 1920x1080 I cannot try this actually, since I only have xrandr 1.2 However, it requires xrandr 1.3, I don't know if your driver has already support for this new version. I an not really sure what panning means. Would this mean that the laptop panel would display the part of the screen where the mouse moves (like if it would be virtual) and the external monitor would display the whole screen in 1920x1080? Yes, exactly. This would be okay, but if the laptop would display a fixed area of the screen it would also be okay. Mainly I want that the external screen runs at 1920x1080 and I do not know how to do this, since xrandr does not list this mode. If the laptop's panel doesn't have to move, it's possible to do this just with xrandr 1.2. As the 1920x1080 modeline seems to be detected and accepted by the driver, it's a bit weird why it doesn't appears in xrandr. Maybe should you try with a more recent xserver/radeonhd? Otherwise, have you tried forcing the mode of the VGA_1 output? Something like: xrandr --newmode 1920x1080n 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync xrandr --addmode VGA_1 1920x1080n xrandr --output VGA_1 --mode 1920x1080n Eric begin:vcard fn;quoted-printable:=C3=89ric Piel n;quoted-printable:Piel;=C3=89ric org:Technical University of Delft;Software Engineering Research Group adr:HB 08.080;;Mekelweg 4;Delft;;2628 CD;The Netherlands email;internet:e.a.b.p...@tudelft.nl tel;work:+31 15 278 6338 tel;cell:+31 6 2437 9135 x-mozilla-html:FALSE url:http://pieleric.free.fr version:2.1 end:vcard ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Joystick input driver and multimedia key events
On Thu, May 21, 2009 at 11:59:38AM +0200, Sascha Hlusiak wrote: Hi, Is it possible to use joystick driver to generate multimedia key events? I wanted to make i.e. buttons 1 and 3 to be volume up and volume down like this: Option MapButton1key=0x1008,0xff13 Option MapButton3key=0x1008,0xff11 I got codes 0x1008ff13 and 0x1008ff11 from xev (I didn't found appropriate constants in /usr/include/X11/keysymdef.h). I tried to put /usr/share/X11/XKeysymDB is the best collection of all keysyms. the codes you're looking for come from XF86Keysym.h) 32-bit numbers, but I got error about this, so i tried the above, but got nothing. If my approach is wrong, how could I get multimedia key actions to work with joystick driver? configuring key=0x1008ff13 worked for me and produced the desired key. xev shows the name as well so it's easy to check. While it is possible to generate those key events, there is a fundamental problem with grabs on those keys. Basically, applications grab on scancodes of a certain input device. Pressing a button on the joystick changes the primary device and the key has to be regrabbed. But of course the first keystroke is lost. For me the above configuration did raise the volume, but on the 2nd button press only. This problem exists with other input devices and grabs as well and is not a joystick driver specific problem. FWIW, XI2 has keysym grabs instead of keycode grabs, so that problem should be gone. Cheers, Peter ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
[intel] 'Virtual' parameter to go away?
Hi everyone, some months ago, there was the idea to remove the (need of a) 'Virtual' parameter in the Display SubSection of the intel driver. What are the current plans? In the spirit of Xorg.conf-free auto-configuration, it would be very nice if this parameter was not needed (or would default to the maximum possible size for the hardware - e.g. 2048 x 2048 on an i915). Regards, Andreas ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: patch XACE
Deflesselle Yann wrote: Hi, I am currently doing a project which is to create a secure GNU/Linux OS and so I have to make Xorg and SELinux work together, so for that I need the XACE patch but sadely I couldn't find it anywhere so I was wondering if someone could tell me where I could find it. XACE has been integrated to the Xorg server since Xorg 1.2 - no patch is necessary nor maintained. -- -Alan Coopersmith- alan.coopersm...@sun.com Sun Microsystems, Inc. - X Window System Engineering ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Joystick input driver and multimedia key events
After putting (and restarting X) Option MapButton1key=0x1008ff13 Option MapButton3key=0x1008ff11 this is what I get from xev for buttons 1 and 3: KeyPress event, serial 49, synthetic NO, window 0x3c1, root 0x8c, subw 0x0, time 48271360, (529,604), root:(627,752), state 0x10, keycode 9 (keysym 0xff1b, Escape), same_screen YES, XLookupString gives 1 bytes: (1b) XmbLookupString gives 1 bytes: (1b) XFilterEvent returns: False KeyRelease event, serial 51, synthetic NO, window 0x3c1, root 0x8c, subw 0x0, time 48271552, (529,604), root:(627,752), state 0x10, keycode 9 (keysym 0xff1b, Escape), same_screen YES, XLookupString gives 1 bytes: (1b) XFilterEvent returns: False KeyPress event, serial 51, synthetic NO, window 0x3c1, root 0x8c, subw 0x0, time 48277632, (529,604), root:(627,752), state 0x10, keycode 11 (keysym 0x32, 2), same_screen YES, XLookupString gives 1 bytes: (32) 2 XmbLookupString gives 1 bytes: (32) 2 XFilterEvent returns: False KeyRelease event, serial 51, synthetic NO, window 0x3c1, root 0x8c, subw 0x0, time 48277792, (529,604), root:(627,752), state 0x10, keycode 11 (keysym 0x32, 2), same_screen YES, XLookupString gives 1 bytes: (32) 2 XFilterEvent returns: False Maybe is something Ubuntu-specific? Everything else is working except those MM keycodes... Žarko On Thu, May 21, 2009 at 2:37 PM, Peter Hutterer peter.hutte...@who-t.net wrote: On Thu, May 21, 2009 at 11:59:38AM +0200, Sascha Hlusiak wrote: Hi, Is it possible to use joystick driver to generate multimedia key events? I wanted to make i.e. buttons 1 and 3 to be volume up and volume down like this: Option MapButton1 key=0x1008,0xff13 Option MapButton3 key=0x1008,0xff11 I got codes 0x1008ff13 and 0x1008ff11 from xev (I didn't found appropriate constants in /usr/include/X11/keysymdef.h). I tried to put /usr/share/X11/XKeysymDB is the best collection of all keysyms. the codes you're looking for come from XF86Keysym.h) 32-bit numbers, but I got error about this, so i tried the above, but got nothing. If my approach is wrong, how could I get multimedia key actions to work with joystick driver? configuring key=0x1008ff13 worked for me and produced the desired key. xev shows the name as well so it's easy to check. While it is possible to generate those key events, there is a fundamental problem with grabs on those keys. Basically, applications grab on scancodes of a certain input device. Pressing a button on the joystick changes the primary device and the key has to be regrabbed. But of course the first keystroke is lost. For me the above configuration did raise the volume, but on the 2nd button press only. This problem exists with other input devices and grabs as well and is not a joystick driver specific problem. FWIW, XI2 has keysym grabs instead of keycode grabs, so that problem should be gone. Cheers, Peter ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: xf86-video-intel: 2 commits - src/drmmode_display.c src/i830_exa.c src/i830.h src/i830_memory.c src/i830_video.c
On Wed, 2009-05-20 at 08:20 +0200, Michel Dänzer wrote:
On Tue, 2009-05-19 at 10:09 -0700, Eric Anholt wrote:
commit 34660fd2df5d61b77ed7041d32ac29053fc94f5a
Author: Eric Anholt e...@anholt.net
Date: Fri May 15 23:21:05 2009 -0700
Only sync XV to vblank when drawing to the frontbuffer.
This fixes emitting syncs to random pipes with boxes bigger than that
pipe's vertical, leading to GPU hangs.
Bug #21738
diff --git a/src/i830_video.c b/src/i830_video.c
index 1c3a5b7..6fec8ff 100644
--- a/src/i830_video.c
+++ b/src/i830_video.c
@@ -2495,13 +2495,15 @@ I830PutImage(ScrnInfoPtr pScrn,
if (sync) {
BoxPtr box;
int y1, y2;
-int pipe, event, load_scan_lines_pipe;
-
- if (pI830-use_drm_mode)
- pipe = drmmode_get_pipe_from_crtc_id(pI830-bufmgr, crtc);
- else {
- I830CrtcPrivatePtr intel_crtc = crtc-driver_private;
- pipe = intel_crtc-pipe;
+ int pipe = -1, event, load_scan_lines_pipe;
+
+ if (pPixmap != pScreen-GetScreenPixmap(pScreen)) {
+ if (pI830-use_drm_mode)
+ pipe = drmmode_get_pipe_from_crtc_id(pI830-bufmgr, crtc);
+ else {
+ I830CrtcPrivatePtr intel_crtc = crtc-driver_private;
+ pipe = intel_crtc-pipe;
+ }
This seems to do the opposite of what the commit message says, i.e. only
sync when not drawing to the front buffer.
Thanks. Somehow both keithp and I missed it.
--
Eric Anholt
e...@anholt.net eric.anh...@intel.com
signature.asc
Description: This is a digitally signed message part
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
Re: [intel] 'Virtual' parameter to go away?
On Thu, 2009-05-21 at 15:29 +0200, Andreas Schildbach wrote: Hi everyone, some months ago, there was the idea to remove the (need of a) 'Virtual' parameter in the Display SubSection of the intel driver. What are the current plans? In the spirit of Xorg.conf-free auto-configuration, it would be very nice if this parameter was not needed (or would default to the maximum possible size for the hardware - e.g. 2048 x 2048 on an i915). Already done with UXA+DRI2: anh...@gaiman:anholt/src/linux-2.6% xrandr Screen 0: minimum 320 x 200, current 1920 x 1200, maximum 8192 x 8192 VGA1 connected 1920x1200+0+0 (normal left inverted right x axis y axis) 519mm x 324mm 1920x1200 60.0*+ 1280x1024 75.0 1152x864 75.0 1024x768 75.1 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 640x48072.8 75.0 66.7 60.0 720x40070.1 640x35070.1 LVDS1 connected (normal left inverted right x axis y axis) 1280x800 60.0 + TV1 disconnected (normal left inverted right x axis y axis) -- Eric Anholt e...@anholt.net eric.anh...@intel.com signature.asc Description: This is a digitally signed message part ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Cursor freeze with XInput2
On Wed, May 20, 2009 at 06:54:47PM +0200, Florian Echtler wrote: Hello everyone, I'm running Peter's development branch with MPX/Xinput2, and mostly everything is working fine. However, I currently can't use gimp or inkscape. As soon as I click somewhere in the drawing, the cursor freezes and can't be moved anymore (regardless of whether I have only one or several pointers active). I can use the keyboard to switch to the console and kill gimp or inkscape, briefly making X usable again, but this will usually result in a X server crash some seconds later. gimp is being nasty. one of the behaviours changed is that if you directly grab an attached slave device, it is detached for the duration of the grab. otherwise, a grabbed device would still send events through the master device, which is just wrong. Gimp grabs all devices it can find as soon as you hit a button, so it floats all slaves for you. IIRC it does so on a ButtonPress event, but once a device is detached, it doesn't send core events anymore so the matching release is never triggered. I don't know how to fix this without changing gimp. A previous fix was to only list floating slave devices in XListInputDevices, but that got removed from the XI2 branch recently. the server crash isn't a gimp feature though, a backtrace would be much appreciated. Cheers, Peter ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
