Mirror
/
ardupilot
mirror of https://github.com/ArduPilot/ardupilot
5
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
42,639 Commits 71 Branches 509 Tags 763 MiB
Commit Graph

14 Commits

Author SHA1 Message Date
Peter Barker 4647c6ef62 StorageManager: use pragmas to set storage layout rather than call 
We don't need the flexibility to reset this, it's a waste of bytes and
something that could go wrong.  AP_Periph led the way with using
pragmas here.
 2020-01-28 11:34:51 +11:00
Peter Barker 8469efc5aa StorageManager: use https:// scheme for ardupilot URLs 2019-12-10 07:53:46 +11:00
Siddharth Purohit 4034af6ef1 StorageManager: add storage aread for CAN Dynamic Node Alloc 2019-10-19 09:55:38 +11:00
Peter Barker f1e5c72ee9 StorageManager: add write_uint8 alias for write_byte 2019-09-28 07:58:48 +09:00
Andrew Tridgell d005f066a9 StorageManager: enable use of a single storage region 2019-08-27 10:29:56 +10:00
Andrew Tridgell b983caa97e StorageManager: allow for 15k storage 
this is for F4 boards using flash storage. They were using 8k, but can
actually fit 16k. This is optimised for lots of param space as we
expect to have a lot of customised params for OSD support
 2018-06-24 08:26:28 +10:00
Andrew Tridgell ac324a3760 StorageManager: added bind info storage area 2018-02-08 17:36:33 +11:00
Mathieu OTHACEHE 152edf7189 Global: remove mode line from headers 
Using a global .dir-locals.el file is a better alternative than
reincluding the same emacs header in every file of the project.
 2016-10-24 09:42:01 -02:00
Andrew Tridgell ca39ece6cb StorageManager: added storage region for signing keys 2016-05-21 15:25:12 +10:00
Luis Vale Gonçalves bbbb3047fa Revising ardupilot.com to .org 
Revising ardupilot.com to .org
 2016-04-23 22:49:40 -07:00
Lucas De Marchi bf9cf74c38 StorageManager: replace header guard with pragma once 2016-02-18 14:52:35 -02:00
Gustavo Jose de Sousa ce0cb248ce StorageManager: standardize inclusion of libaries headers 
This commit changes the way libraries headers are included in source files:

 - If the header is in the same directory the source belongs to, so the
 notation '#include ""' is used with the path relative to the directory
 containing the source.

 - If the header is outside the directory containing the source, then we use
 the notation '#include <>' with the path relative to libraries folder.

Some of the advantages of such approach:

 - Only one search path for libraries headers.

 - OSs like Windows may have a better lookup time.
 2015-08-11 16:38:25 +10:00
Andrew Tridgell 52cdd6394f StorageManager: cope with a wider range of storage sizes 2014-08-13 21:35:26 +10:00
Andrew Tridgell 66a21c4c33 StorageManager: first version of storage management library 
used to divvy up eeprom/fram and allow for expandable storage
 2014-08-13 18:29:04 +10:00