- Sydney, Australia
- https://micl.dev
-
Joined on
2026年04月23日
a4b5b13505
nrf53: Initial support
79ad43c765
misc: Bumped the meson out of Git version to v2.1.0-rc1
631a5de13e
meson: Disabled building of support for TI parts by default for ST-Link v1 firmware to make things fit again
7fc83d2c73
ch32vx: Fixed a missing
static on the command list
b624393ac6
efm32: Fixed a missing
static on the command list
dbdca3114f
nrf53: Initial support
2129a32419
meson: Moved the building of support for TI parts by default from the BMPv2 common targets firmare to the uncommon targets irmware to make things fit again
4ec2041d3e
meson: Disabled building of support for TI parts by default for the F072 firmware to make things fit again
09003e4b05
bmp-v3: Fixed the platform mis-reporting when target power is applied (it was backwards)
6bfecfab57
stm32f1: Detect locked AT32F403A/407 to allow unlocking
nrf53: Initial support
660f6226b0
nrf53: Initial support
e04459bb5b
nrf53: Initial support
c87703c7b3
nrf53: Initial support
ca1fc6df5a
nrf53: Initial support
[Research] Plug-in System
I don't think the IPC security is as strong as stated. In this model a malicious IPC plugin could be anything, and the user would have to vet each plugin. You'd still need proper sandboxing on top...
[Research] Plug-in System
I think Lua would be a good choice. The packaging argument is decisive for me, if C plugins are shared libraries (dlopen) they effectively become part of kew's ABI, which has consequences...