AP_ADC: fixed scaling factor for voltage on APM1 Ch6 ADC
AP_Rangefinder: use voltage_average() interface for generic analog rangefinder
AP_ADC_AnalogSource: fixed reference scaling for APM1 Ch6 ADC

it is not referenced to Vcc
AP_Airspeed: use new voltage_average() API in Airspeed driver
Plane: removed INPUT_VOLTS parameter

no longer needed
Rover: removed INPUT_VOLTS parameter

no longer needed
AP_Mount: fixed scaling of the joystick speed to give better control

thanks to Chris Miser for reporting this problem
Build: Cygwin Windows build and upload fixes

SITL, HIL and normal builds and uploads work under Cygwin
Build: MINGW can be used to build/upload apm hex
Build: fix case of "com3" and add Arduino path override
Plane: make a throttle_cruise of 0 mean always zero throttle

this can be used for parachute landing missions

Thanks to Chris Miser for the suggestion
Plane: don't trigger GCS failsafe if GCS never connected

The we have never received a heartbeat message from the GCS then don't
use the lack of heartbeat to trigger a failsafe event
Plane: Added extra parameter to specify at what speed in auto-takeoff throttle should engage

This adds TKOFF_THR_MINSPD in m/s
Plane: added TKOFF_THR_MINACC option

this is used for triggering auto takeoff with a hand launched plane
Examples: Improved compatibility with Mission Planner serial terminal (CLI)
autotest: build all binaries for master on each commit
Docs: Add XML emit to param_parse.py.  See below for more details...

I've refactored the param_parse tool to use various 'emitters'.  An emitter
can take parameter info and output it in a particular format.  Currently the
only supported emitters are the wiki and XML formats.

The goal of these changes is to create a standard machine readable description
of parameters - mainly for use by ground control stations, but it will also
enable spiffy scripting environments where code can refer symbolically to
vehicle parameters (reflectionish).

Open issue: Is there any sort of Ardupilot build id which can be included in
the generated XML?  That would ensure that we select the correct paramdefs
for the load on the target (possibly by asking the target for a SHA or
somesuch).  If that issue is resolved, then the filename for the XML
file should probably be something like:
arduplane-ca5742ac.pdef.xml.

It is worth noting that I've proposed a suffix of ".pdef.xml" for these file
types.  This facilitates automated file handling on Android devices.  On
Android you can register 'handlers' for particular file extensions and if
the user tries to open that extension in email or a web browser your app
will be given a chance to do something about it.  The 'outer' xml extension
will allow naive editors to know that at least this is an xml file.

I will include a sample of the XML format with the pull-request for this CL.
Build: fixed location of latest/ directory
DataFlash: start to fix example build
autotest: fixed python path for mavtemplate