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

Contributor sign-offs: https://git.card10.badge.events.ccc.de/badge23/firmware/-/issues/5

This is an annoyingly large change, but the gist of it is that we:

1. Move ctx into components/ctx
2. Move uctx into usermodule/mp_uctx.c
3. Split out uctx config into ctx_config.h and share it with the
   simulator.
4. Delete a bunch of unused ctx files
5. Flip some ctx bits for speed.
6. Draw the rest of the owl, ie. implement a dedicated rasterizer task
   in components/st3m.