Philip Howard

Figuring out where to start is on my TODO list. I'm a fan of CircuitPython but we can't just bake our libraries in and ship our own version like we're...

Specifically we would need to (and this is very off the top of my head so it may be wrong/incomplete): 1. [ ] Verify there is upstream support for the...

I think this will explode since all surface manipulation must now go via `set_pixel` for a single pixel or `set_pixel_span` for a horizontal span. The actual framebuffer is now `void...

That was, uh, planned: https://github.com/pimoroni/pimoroni-pico/blob/82756a3fc99dd587ef2b77d629748e713dd4074f/micropython/modules/jpegdec/jpegdec.cpp#L129 But yes RGB332 mode should support quantized output.

Should be fixed by #492 If you grab the appropriate build from https://github.com/pimoroni/pimoroni-pico/actions/runs/2839220919 and call decode like so: `jpeg.decode(0, 0, dither=False)` then it should posterise to the RGB332 colourspace instead.

Ooh good catch I was waiting for this to end up in a release, apparently time flies. Pending in a PR- test build available here: https://github.com/pimoroni/pimoroni-pico/actions/runs/2281363972

I've tried adding the "generic_micropython" dir to the modules. Right now the code that handles this is awful, but it *should* copy over just enough of a - stripped down...

I can't see why it would collapse, but it's fair to say that the Blinka/PlatformDetect compatibility layer is a little bit of a gamble so I am not surprised. Let...

I have a suspicion that we've just blown the maximum binary size by baking these files into the firmware- so the first thing MicroPython does on launch (or if any...

Sorry for the lack of response here, Pico W has been causing me all kinds of headaches. I'm apprehensive about allocating too much RAM here since I keep running into...