aepko/Ardupilot2
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
ArduPlane, ArduCopter, ArduRover, ArduSub source
17,228 Commits 72 Branches 509 Tags 683 MiB
C++ 68.3%
Python 13%
C 11%
Lua 4.4%
HTML 1.1%
Other 1.8%
a4c1b0d75f
Go to file
Lucas De Marchi a4c1b0d75f AP_HAL_Linux: add constructor to find I2C bus reliably 
The device number in /dev may not be reliable from one boot to another
due to the initialization order of each bus.

For example, in Minnow Board Max, the exposed I2C buses may be i2c-7 and
i2c-8 or i2c-8 and i2c-9 depending if the platform driver in the kernel
is initialized before or after the PCI.

It also may change with different version and configuration of the DT or
UEFI used making another kernel driver to bind to the device. This means that
for Minnow Board Max we need to use something like below to pass to the
constructor:

	static const char * const i2c_devpaths[] = {
	    /* UEFI with lpss set to ACPI */
	    "/devices/platform/80860F41:05",
	    /* UEFI with lpss set to PCI */
	    "/devices/pci0000:00/0000:00:18.6",
	     NULL
	};

The devpath here is the one returned by udev with the following command:

	udevadm info -q path /dev/<i2c-device>

In contrary to the device number in /dev/i2c-N, this path in sysfs is
stable across reboots and can only change if there's a change in the
UEFI firmware or the board's device tree.

This patch assumes the currently supported boards don't have this
problem so it's not touching them.
2015-06-30 09:10:54 +10:00
AntennaTracker AntennaTracker: fixed pde path 2015-06-16 09:59:27 +10:00
APMrover2 Rover: DataFlash frontend/backend split 2015-06-26 16:02:51 +10:00
ArduCopter Copter: loiter state reads takeoff climb rate during takeoff 2015-06-29 13:49:58 +09:00
ArduPlane Plane: DataFlash frontend/backend split 2015-06-26 16:02:50 +10:00
docs docs: allow docs build to output to another directory 2013-08-15 09:04:58 +10:00
libraries AP_HAL_Linux: add constructor to find I2C bus reliably 2015-06-30 09:10:54 +10:00
mk build: removed include of vehicle directory in build 2015-06-29 15:34:43 +10:00
modules PX4Firmware: submodule update 2015-06-27 21:25:09 +10:00
Tools Replay: fixed build 2015-06-29 15:59:53 +10:00
.editorconfig all: Change the editorconfig so that it won't want to reformat 2014-07-09 19:03:18 -07:00
.gitattributes Revert ".gitattributes: automatically clean up newlines in source files" 2015-04-20 11:04:59 +09:00
.gitignore .gitignore update for jsbsim changes 2015-06-26 21:58:27 +10:00
.gitmodules modules: added git submodules for PX4 build 2015-06-09 12:48:56 +10:00
.pydevproject AP_Relay: add -1:Disabled to list of param values 2014-05-15 17:13:37 +09:00
.travis.yml Travis: removed parallism from coverity build 2015-06-20 17:03:15 +10:00
CONTRIBUTING.md Update CONTRIBUTING.md 2014-10-12 00:11:30 -07:00
COPYING.txt cmake overhaul, cleaned up readme, added license 2011-09-30 17:32:51 -04:00
Doxyfile.in Working on doxygen support. 2011-11-25 21:35:20 -05:00
Makefile build: simple top level makefile 2015-06-03 06:32:10 +10:00
README.md Maintainers: add Peter as DataFlash maintainer 2015-06-26 16:08:38 +10:00
reformat.sh better commit message for uncrustify 2012-08-17 11:36:07 -07:00
uncrustify_cpp.cfg fixes to preprocessor retab settings 2012-08-17 11:36:07 -07:00
uncrustify_headers.cfg small changes to uncrustify_headers.cft 2012-08-21 18:59:13 -07:00
Vagrantfile Fix vagrant build issues with submodules. 2015-06-18 08:47:32 +10:00

README.md

#ArduPilot Project#

Gitter

The ArduPilot project is made up of:

ArduCopter (or APM:Copter) : code, wiki

ArduPlane (or APM:Plane) : code, wiki

ArduRover (or APMrover2) : code, wiki

Antenna Tracker : code, wiki

User Support & Discussion Forums

APM Forum: http://ardupilot.com/forum/index.php

Community Site: http://diydrones.com

Developer Information

Github repository: https://github.com/diydrones/ardupilot

Main developer wiki: http://dev.ardupilot.com

Developer email group: drones-discuss@googlegroups.com

Contributors

Github statistics

Dronecode.org

ArduPilot is part of Dronecode.org, a Linux Foundation collaborative project.

Dronecode encompasses projects that control flight, enable mission planning, and otherwise make drone flight and advanced functionality possible.

Dronecode development is done at the project level with coordinating and resource allocation performed by the TSC and the Board.

For information on the foundation please visit https://www.dronecode.org and https://github.com/Dronecode for further information or contact celder@dronecode.org

How To Get Involved

The ArduPilot project is open source and we encourage participation and code contributions: guidelines for contributors to the ardupilot codebase

We have an active group of Beta Testers especially for ArduCopter to help us find bugs: release procedures

Desired Enhancements and Bugs can be posted to the issues list.

Helping other users with log analysis on diydrones.com and the APM forums is always appreciated:

There is a group of wiki editors as well in case documentation is your thing: ardu-wiki-editors@googlegroups.com

Developer discussions occur on drones-discuss@google-groups.com

License

Overview of license

Full Text

Maintainers

Ardupilot is comprised of several parts, vehicles and boards. The list below contains the people that regularly contribute to the project and are responsible for reviewing patches on their specific area. See CONTRIBUTING.md for more information.