<feed xmlns='http://www.w3.org/2005/Atom'>
<title>suspect-devices/circuitpython/shared-module/rgbmatrix/RGBMatrix.c, branch 6.2.x</title>
<subtitle>CircuitPython - a Python implementation for teaching coding with microcontrollers</subtitle>
<id>https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=6.2.x</id>
<link rel='self' href='https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=6.2.x'/>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/'/>
<updated>2021-03-15T13:57:36+00:00</updated>
<entry>
<title>run code formatting script</title>
<updated>2021-03-15T13:57:36+00:00</updated>
<author>
<name>microDev</name>
<email>70126934+microDev1@users.noreply.github.com</email>
</author>
<published>2021-03-15T13:57:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=a52eb88031620a81521b937f2a0651dbac2bb350'/>
<id>urn:sha1:a52eb88031620a81521b937f2a0651dbac2bb350</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Enable protomatter on RP2040 builds</title>
<updated>2021-02-12T14:25:15+00:00</updated>
<author>
<name>Jeff Epler</name>
<email>jepler@gmail.com</email>
</author>
<published>2021-02-11T22:37:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=ff1942cff68a4e192f984a14a83b59800186e45a'/>
<id>urn:sha1:ff1942cff68a4e192f984a14a83b59800186e45a</id>
<content type='text'>
Also found a race condition between timer_disable and redraw, which
would happen if I debugger-paused inside common_hal_rgbmatrix_timer_disable
or put a delay or print inside it.  That's what pausing inside reconstruct
fixes.

So that the "right timer" can be chosen, `timer_allocate` now gets the `self`
pointer.  It's guaranteed at this point that the pin information is accurate,
so you can e.g., find a PWM unit related to the pins themselves.
This required touching each port to add the parameter even though it's
unused everywhere but raspberrypi.
</content>
</entry>
<entry>
<title>rgbmatrix: Eliminate some duplicated height-calculating code</title>
<updated>2021-01-26T20:35:26+00:00</updated>
<author>
<name>Jeff Epler</name>
<email>jepler@gmail.com</email>
</author>
<published>2021-01-26T20:35:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=20c9f25a654df33e4fb719edfeaad8c4d4396f5e'/>
<id>urn:sha1:20c9f25a654df33e4fb719edfeaad8c4d4396f5e</id>
<content type='text'>
This was hard to write, so let's have it written in 2 places instead
of 4.
</content>
</entry>
<entry>
<title>RGBMatrix: Additional tile tweaks</title>
<updated>2021-01-26T20:33:48+00:00</updated>
<author>
<name>Jeff Epler</name>
<email>jepler@gmail.com</email>
</author>
<published>2021-01-26T20:33:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=368977fb906e6561bd67977a47dc0b415547cc33'/>
<id>urn:sha1:368977fb906e6561bd67977a47dc0b415547cc33</id>
<content type='text'>
 * Introduce explicit serpentine: bool argument instead of using negative
   numbers (thanks, ghost of @tannewt sitting on one shoulder)
 * Fix several calculations of height

Testing performed (matrixportal):
 * set up a serpentine 64x64 virtual display with 2 64x32 tiles
 * tried all 4 rotations
 * looked at output of REPL
</content>
</entry>
<entry>
<title>protmatter: Update to version that supports tiling</title>
<updated>2021-01-26T15:19:44+00:00</updated>
<author>
<name>Jeff Epler</name>
<email>jepler@gmail.com</email>
</author>
<published>2021-01-26T15:19:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=51f054440516d21bd2e8d07a3e6f1f8e3acfbd55'/>
<id>urn:sha1:51f054440516d21bd2e8d07a3e6f1f8e3acfbd55</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Use movable allocation system for RGBMatrix allocations.</title>
<updated>2020-11-28T16:54:34+00:00</updated>
<author>
<name>Christian Walther</name>
<email>cwalther@gmx.ch</email>
</author>
<published>2020-10-17T11:49:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=a4b84cf0e118f06cc3b563866d5c594b94b9b3fb'/>
<id>urn:sha1:a4b84cf0e118f06cc3b563866d5c594b94b9b3fb</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>Add movable allocation system.</title>
<updated>2020-11-28T16:50:23+00:00</updated>
<author>
<name>Christian Walther</name>
<email>cwalther@gmx.ch</email>
</author>
<published>2020-10-11T12:59:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=c7404a3ff89c738c002ec63448a58d56330dfcc3'/>
<id>urn:sha1:c7404a3ff89c738c002ec63448a58d56330dfcc3</id>
<content type='text'>
This allows calls to `allocate_memory()` while the VM is running, it will then allocate from the GC heap (unless there is a suitable hole among the supervisor allocations), and when the VM exits and the GC heap is freed, the allocation will be moved to the bottom of the former GC heap and transformed into a proper supervisor allocation. Existing movable allocations will also be moved to defragment the supervisor heap and ensure that the next VM run gets as much memory as possible for the GC heap.

By itself this breaks terminalio because it violates the assumption that supervisor_display_move_memory() still has access to an undisturbed heap to copy the tilegrid from. It will work in many cases, but if you're unlucky you will get garbled terminal contents after exiting from the vm run that created the display. This will be fixed in the following commit, which is separate to simplify review.
</content>
</entry>
<entry>
<title>Merge pull request #3537 from jepler/update-protomatter-2</title>
<updated>2020-10-12T22:45:51+00:00</updated>
<author>
<name>Scott Shawcroft</name>
<email>scott@adafruit.com</email>
</author>
<published>2020-10-12T22:45:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=1eb1434fc968cb05e3cfd69b40434331404ef5df'/>
<id>urn:sha1:1eb1434fc968cb05e3cfd69b40434331404ef5df</id>
<content type='text'>
rgbmatrix: update protomatter to 1.0.5 tag</content>
</entry>
<entry>
<title>rgbmatrix: Don't crash when setting brightness=0</title>
<updated>2020-10-12T18:28:20+00:00</updated>
<author>
<name>Jeff Epler</name>
<email>jepler@gmail.com</email>
</author>
<published>2020-10-12T18:26:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=9696dbfd388aa4c21b686d4566832964c31f8035'/>
<id>urn:sha1:9696dbfd388aa4c21b686d4566832964c31f8035</id>
<content type='text'>
If the display is paused, `_PM_swapbuffer_maybe` will never return.
So, when brightness is 0, refresh does nothing.  This makes it necessary
to update the display when unpausing.

Closes: #3524
</content>
</entry>
<entry>
<title>rgbmatrix: update protomatter to 1.0.5 tag</title>
<updated>2020-10-10T19:30:37+00:00</updated>
<author>
<name>Jeff Epler</name>
<email>jepler@gmail.com</email>
</author>
<published>2020-10-10T19:30:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=5e38bb98cbcc2d1ab607b19d11e628def4f48f4c'/>
<id>urn:sha1:5e38bb98cbcc2d1ab607b19d11e628def4f48f4c</id>
<content type='text'>
this is compile-tested on
 stm32f405 feather
 matrixportal
 nrf52840 feather

but not actually tested-tested.
</content>
</entry>
</feed>
