Advantech RSB-4210 Evaluation Kit User Manual download pdf (Page 101)

93 RSB-4210 User Manual

Chapter 3 Software Functionality

The right way would be to pass the events to keyboard.c directly, best if key-

board.c would itself be an event handler. This is done in the input patch, available

on the webpage mentioned below.

B. mousedev

mousedev is also a hack to make programs that use mouse input work. It takes

events from either mice or digitizers/tablets and makes a PS/2-style (a la /dev/

psaux) mouse device available to the userland. Ideally, the programs could use a

more reasonable interface, for example evdev

Mousedev devices in /dev/input (as shown above) are:

crw-r--r-- 1 root root 13, 32 Mar 28 22:45

mouse0

crw-r--r-- 1 root root 13, 33 Mar 29 00:41

mouse1

crw-r--r-- 1 root root 13, 34 Mar 29 00:41

mouse2

crw-r--r-- 1 root root 13, 35 Apr 1 10:50

mouse3

...

crw-r--r-- 1 root root 13, 62 Apr 1 10:50

mouse30

crw-r--r-- 1 root root 13, 63 Apr 1 10:50

mice

Each 'mouse' device is assigned to a single mouse or digitizer, except the last one

- 'mice'. This single character device is shared by all mice and digitizers, and even

if none are connected, the device is present. This is useful for hotplugging USB

mice, so that programs can open the device even when no mice are present.

CONFIG_INPUT_MOUSEDEV_SCREEN_[XY] in the kernel configuration are the

size of your screen (in pixels) in XFree86. This is needed if you want to use your

digitizer in X, because its movement is sent to X via a virtual PS/2 mouse and thus

needs to be scaled accordingly. These values won't be used if you use a mouse

only.

Mousedev will generate either PS/2, ImPS/2 (Microsoft IntelliMouse) or Explor-

erPS/2 (IntelliMouse Explorer) protocols, depending on what the program reading

the data wishes. You can set GPM and X to any of these. You'll need ImPS/2 if you

want to make use of a wheel on a USB mouse and ExplorerPS/2 if you want to

use extra (up to 5) buttons.

C. joydev

Joydev implements v0.x and v1.x Linux joystick api, much like drivers/char/joystick/

joystick.c used to in earlier versions. See joystick-api.txt in the Documentation

subdirectory for details. As soon as any joystick is connected, it can be accessed

in /dev/input on:

crw-r--r-- 1 root root 13, 0 Apr 1 10:50 js0

crw-r--r-- 1 root root 13, 1 Apr 1 10:50 js1

crw-r--r-- 1 root root 13, 2 Apr 1 10:50 js2

crw-r--r-- 1 root root 13, 3 Apr 1 10:50 js3

...

And so on up to js31.

D. evdev

1 2 ... 96 97 98 99 100 101 102 103 104

Comments to this Manuals

No comments

Advantech RSB-4210 Evaluation Kit User Manual Page 101

Comments to this Manuals

Related products and manuals for Server barebones Advantech RSB-4210 Evaluation Kit