Red Bear OS
6c980c2dfd
The previous "outer: bump local/sources/{kernel,base} submodules"
commit (9381ed4fd) showed the diff for the kernel gitlink in
git show output, but the outer repo's .gitmodules file did NOT
register local/sources/kernel as a real submodule. This meant the
pointer change in 9381ed4fd was a working-tree-only edit, never
actually committed to the outer repo's index.
This commit rectifies the inconsistency: register
local/sources/kernel in .gitmodules pointing at the Red Bear gitea
fork (https://gitea.redbearos.org/vasilito/redbear-os-kernel.git),
then bump it to the Phase G.3 commit (19010ce) which adds the
MWAIT idle_loop.
For the LG Gram 2025 / Arrow Lake-H this matters: the existing
enable_and_halt() path lands the CPU in C1 only. The new MWAIT
idle_loop enters the deepest available C-state (C6/C7/C8/C9/C10/S0iX),
which dramatically reduces idle power on real hardware.
Note: local/sources/base is a separate git repo without a
.gitmodules entry; it works in practice because the
"outer: bump local/sources/{kernel,base} submodules" commit
captures its diff as a subproject change in the commit object,
but the working tree is never updated. A follow-up could add a
.gitmodules entry for base too, but the current approach has
worked for the prior base commits (8cd4f69's diff-via-base
and earlier 4f2a043 re-sync).
This is the SECOND commit to track the same kernel submodule
bump (cf. 9381ed4fd which only captured the change in tree
state). The previous commit was effectively informational only;
this one makes the change permanent in the outer index.
4 lines
130 B
Plaintext
4 lines
130 B
Plaintext
[submodule "local/sources/kernel"]
|
|
path = local/sources/kernel
|
|
url = https://gitea.redbearos.org/vasilito/redbear-os-kernel.git
|