Skip to content

fix(kode): Start the rows above the renderer's priority - #107

Merged
jbenedictocenteno merged 1 commit into
developfrom
fix/rows-above-renderer
Nov 13, 2026
Merged

jbenedictocenteno merged 1 commit into
developfrom
fix/rows-above-renderer

Conversation

@jbenedictocenteno

Copy link
Copy Markdown
Contributor

Description of Change

The boot task runs every owner's initial transition at priority 1. The renderer starts in the early row at priority 3 and draws without a pause. Where the port puts it on the boot task's core, the walk got only the gaps between its passes, and the console and the owners below the early row came up as much as 2.6 s late.

kode_sys_rows_walk() now runs one level above the renderer and gives the boot task its priority back when the walk ends.

Test Scenarios

  • tools/host_tests.sh and tools/check_layers.sh, green at this branch.
  • DVT board e8:f6:0a:e7:6b:d5, kodeOS built with this change: on a board where 21 boots of 30 were slow, 60 of 60 brought the console up in 0.31 s, with the first frame where it was. Later runs of the same series: 100 of 100 and 40 of 40 at 0.30 s.

Related links

Closes #70

The boot task runs every owner's initial transition at priority 1. The
renderer starts in the early row at priority 3 and draws without a
pause. Where the port puts it on the boot task's core, the walk got only
the gaps between its passes, and the console and the owners below the
early row came up as much as 2.6 s late.

kode_sys_rows_walk() runs one level above the renderer and gives the
boot task its priority back. On a board where 21 boots of 30 were slow,
60 of 60 bring the console up in 0.31 s, with the first frame where it
was.

Closes #70
@jbenedictocenteno
jbenedictocenteno merged commit 79d2e35 into develop Nov 13, 2026
1 of 7 checks passed
@jbenedictocenteno
jbenedictocenteno deleted the fix/rows-above-renderer branch November 13, 2026 10:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

One boot in ten takes 2.7 s to start the owners: the boot task waits behind AO_Gui on core 0

1 participant