agessaman dc539d2dd6 kiss_modem: answer FEM requests strictly in arrival order ...

A second SetFemState sent while the first was held for a TX got an
immediate TxBusy, which reached the host before the first request's
reply. With no request IDs, the host could not tell which Set failed.

FEM requests now go through a small ordered queue (Set, Get and their
error replies). Sets still wait for TxDone to be queued and apply
once. Each reply is kept until it can be queued. Capability checks
happen in order at processing time. Only an overflow (more than 4
waiting) replies TxBusy immediately.

2026-09-23 17:41:14 -07:00

..

companion_radio

missing board.loop() in companion, room server, kiss modem.

2026-09-22 18:01:15 +10:00

kiss_modem

kiss_modem: answer FEM requests strictly in arrival order

2026-09-23 17:41:14 -07:00

simple_repeater

Add board loop hook for periodic work

2026-09-22 08:01:48 +02:00

simple_room_server

missing board.loop() in companion, room server, kiss modem.

2026-09-22 18:01:15 +10:00

simple_secure_chat

Ensure command buffers stay NUL-terminated to prevent overflow

2026-09-04 20:01:39 +01:00

simple_sensor

Merge pull request #3131 from liekmarflow/feature/board-api-hooks

2026-09-22 16:43:18 +10:00