<feed xmlns='http://www.w3.org/2005/Atom'>
<title>suspect-devices/circuitpython/esp8266/ets_alt_task.h, branch esp-extra-scripts</title>
<subtitle>CircuitPython - a Python implementation for teaching coding with microcontrollers</subtitle>
<id>https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=esp-extra-scripts</id>
<link rel='self' href='https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=esp-extra-scripts'/>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/'/>
<updated>2016-06-01T16:26:49+00:00</updated>
<entry>
<title>esp8266: Provide a dedicated variable to disable ets_loop_iter.</title>
<updated>2016-06-01T16:26:49+00:00</updated>
<author>
<name>Damien George</name>
<email>damien.p.george@gmail.com</email>
</author>
<published>2016-06-01T16:26:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=927388e80ecac345147597c1d7a53b0c1848f609'/>
<id>urn:sha1:927388e80ecac345147597c1d7a53b0c1848f609</id>
<content type='text'>
So ets_loop_iter is now only disabled when using machine.disable_irq.
</content>
</entry>
<entry>
<title>esp8266: Add alternative event loop implementation.</title>
<updated>2016-03-11T02:13:31+00:00</updated>
<author>
<name>Paul Sokolovsky</name>
<email>pfalcon@users.sourceforge.net</email>
</author>
<published>2015-12-21T21:04:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=97c262890058896b0acd735b54d66d9ea19c3a53'/>
<id>urn:sha1:97c262890058896b0acd735b54d66d9ea19c3a53</id>
<content type='text'>
This implementation provides the same interface and uses the same
datastructures as used by BootROM, i.e. is a drop-in replacement for it.
But it offers one advantage: it allows to run single iteration of
event-pumping loop.

Original BootROM function are renamed, prefixed with underscore. There's
a switch which allows to use forward calls to them, for compatibility
testing.

The implementation also includes workarounds for hardware timer handler,
and these workarounds may be SDK version specific.
</content>
</entry>
</feed>
