<feed xmlns='http://www.w3.org/2005/Atom'>
<title>suspect-devices/circuitpython/shared-module/sharpdisplay/SharpMemoryFramebuffer.h, branch 6.1.0-beta.3</title>
<subtitle>CircuitPython - a Python implementation for teaching coding with microcontrollers</subtitle>
<id>https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=6.1.0-beta.3</id>
<link rel='self' href='https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=6.1.0-beta.3'/>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/'/>
<updated>2020-11-28T16:54:34+00:00</updated>
<entry>
<title>Use movable allocation system for Sharp display framebuffer.</title>
<updated>2020-11-28T16:54:34+00:00</updated>
<author>
<name>Christian Walther</name>
<email>cwalther@gmx.ch</email>
</author>
<published>2020-10-16T21:08:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=ac91220361e402bbf6ebb741a9b6ea258a05da99'/>
<id>urn:sha1:ac91220361e402bbf6ebb741a9b6ea258a05da99</id>
<content type='text'>
Hybrid allocation is now part of the infrastructure. Moving memory contents would not be necessary because displayio can recreate them, but does not hurt.
</content>
</entry>
<entry>
<title>sharpmemory: Implement support for Sharp Memory Displays in framebufferio</title>
<updated>2020-08-12T12:32:18+00:00</updated>
<author>
<name>Jeff Epler</name>
<email>jepler@gmail.com</email>
</author>
<published>2020-08-06T21:03:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=c1400bae9bbdd55f650ddfe24edf6778f08c35b8'/>
<id>urn:sha1:c1400bae9bbdd55f650ddfe24edf6778f08c35b8</id>
<content type='text'>
</content>
</entry>
</feed>
