mirror of
https://github.com/trezor/trezor-firmware.git
synced 2024-12-18 20:38:10 +00:00
6f53ca0ac6
The original wait_layout was unreliable, because there are no guarantees re order of arrival of the respective events. Still, TT's event handling is basically deterministic, so as long as the host sent its messages close enough to each other, the order worked out. This is no longer the case with the introduction of loop.spawn: TT's behavior is still deterministic, but now ButtonAck is processed *before* the corresponding wait_layout, so the waiting side waits forever. In the new process, the host must first register to receive layout events, and then receives all of them (so the number of calls to wait_layout must match the number of layout changes). DebugLinkWatchLayout message must be version-gated, because of an unfortunate collection of bugs in previous versions wrt unknown message handling; and this interests us because upgrade-tests are using wait_layout feature. |
||
|---|---|---|
| .. | ||
| .gitignore | ||
| Makefile | ||
| messages_map.py | ||
| messages-bitcoin.options | ||
| messages-bitcoin.proto | ||
| messages-common.options | ||
| messages-common.proto | ||
| messages-crypto.options | ||
| messages-crypto.proto | ||
| messages-debug.options | ||
| messages-debug.proto | ||
| messages-ethereum.options | ||
| messages-ethereum.proto | ||
| messages-lisk.options | ||
| messages-lisk.proto | ||
| messages-management.options | ||
| messages-management.proto | ||
| messages-nem.options | ||
| messages-nem.proto | ||
| messages-stellar.options | ||
| messages-stellar.proto | ||
| messages.options | ||
| messages.proto | ||