D David Herrmann #
Message details and related content
Hi As Oliver pointed out my proposed wiimote userspace interface isn't exactly the best way to go so I wanted to discuss possible interfaces first. The following data is reported by the wiimote to userspace: - Button data - 3D accelerometer data (1x) - 2D pointing data through IR cam (4x) By motion+ extension: - 3D gyro/rotation data (1x) By nunchuck extension: - 2D analog stick data (1x) - additional buttons - 3D accelerometer data (1x) By classic controller extension: - additional buttons - 2D analog stick (2x) To be extended with further wiimote extensions Obviously this is way too much data for a single interface. Its 23 ABS_ values (4x IR cam!). I could report them through one interface but I had to use my own ABS_ values which are not in input.h since there aren't enough predefined values. Additionally, the driver is capable of disabling the accelerometers, IR cam, gyro etc. on the remote device to save energy (a *lot* of energy). So I really want to enable these devices only if userspace uses them. Interface #1: Everything is reported through one input device and there are sysfs attributes which control the peripherals of the wiimote. Eg., writing 1 to "accelerometer" enables the accelerometer. Writing 0 disables it.