Confused

[James Cloos]

>>>>> "Simon" == Simon Thum <simon.thum at gmx.de> writes:

Simon> I fully agree for diverse buttons, but why should evdev handle a
Simon> 'Video Bus'? OTOH, as long as it doesn't cause problems, all is fine.

The Video Bus input device is a keyboard.  Mine is:

,----[ excerpt from: /proc/bus/input/devices ]
| I: Bus=0019 Vendor=0000 Product=0006 Version=0000
| N: Name="Video Bus"
| P: Phys=/video/input0
| S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0A03:00/device:08/device:09/input/input3
| U: Uniq=
| H: Handlers=kbd event3 
| B: EV=3
| B: KEY=3f000b 0 0 0 0 0 0 0
`----

The Handlers line shows that it is a keyboard (and only a keyboard).

The KEY= line shows that "Video Bus" can send any of these keys:

,----[ excerpt from: /usr/include/linux/input.h ]
| #define KEY_BRIGHTNESSDOWN      224
| #define KEY_BRIGHTNESSUP        225
| #define KEY_SWITCHVIDEOMODE     227     /* Cycle between available video
|                                            outputs (Monitor/LCD/TV-out/etc) */
| #define KEY_UNKNOWN             240
| #define KEY_VIDEO_NEXT          241     /* drive next video source */
| #define KEY_VIDEO_PREV          242     /* drive previous video source */
| #define KEY_BRIGHTNESS_CYCLE    243     /* brightness up, after max is min */
| #define KEY_BRIGHTNESS_ZERO     244     /* brightness off, use ambient */
| #define KEY_DISPLAY_OFF         245     /* display device to off state */
`----

So, if one wants to handle those keys via X, evdev needs to read that
input device.

-JimC
-- 
James Cloos <cloos at jhcloos.com>         OpenPGP: 1024D/ED7DAEA6