CircuitPython - a Python implementation for teaching coding with microcontrollers https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=6.1.x 2017-09-06T03:40:51+00:00 2017-09-06T03:40:51+00:00 Damien George damien.p.george@gmail.com 2017-09-06T03:40:51+00:00 urn:sha1:01dd7804b87d60b2deab16712eccb3b97351a9b7 This is to keep the top-level directory clean, to make it clear what is core and what is a port, and to allow the repository to grow with new ports in a sustainable way. 2017-07-31T08:35:40+00:00 Alexander Steffen devel.20.webmeister@spamgourmet.com 2017-06-30T07:22:17+00:00 urn:sha1:55f33240f3d7051d4213629e92437a36f1fac50e There were several different spellings of MicroPython present in comments, when there should be only one. 2017-07-18T01:57:39+00:00 Alexander Steffen devel.20.webmeister@spamgourmet.com 2017-06-29T21:14:58+00:00 urn:sha1:299bc625864b9e624ed599c94a5f95870516139a The code conventions suggest using header guards, but do not define how those should look like and instead point to existing files. However, not all existing files follow the same scheme, sometimes omitting header guards altogether, sometimes using non-standard names, making it easy to accidentally pick a "wrong" example. This commit ensures that all header files of the MicroPython project (that were not simply copied from somewhere else) follow the same pattern, that was already present in the majority of files, especially in the py folder. The rules are as follows. Naming convention: * start with the words MICROPY_INCLUDED * contain the full path to the file * replace special characters with _ In addition, there are no empty lines before #ifndef, between #ifndef and one empty line before #endif. #endif is followed by a comment containing the name of the guard macro. py/grammar.h cannot use header guards by design, since it has to be included multiple times in a single C file. Several other files also do not need header guards as they are only used internally and guaranteed to be included only once: * MICROPY_MPHALPORT_H * mpconfigboard.h * mpconfigport.h * mpthreadport.h * pin_defs_*.h * qstrdefs*.h 2016-12-05T04:14:22+00:00 Damien George damien.p.george@gmail.com 2016-12-05T04:14:22+00:00 urn:sha1:aaab6a9921a9a874d9a974ecc5c3639002dc286b 2015-11-30T13:07:20+00:00 Ryan Shaw ryannathans@hotmail.com 2015-11-27T15:31:59+00:00 urn:sha1:f99491cbf743d51fd2aa7332c0e03da64448d60a 2015-05-27T15:51:04+00:00 Damien George damien.p.george@gmail.com 2015-05-27T15:51:04+00:00 urn:sha1:1775b65e07fae808dc50f9cee2005608cd3a26de Now all stmhal-based boards can name their peripherals (if they want) to any string. 2014-10-21T21:15:20+00:00 Damien George damien.p.george@gmail.com 2014-10-11T16:57:10+00:00 urn:sha1:481d714bd56e0173668b249760e9cea8fce9b04f UART object now uses a stream-like interface: read, readall, readline, readinto, readchar, write, writechar. Timeouts are configured when the UART object is initialised, using timeout and timeout_char keyword args. The object includes optional read buffering, using interrupts. You can set the buffer size dynamically using read_buf_len keyword arg. A size of 0 disables buffering. 2014-07-20T12:57:43+00:00 Damien George damien.p.george@gmail.com 2014-07-20T12:57:43+00:00 urn:sha1:951ed9d02ffc826c68ee3af26c3530477e7e6156 Recent changes to builtin print meant that print was printing to the mp_sys_stdout_obj, which was sending data raw to the USB CDC device. The data should be cooked so that \n turns into \r\n. 2014-05-03T22:27:38+00:00 Damien George damien.p.george@gmail.com 2014-05-03T22:27:38+00:00 urn:sha1:04b9147e150d2d6fa3750f312fe328b6a71c1b28 Blanket wide to all .c and .h files. Some files originating from ST are difficult to deal with (license wise) so it was left out of those. Also merged modpyb.h, modos.h, modstm.h and modtime.h in stmhal/. 2014-04-21T11:03:09+00:00 Damien George damien.p.george@gmail.com 2014-04-21T11:03:09+00:00 urn:sha1:7533700393b4b5d4858e1f5745be4544b2a970cc It's really a UART because there is no external clock line (and hence no synchronous ability, at least in the implementation of this module). USART should be reserved for a module that has "S"ynchronous capabilities. Also, UART is shorter and easier to type :)