Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

wminput(1) [debian man page]

WMINPUT(1)						      General Commands Manual							WMINPUT(1)

NAME

       wminput - an event driver for the wiimote

SYNOPSIS

       wminput [options]

DESCRIPTION

       This manual page documents briefly the wminput command.

       wminput is a program that provides an event driver for the wiimote, supporting all buttons (except Power) and pointer tracking, and featur-
       ing a tracking algorithm plugin architecture.

       Your kernel must be configured with uinput support (INPUT_UINPUT, or Device Drivers/Input Device Support/Miscellaneous  Drivers/User  Level
       Driver  Support under menuconfig).  Compile into the kernel or as a module.  See http://gentoo-wiki.com/HOWTO_Compile_a_Kernel_Manually for
       information on kernel compilation.  By default, some (most? all?) udev configurations set up a uinput device file readable  only  by  root.
       Using  wminput  as  a  user other than root requires configuration udev to change the permissions on uinput.  Place the following line in a
       file in /etc/udev/rules.d (see the documentation for your distro for the recommended file for local rules) to allow anyone on the system to
       use uinput:

       KERNEL=="uinput", MODE="0666"

       A more secure method uses the following line to allow anyone in <group> to use wminput, and adds only the desired users to <group>:

       KERNEL=="uinput", GROUP="<group>"

       A uinput group can be created specifically for this purpose, or another existing group such as wheel can be used.

       Getting	X  to  recognize  non-standard	key  symbols,  and  mapping  actions to those symbols, is not automatic.  An excellent tutorial at
       http://gentoo-wiki.com/HOWTO_Use_Multimedia_Keys can help you set this up.  An overview of the process (see the	HOWTO  for  more  informa-
       tion):
       1.Edit ~/.CWiid/wminput.conf
       2.Use xev, wminput, and your wiimote to find out if the key symbols are already mapped, and find the key codes if they are not.
       3.If  the  codes  are  not  mapped  to  the appropriate symbols, edit ~/.Xmodmap, and use xmodmap to map them.  (A copy of my ~/.Xmodmap is
       included in CWiid/doc)
       4.Use xbindkeys or a window manager-specific utility to map the key symbols to specific actions.

       wminput tracking plugins are, by default, installed to /usr/lib/CWiid/plugins.  Plugins may also be placed in ~/.CWiid/plugins, and plugins
       placed here will take precedence.

OPTIONS

       -h     Show summary of options.

       -v, --version
	      Output version information and exit.

       -c, --config [file]
	      Choose config file to use.

       -d, --daemon
	      Implies -q, -r, and -w.

       -q, --quiet
	      Reduce output to errors

       -r, --reconnect [wait]
	      Automatically try reconnect after wiimote disconnect.

       -w, --wait
	      Wait indefinitely for wiimote to connect.

       bdaddr Specify the wiimote bluetooth address. The bluetooth device address (bdaddr) of the wiimote can be specified on the command-line, or
	      through the WIIMOTE_BDADDR environment variable, in the that order of precedence.  If neither is given, the first wiimote  found	by
	      hci_inquiry will be used.

SEE ALSO

       wmgui(1),

AUTHOR

       wminput was written by L. Donnie Smith <cwiid@abstrakraft.org>

       This manual page was written by Romain Beauxis <toots@rastageeks.org>, for the Debian project (but may be used by others).

								 janvier 18, 2007							WMINPUT(1)

Check Out this Related Man Page

LIRCMD(8)								FSF								 LIRCMD(8)

NAME

       lircmd - LIRC mouse daemon translates infrared signals into mouse events

SYNOPSIS

       lircmd [options] [config-file]

DESCRIPTION

       This  daemon  can  simulate a MouseSystems, IntelliMouse or IMPS/2 type mouse. It gets the received buttons from lircd and converts them to
       mouse events. To make this possible, lircmd needs a config file located in /etc/lircmd.conf. In this file you have to determine which  but-
       ton  from  which  remote causes a mouse move or a mouse button click.  You can also specify a special button which activates or deactivates
       the mouse mode.

       -h --help
	      display this message

       -v --version
	      display version

       -n --nodaemon
	      don't fork to background

       -u --uinput
	      generate Linux input events

OPTIONS

       If you provide the --nodaemon option lircmd won't fork to background.

       On Linux systems the --uinput option will enable automatic generation of Linux input events. lircmd will open /dev/input/uinput and  inject
       the simulated mouse events into the Linux kernel rather than creating the /dev/lircm device.

FILES

       lircmd will use syslogd to output error messages. It depends on your system configuration where they will show up.

DAEMONS

       lircd  and  lircmd are daemons. You should start them in some init script depending on your system. There are some example scripts for dif-
       ferent distributions in the contrib directory. lircmd has to be started after lircd as it connects to the socket lircd provides.

       If you start lircd or lircmd from your shell prompt you will usually get back immediately to the prompt. Often people think that  the  pro-
       gram has died. But this is not an error. lircd and lircmd are daemons. Daemons always run in background.

SEE ALSO

       The documentation for lirc is maintained as html pages. They are located under html/ in the documentation directory.

lircmd 0.8.7pre1						     May 2010								 LIRCMD(8)
Man Page