<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openmano-mpy/cc3200/mpthreadport.h, branch master</title>
<subtitle>MicroPython source and hardware configuration for OpenMano</subtitle>
<link rel='alternate' type='text/html' href='https://git.0x7felf.com/openmano-mpy/'/>
<entry>
<title>ports: Make new ports/ sub-directory and move all ports there.</title>
<updated>2017-09-06T03:40:51+00:00</updated>
<author>
<name>Damien George</name>
</author>
<published>2017-09-06T03:40:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.0x7felf.com/openmano-mpy/commit/?id=01dd7804b87d60b2deab16712eccb3b97351a9b7'/>
<id>01dd7804b87d60b2deab16712eccb3b97351a9b7</id>
<content type='text'>
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.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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.
</pre>
</div>
</content>
</entry>
<entry>
<title>all: Unify header guard usage.</title>
<updated>2017-07-18T01:57:39+00:00</updated>
<author>
<name>Alexander Steffen</name>
</author>
<published>2017-06-29T21:14:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.0x7felf.com/openmano-mpy/commit/?id=299bc625864b9e624ed599c94a5f95870516139a'/>
<id>299bc625864b9e624ed599c94a5f95870516139a</id>
<content type='text'>
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
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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
</pre>
</div>
</content>
</entry>
<entry>
<title>cc3200: Allow to compile bootloader with threading enabled.</title>
<updated>2016-06-28T10:28:53+00:00</updated>
<author>
<name>Damien George</name>
</author>
<published>2016-06-28T10:25:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.0x7felf.com/openmano-mpy/commit/?id=842c2c74c02d5ad0b409cda2fd6e64f339b45ba9'/>
<id>842c2c74c02d5ad0b409cda2fd6e64f339b45ba9</id>
<content type='text'>
Threading is not used in the bootloader but the config optios are still
enabled so we must exclude including FreeRTOS.h.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Threading is not used in the bootloader but the config optios are still
enabled so we must exclude including FreeRTOS.h.
</pre>
</div>
</content>
</entry>
<entry>
<title>cc3200/mpthreadport: Make mutex statically allocated.</title>
<updated>2016-06-28T10:28:52+00:00</updated>
<author>
<name>Damien George</name>
</author>
<published>2016-05-31T16:28:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.0x7felf.com/openmano-mpy/commit/?id=27241293c4f5ae26927f70fe03cdd86fa1819aa1'/>
<id>27241293c4f5ae26927f70fe03cdd86fa1819aa1</id>
<content type='text'>
Reduced the need for the FreeRTOS heap to allocate the mutex.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Reduced the need for the FreeRTOS heap to allocate the mutex.
</pre>
</div>
</content>
</entry>
<entry>
<title>cc3200: Add basic threading capabilities.</title>
<updated>2016-06-28T10:28:51+00:00</updated>
<author>
<name>Damien George</name>
</author>
<published>2016-05-27T16:35:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.0x7felf.com/openmano-mpy/commit/?id=eef4f13a3390dc88902563acb047f0439eff0caf'/>
<id>eef4f13a3390dc88902563acb047f0439eff0caf</id>
<content type='text'>
Can create a new thread and run it.  Does not use the GIL at this point.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Can create a new thread and run it.  Does not use the GIL at this point.
</pre>
</div>
</content>
</entry>
</feed>
