px4-firmware - PX4 Firmware for PX4FMU autopilot and PX4IO servo / failsafe board

	Commit message (Collapse)	Author	Age	Files	Lines
*	APP -> MODULE	px4dev	2013-02-23	1	-86/+86
\| \| \| \|	remove as many duplicate slashes, etc. as seems practical
*	Checkpoint: application framework makefile done	px4dev	2013-02-23	1	-61/+139
\|
*	Get a bit fancier with the builtin app specifications, so that we can ↵	px4dev	2013-02-23	1	-3/+30
\| \| \| \|	generate them from apps as well as the config.
*	platform -> board	px4dev	2013-02-23	1	-16/+16
\|
*	Auto-generate builtin command prototypes.	px4dev	2013-02-23	1	-66/+77
\| \| \| \|	Tidy up path configuration, etc.
*	Add support for per-config ROMFS generation.	px4dev	2013-02-23	1	-1/+57
\|
*	Rename makefiles to help categorise them.	px4dev	2013-02-23	1	-1/+1
\|
*	Simplify the PLATFORM/CONFIG handling a little.	px4dev	2013-02-23	1	-1/+5
\|
*	Move upload functionality out into a separate makefile.	px4dev	2013-02-23	1	-18/+6
\|
*	Move more functionality into firmware.mk. Now we build the px4 bundles in a ↵	px4dev	2013-02-23	1	-19/+160
\| \| \| \| \| \|	way that will let external builders generate them too. Pass the platform define into the firmware builder.
*	Recover commits lost in the previous merge. Syllableise PX4_BASE like its peers.	px4dev	2013-02-23	1	-0/+6
\|
*	Break up the firmware build into a 'make export' phase for NuttX on a ↵	px4dev	2013-02-23	1	-0/+71
	per-board basis, and then a separate per-config phase that allows us to avoid re-building NuttX all the time, and ship more than one firmware config for a given board. This is a first cut; it builds one firmware for each of FMU and IO.