(bootstrap files) added control-test to bootstrapper configuration
(control-test) don't set values in mod. control obj. if has no Module set

Bad things will happen if you do.
(control-test) init input-device cache values to make valgrind shut up
(control-test,drive-test) don't abort on I2C write fail

It's possible for one write to fail and the next one succeed, for example.
(control-test) send control packets at 25 Hz (prev. 10 Hz)
bootstrap/drive-test: add default-mode, a default value for server-port
bootstrap: added systemctl entry to enable remote shutdown/restart/etc.
drive-test: renamed ChassisData.h => DriveData.h
control-test: made gnublin_i2c.[ch]pp symlinks to drive-test copies of same
drive-test/gnublin-i2c.cpp: return useful error codes, damnit
control-test: remove `volatile' keyword from static vars

This was causing problems, apparently.
drive-test: set cubic mapping for all axes
drive-test: improve usefulness of output for diagnosing problems
drive-test: correct CRISP module name
drive-test: don't set values in mod control obj. if has no Module set

Bad things will happen if you do.  See also @0072c89.
drive-test: fix reversed vert. axes for our stupid Logitech game pad
Merge remote-tracking branch 'origin/master'
drive-test: update I2C_SLAVE_ADDRESS and I2C_BUS for Rasp. Pi
cmake/RaspberryPiToolchain: Cross-compiler toolchain file

I've had this lying around, thought I'd throw it up on Git.
Haven't had any luck with cross-compiling for the Pi myself,
but it's *supposed* to be possible...