• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..03-May-2022-

fdi/H25-Jun-2015-535424

man/H25-Jun-2015-682537

shared/H25-Jun-2015-1,392786

src/H25-Jun-2015-2,3331,514

tools/H25-Jun-2015-1,317954

COPYINGH A D07-Sep-20102.7 KiB5244

ChangeLogH A D25-Jun-201544.8 KiB1,305879

INSTALLH A D25-Jun-201511.1 KiB292219

Makefile.amH A D30-Oct-20141.5 KiB3610

Makefile.inH A D25-Jun-201526.1 KiB837721

READMEH A D07-Sep-20102.6 KiB6751

aclocal.m4H A D25-Jun-2015411.8 KiB11,68110,561

config.guessH A D25-Jun-201543.8 KiB1,5311,321

config.h.inH A D25-Jun-20152.8 KiB12281

config.subH A D25-Jun-201534.6 KiB1,7741,631

configureH A D03-May-2022591.5 KiB20,83616,976

configure.acH A D25-Jun-20156.9 KiB216187

depcompH A D25-Jun-201520.4 KiB709460

install-shH A D25-Jun-201513.7 KiB528351

ltmain.shH A D25-Jun-2015276.8 KiB9,6567,304

missingH A D25-Jun-201510.1 KiB332243

README

1VMMouse
2-------
3
4The VMMouse driver enables support for the special VMMouse protocol
5that is provided by VMware virtual machines to give absolute pointer
6positioning.
7
8Installing the driver will improve the user experience when using the
9mouse to interact with the guest operating system. In particular, use of
10the driver improves mouse "lag", provides mouse speed and acceleration
11consistent with the user's host operating system, and enables the
12auto-grab/ungrab feature in VMware products without requiring the VMware
13toolbox application.
14
15Using the driver
16----------------
17
18Assuming you have built and installed the driver in the standard way
19for autotools based packages (see INSTALL), or the driver was already
20installed by your distro, using it is simply a matter of changing the
21driver used for the mouse input device from "mouse" to "vmmouse".
22
23The vmmouse driver is capable of falling back to the standard "mouse"
24driver if a VMware virtual machine is not detected. This allows for
25dual-booting of an operating system from a virtual machine to real hardware
26without having to edit xorg.conf every time.
27
28Implementation
29--------------
30
31The following is not necessary reading for anyone who wants to use the
32driver, but should help anyone who wants to understand how it works or
33who wants to write a driver for a different target, whether it's another
34operating system, a linux kernel input driver or even gpm.
35
36The driver is composed of three different layers:
37
381) The vmmouse protocol layer (vmmouse_proto.[c|h])
39   - This provides the call to read and write the port over which
40     the vmmouse packets are transfered.
41
422) The vmmouse client layer (vmmouse_client.[c|h])
43   - This builds on top of the protocol layer to provide higher
44     level calls for enabling/disabling the vmmouse mechanism
45     and for reading data.
46   - A new driver for a different target would use this interface.
47
483) The Xorg vmmouse driver (vmmouse.c)
49   - This is the actual Xorg specific part of the driver.
50   - Note that interrupts indicating the presence of mouse data
51     are still transmitted on the PS/2 port so it is necessary
52     to be set up to receive those interrupts like a standard
53     PS/2 driver, but the actual data on the PS/2 port is ignored.
54
55vmmouse_detect
56--------------
57
58A simple program to detect whether the vmmouse device is present.
59It is used by the HAL callout script to automatically detect a
60vmmouse device.
61
62Returns 0 if we are running in a virtual machine where the vmmouse
63device is present.
64
65Returns 1 otherwise (either we are not in a VM or the vmmouse device
66was disabled).
67