This seem to break mpremote mount, and I'm not sure why we even want
them.

Renames font constants so they match the indexing used by
ctx_get_font_name.

As requested by moon2. Spikes is the default as that's what p4 uses and
the current code handles decently, spirals is new in p6 and ideally
should have its own implementations for rad and phi, right now it has
placeholders.

It was never actually supported by the codebase (the port expanders are
completely different and only implemented in the other repo)

Yeah I'm aware all of this can change any time, yell at me if it's a
problem.

Previously MicroPython would mount LittleFS directly from the partition
by itself, using its own VFS stack.

This reconfigured the VFS layer in MicroPython to use POSIX
open/read/write/etc calls, which are backed by ESP-IDF. Now, instead of
managing (possibly multuple) block devices at different mountpoints,
MicroPython simply passes through all VFS access to the ESP-IDF VFS.

Then, we make the ESP-IDF VFS mount a wear-leveled FAT (backed by the
same partition which previously held LittleFS) onto /.

q3k authored 1 year ago and q3k committed 1 year ago

Having lurked some FreeRTOS forum threads, it seems like this is
preferable to the previous approach (timer unblocking a thread using a
queue/semaphore), as it's less resource-intense and doesn't cause a
global timer pileup if one of the tasks causes backpressure.

This is a random commit that might help us chase out Core 0 WDT
interrupts.

Tested on p3.

also:  writing and reading calib data to/from json file, optional background for ui.Viewport

The stub seems to break uploading from running firmware on newer
ESP-IDFs.

There's a better way to fix this by patching esptool.py, but this is
good enough for now.

https://www.esp32.com/viewtopic.php?t=10184#p42176