Threads don’t necessarily share all their memory - thread-local storage is a thing. And even processes can share memory.
I refered to threading to emphasise the difficulty involved in coordination and synchronisation.
Messages don’t necessarily have to be large, but the mechanism for sending and receiving the messages would indeed introduce some overhead.
A full frame is 38,720 pixels, running at 60 fps that would be 2,323,200 pixels per second.
So I suppose it’s plausible, but then you’d potentially need buttons on the hat as well, otherwise the Pokitto’s processor then has to send button data to the hat and it’ll get complicated.
To be honest I think it kind of takes the fun out of it.
May as well stick a screen on the hat and call it a new console. :P
Regular bluetooth would work alright for multiplayer.
Even so it’s a powerful chip in its own right.
14.4 times the amount of SRAM on the Pokitto itself.
3.3 to 5 times the clock speed of the Pokitto’s chip.
That’s a shame. I wonder why there’s such a price disparity?
I found the core for esp8266, which is indeed LGPL:
However it’s not all LGPL, the part inside Arduino/tools/sdk
is licenced under a customised version of the MIT licence.
It’s the same as the MIT licence apart from one aspect:
Permission is hereby granted for use on ESPRESSIF SYSTEMS ESP8266 only
Which would make it suitable for the Pokitto’s use-case but technically not free software.
Also they only distribute that part precompiled, they don’t provide the source code for it.
I also found the ESP32 WiFi stack, which is marked as being under Apache 2.0 but is distributed precompiled, so the source code is not accessible:
This is extremely odd.
Technically both licences allow the code to be distributed precompiled, but it goes against the spirit of the licences.
Furthermore, the licences allow people to modify and reverse engineer the precompiled code,
so precompiling the code just makes modifying it difficult,
legally there’s nothing stopping someone from modifying it.