Jade Mattsson

> I feel that whatever we do on the ESP32 side we should leave the ESP8266 APIs as is. I agree. The API there is the way it is for...

I'd quite like to have us settle on some sort of standard naming convention. It's all a bit of a mess at the moment. Something like - Functions consisting of...

> I never tried but does @jmattsson's BT module for ESP32 support all you'd need? Nah, it only handles sending/receiving BT advertisements. Having "real" BT support would certainly be nice...

Definitely defer this, I'd say. While I absolutely agree it's something that _should_ get done, let's get all the big LVM stuff landed and settled. I'd like to get to...

It's still on my todo list, just like last year >.< On Sun, 31 Jan 2021 at 17:18, M.K. wrote: > Any news on this? > > — > You...

IIRC (and it's been years since I worked in this area), the sleep time limitation came from the 32bit registers used to configure the chip for wakeup.

Based on that error message, it looks to me like either `lua_tounsigned()` is still trying to fit it into a signed 32bit integer (max value 2147483648), or the `lua_isinteger()` is...

That does sound tempting considering the hardware we're running on.

Two comments (other than "good job!") so far: 1. Pretty please with sugar on the top, don't `#include C_HEADER_STDIO` in the final stuff; Let's do the cleanup on the ESP8266...

1. It shouldn't be too bad. As the first stage, simply renaming our `c_whatever.h` files to `whatever.h` and using `-nostdinc` will preference our "standard C" headers. Adding a `-isystem "$(xtensa-lx106-elf-gcc...