| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
Really this should be installed as a proper pygments style and selected
as such in conf.py. The way this patch works two full .css files get
loaded and the second (solarized) clobbers the default.
|
|
|
|
|
|
| |
If the 'breath' python package (for doxygen => sphinx bridging) is
installed system-wide, builds would fail because the system version had
priority.
|
|
|
|
| |
Still needs bundled fonts and polish.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the past, libample documentation was forked out of this repository
because the documentation had increased in scope. For the librambutan,
and the rambutan project in general, we will try to keep documentation
closer to the source code, so the librambutan-specific documentation
should live here. Other sections of leaflabs-docs will be culled in a
following commit.
This merge attempts to maintain history by using a subtree strategy.
Followed directions at:
http://nuclearsquid.com/writings/subtree-merging-and-you/
Full history for files should be accessible using the "--follow" flag to
git log, eg:
git log --follow docs/source/adc.rst
It should be possible to pull patches from leaflabs-docs with:
git pull -s subtree leaflabs-docs master
... at least until the docs in this repository diverge significantly.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The documentation covers topics not specifically relevant to libmaple,
so it doesn't make sense for it to be part of the libmaple source
distribution.
Delete the docs/ tree, and prepare libmaple for use with the new
leaflabs-docs repo, which will contain the docs from now on.
* README: update to reflect this change
* support/doxygen/Doxyfile: This is the old docs/Doxyfile
* Makefile: Add a doxygen target
* wirish/comm/HardwareSerial.h: fix reference to docs/. The comment
informing maintainers that the HardwareSerial interface is
documented by hand refers to the docs/ tree, which no longer exists.
Update it to refer to the separate leaflabs-docs repository.
* support/scripts/copy-to-ide: No longer build the documentation
|
| |
|
| |
|
| |
|
|
|
|
|
| |
ASSERT() was previously documented in language.rst. Move it to a new
lang/api/assert.rst.
|
|
|
|
|
|
| |
The FAQ entry which explains the throbbing LED behavior is
insufficiently general. Rewrite it so users can tell that throbbing
generally indicates a failed assertion or some other error.
|
|
|
|
|
|
| |
Fix examples where pin 13 was used explicitly instead of
BOARD_LED_PIN. Also change an AVR-specific example in
docs/lang/cpp/booleanvariables.rst to Maple conventions.
|
|
|
|
| |
Thanks to forum user AndyH for the suggestion.
|
| |
|
|
|
|
| |
Thanks to forum user AndyH for the corrections.
|
|
|
|
|
| |
This is a pretty brain-dead way to manage these pre-release
preparations. Should figure out the done thing and use that instead.
|
| |
|
|
|
|
|
| |
Make the language a little friendlier, say the words "serial port",
and let them know that baud rate is a speed.
|
|
|
|
|
|
| |
Make the note warning against its usage more direct. Add a blurb
introducing its purpose and links in See Also to related
board-specific values.
|
|
|
|
| |
Slightly reorganize to keep it consistent with the rest of the docs.
|
|
|
|
|
| |
Make the language friendlier; point to GPIO port definition for an
explanation of the EXTI line definition.
|
| |
|
|
|
|
|
| |
Add a section about GPIO ports, since that existed nowhere. Made a
ref for 5V tolerance. Other clarifications and improvements.
|
|
|
|
| |
Convert to board-specific values; make the language friendlier.
|
|
|
|
|
| |
10-bit addressing has now been implemented. Slave mode is
unimplemented, however.
|
|
|
|
|
| |
It did, but there was no jumper to cut power from the charging
circuit, resulting in weird blinky behavior that was fixed in Rev 3.
|
| |
|
|
|
|
| |
Vdda, not Vcc.
|
| |
|
| |
|
|
|
|
|
| |
This should get changed on each release branch when the time comes. A
FIXME comment has been added to that effect.
|
|
|
|
|
| |
These two examples from board-values.rst really belong in the
documentation for the functions they reference.
|
|
|
|
|
| |
Flesh out and uncomment maple-mini.rst. Add links to pieces of it in
various appropriate places throughout the rest of the documentation.
|
|
|
|
|
|
|
|
|
|
| |
Pick a standard layout for the information and fix mistakes. Looks
like some of these errors were copy-pasted in from the old HTML
documentation, some crept in due to API changes, and some were just
wrong.
I've checked all the claims against the datasheets and source code, so
we should be in good shape now.
|
|
|
|
| |
Mostly, make it less pedantic. Also some stylistic and content fixes.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
In line with some changes made earlier today to the maple-ide repo,
the master libmaple branch no longer points to a particular IDE
release as "current", since there's no way it can know. From now on,
only release branches will contain the blessed download links.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|