search for: abs_x

...position on the server. Mousedev is not designed to pass those absolute events directly to X, but it can translate them into relative movements. It currently does this for tablet like devices and touchpads. This patch merely tells it to also include a device with ABS_X, ABS_Y, and mouse buttons in its list of devices to process input for. This patch enables the mouse pointer to move when using the remote console. Signed-off-by: Micah Parrish <micah.parrish@hp.com> Signed-off-by: Dmitry Torokhov <dtor@mail.ru>...

This is an update to the Linux part of the Xen PVFB. Linux Xen PVFB is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. Their backends run in dom0 user space. Parts in this patch series: 1. Enable Xen console by default in domU 2. Pointer z-axis (mouse wheel) support 3. Module

This is an update to the Linux part of the Xen PVFB. Linux Xen PVFB is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. Their backends run in dom0 user space. Parts in this patch series: 1. Enable Xen console by default in domU 2. Pointer z-axis (mouse wheel) support 3. Module

This is an update to the Linux part of the Xen PVFB. Linux Xen PVFB is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. Their backends run in dom0 user space. Parts in this patch series: 1. Enable Xen console by default in domU 2. Pointer z-axis (mouse wheel) support 3. Module

This release fixes a missing property for scroll methods if none of the scroll methods were enabled by default (but still available on the device). Another fix for 'mixed' devices, i.e. devices with relative and absolute axes at the same time. This is quite common in MS mice that init all ABS_X axes in addition to relative x/y. Those devices previously got scaled weirdly by the server (because the server would think there's an absolute axis range to scale to). We now prefer the relative axes, restoring normal pointer movement. Finally, this release makes use of the new unaccelerated...

...are scaled to a normalized 1000dpi resolution. This can be used to make high-resolution mice less sensitive without having to actually change the acceleration in the desktop environment. The default for this option is 0 and no scaling is performed. Colin B. Macdonald (1): Workaround lack of ABS_X on MT devices (#80470) Peter Hutterer (12): Drop evdev-specific XKB defaults Require multitouch/smooth scrolling dependencies Split android axis simulation into a helper function Factor out MT axis counting into a separate function Invert two conditions to reduce nest...

Only one change over 2.10, affecting some devices with absolute axes but not ABS_X/ABS_Y. Previously, those devices had the first to axes mapped to axes 0 and 1 and thus some random axes was interpreted as x/y coordinate. With this release, axes 0 and 1 are reserved for x/y axes only. Peter Hutterer (2): Only map x and y to axes 0 and 1 evdev 2.10.1 git tag: xf86-in...

Two fixes in this release, one to support Android MT devices, one to avoid an array index overflow. Colin B. Macdonald (1): Workaround lack of ABS_X on MT devices (#80470) Peter Hutterer (1): evdev 2.9.2 Tobias Himmer (1): Check for incoming MT slot indices exceeding the allocated number of slots. git tag: xf86-input-evdev-2.9.2 http://xorg.freedesktop.org/archive/individual/driver/xf86-input-evdev-2.9.2.tar.bz2 MD5: 99eebf171e...

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. I started with the Xen version at http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/ca05cf1a9bdc Differences to that Xen version, for those who care: * Rewritten on top of fb deferred

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. I started with the Xen version at http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/ca05cf1a9bdc Differences to that Xen version, for those who care: * Rewritten on top of fb deferred

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. I started with the Xen version at http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/ca05cf1a9bdc Differences to that Xen version, for those who care: * Rewritten on top of fb deferred

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. Differences since last post: * Required patch fixing 32-on-64 xen-blkfront included. * Cleanup when xenkbd_probe() fails fixed. * Don't store event channel in device info. I started

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. Differences since last post: * Required patch fixing 32-on-64 xen-blkfront included. * Cleanup when xenkbd_probe() fails fixed. * Don't store event channel in device info. I started

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. Differences since last post: * Required patch fixing 32-on-64 xen-blkfront included. * Cleanup when xenkbd_probe() fails fixed. * Don't store event channel in device info. I started

The following series of 10 patches is a merge of the xenfb and xenconsoled functionality into the qemu-dm code. The general approach taken is to have qemu-dm provide two machine types - one for xen paravirt, the other for fullyvirt. For compatability the later is the default. The goals overall are to kill LibVNCServer, remove alot of code duplication and/or parallel impls of the same concepts, and

Hey Guys, The ForceFeedback from my Microsoft Sidewinder ForceFeedback Wheel doesn't work with Wine. I compiled wine myself and "ac_cv_member_struct_ff_effect_direction=yes" was set in the config.log like it is told here: http://wiki.winehq.org/ForceFeedback I also checked that FF is working with BZFlag under Linux. When i play BZFlag with Wine, the FF-Effects are missing. I

Hello, Sometimes the backend of PVFB knows that it doesn''t need permanent refresh, when the window is minimized for instance (no refresh at all), or the administration tools know that the window is thumnailed, and so a slow refresh rate is fine. Also, some users may want to tune the refresh rate according to the smoothness they would like, balanced with the CPU time that requires.

Changes from v3: - mini-os configuration files moved into stubdom/ - mini-os extra console support now a config option - Fewer #ifdefs - grant table setup uses hypercall bounce - Xenstore stub domain syslog support re-enabled Changes from v2: - configuration support added to mini-os build system - add mini-os support for conditionally compiling frontends, xenbus -