| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
to return useful data
|
|\ |
|
| | |
|
| | |
|
|\| |
|
| |
| |
| |
| |
| |
| |
| |
| | |
this keeps it small enough to fit in a float, which makes it possible
to see the full value in a MAVLink tlog
Conflicts:
mavlink/include/mavlink/v1.0
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
this device ID identifies a specific device via the tuple of (bus, bus
type, address, devtype). This allows device specific configuration
data to be stored along with a device ID, so the code can know when
the user has changed device configuration (such as removing an
external compass), and either invalidate the device configuration or
force the user to re-calibrate
|
|/ |
|
| |
|
|
|
|
|
| |
this allows drivers to register generic device names for a device
class, with automatic class instance handling
|
|
|
|
|
|
|
|
| |
way of talking to drivers regardless of which of the specialised classes they derive from.
Make the Device destructor public and virtual, so that arbitrary devices can be deleted. Likewise for classes that derive from it.
Make Device::init public so that arbitrary devices can be initialised after being returned by factories.
|
|
|