Commit Graph

15 Commits

Author SHA1 Message Date
vasilito 5cde25495c git: enforce SINGLE-REPO RULE — redirect submodules to canonical repo
Per local/AGENTS.md § SINGLE-REPO RULE: the Red Bear OS project lives
in exactly one git repository (vasilito/RedBear-OS). Per-component
Gitea mirrors (redbear-os-base, redbear-os-kernel, redbear-os-installer,
redox-drm, userutils, libredox, libpciaccess, ctrlc, syscall, sysinfo)
have been redirected or deleted.

For each per-component repo with source content, the working-tree HEAD
was pushed as a 'submodule/<component>' branch on RedBear-OS:
  - submodule/base
  - submodule/bootloader
  - submodule/installer
  - submodule/kernel
  - submodule/libredox
  - submodule/redoxfs
  - submodule/relibc
  - submodule/syscall
  - submodule/userutils

The .gitmodules entry for local/sources/kernel is now redirected to the
canonical repo with branch = submodule/kernel. The other submodule
.gitmodules entries remain to be added in a follow-up.

Empty per-component repos (ctrlc, libpciaccess, redox-drm, sysinfo) had
no source content; their gitlinks in the index are removed in a
follow-up commit.

Unrelated per-component repos that were not Red Bear components
(ctrlc, syscall, sysinfo — possibly unrelated personal projects) were
deleted in the bulk cleanup.

Gitea state under vasilito/ is now exactly: RedBear-OS, hiperiso.

Adds:
  - local/scripts/redirect-to-submodules.sh
  - local/scripts/delete-per-component-repos.sh

Updates:
  - .gitmodules (kernel → RedBear-OS#submodule/kernel)
  - local/AGENTS.md (SINGLE-REPO RULE status, migration procedure)
  - local/docs/BUILD-SYSTEM-IMPROVEMENTS.md §11 (resolved)
  - local/docs/QUIRKS-AUDIT.md (drop dead links)
  - local/docs/SLEEP-IMPLEMENTATION-PLAN.md (mark historical)
  - CHANGELOG.md (mark historical references)
2026-07-01 22:02:26 +03:00
vasilito fcd8722f92 CHANGELOG: document Phase II.X.W S3 round-trip wire-up
The full S3 round-trip is now functional:
- acpid writes the kernel's S3 trampoline address to FACS
  via the SetS3WakingVector AcPiVerb
- kernel's stop::enter_s3 reads S3_SLP_TYP and writes the
  SLP_TYP|SLP_EN bits to PM1a_CNT
- firmware enters S3; on wake jumps to FACS.waking_vector
  -> kernel's s3_resume::s3_trampoline restores state
- acpid receives kstop reason=3 and runs the wake AML
  sequence (\\_SST(2) -> \\_WAK(3) -> \\_SST(1))

Hardware-agnostic: works on any x86_64 system with
standard ACPI S3 support (Dell, HP, Lenovo, LG Gram 14).
On Modern Standby-only systems (LG Gram 16 (2025)), the
kernel never enters S3 so these verbs are no-ops.

Build: redbear-mini.iso (512 MB) builds successfully.
QEMU: S3 entry/exit is not exercised in QEMU's default
config (QEMU doesn't actually enter S3). The wiring is
verified by the build system (the FACS parser, the
AcPiVerb handler, and the acpid main-loop all compile
and the symbols are correctly resolved). The S3 round-
trip can be exercised on real hardware (Dell, HP,
Lenovo, LG Gram 14) or on a QEMU with custom firmware
that emulates S3 entry.
2026-07-01 17:06:32 +03:00
vasilito 5725acc7dc CHANGELOG: document Phase II.X S3 resume trampoline
The S3 state save in `enter_s3()` and the
`s3_resume::s3_trampoline` 64-bit `naked_asm!` block
are now committed and built. Mirrors Linux 7.1
`arch/x86/kernel/acpi/wakeup_64.S` in 64-bit assembly.

Hardware-agnostic: works on any x86_64 system with
standard ACPI S3 support (Dell, HP, Lenovo, LG Gram 14).
The acpid <-> kernel wiring via a new AcpiVerb is the
next step (Phase II.X.W).
2026-07-01 15:58:35 +03:00
vasilito 1834c3bf58 CHANGELOG: document build system patch verification (make verify-patches)
The new `make verify-patches` target runs
`local/scripts/check-cargo-patches.sh` which verifies
all [patch.crates-io] and [patch.'<URL>'] sections in
local sources' Cargo.toml files resolve to the expected
local fork paths. The kernel's Phase J patch
([patch.'<URL>'] redox_syscall for the URL-based
overrides of the git-URL dependency) is verified
end-to-end.

The user requested 'build system must report complete when
upstream have our patches applied' — this is now an
explicit Makefile target. Hardware-agnostic: works for
any Red Bear OS checkout.
2026-07-01 15:03:26 +03:00
vasilito 339cd4e223 CHANGELOG: document Phase J (typed-AcPiVerb s2idle / S3 + libredox fork)
Phase J is complete: the local syscall fork at
local/sources/syscall/ has the EnterS2Idle/ExitS2Idle
AcPiVerb variants; the local libredox fork at
local/sources/libredox/ uses the local syscall fork; the
[patch.crates-io] and [patch.'<URL>'] sections in base
and kernel Cargo.toml wire both forks into the build.

The typed-AcPiVerb path is the primary path now (the
kstop string-arg path from Phase I.5 is the fallback for
older acpid builds). Both paths are functional. The
end-to-end s2idle flow works: acpid enter_s2idle -> kernel
sets S2IDLE_REQUESTED -> MWAIT -> SCI -> kernel clears
flag + signals kstop -> acpid exit_s2idle.

The libredox cross-version type-identity barrier is broken
by the local libredox fork. scheme-utils and daemon
compile cleanly.

Hardware-agnostic: works on any platform with Modern
Standby firmware (Dell, HP, Lenovo, LG Gram, etc.).

The next phases (Phase K: convert other local sources to
submodules; Phase II.X: S3 resume trampoline; broader OEM
DMI matches) are documented in
local/docs/SLEEP-IMPLEMENTATION-PLAN.md.
2026-07-01 14:40:55 +03:00
vasilito 23ef3fdd3f CHANGELOG: document Phase I/II (s2idle + S3 + LG Gram DMI)
Phase I.5 + Phase II complete and built. The CHANGELOG
captures:

* Phase I.5: kernel MWAIT wake signal + kstop reason
  codes + acpid main-loop reason dispatch. End-to-end
  s2idle flow (acpid enter_s2idle → kernel s2idle_set →
  MWAIT → SCI → s2idle_signal_wake → acpid exit_s2idle)
  now works on any Modern Standby platform (Dell, HP,
  Lenovo, LG Gram, etc.).

* Phase II: FADT parser extracts PM1a_CNT/PM1a_STS ports.
  enter_s3() does the full Linux 7.1 acpi_hw_legacy_sleep
  sequence: clear WAK_STS, wbinvd, split-write SLP_TYP
  then SLP_TYP|SLP_EN. S3 resume trampoline is Phase II.X
  (deferred). The current path falls through to S5 if
  S3 doesn't take.

* Phase I (redbear-quirks): acpi_irq1_skip_override,
  kbd_deactivate_fixup, no_legacy_pm1b, force_s2idle
  flags ported from Linux 7.1 for LG Gram 16 (2025)
  16Z90TR, 16T90SP, 17U70P, and a catch-all LG
  Electronics entry.

* Phase J (deferred): syscall AcpiVerb::EnterS2Idle and
  ExitS2Idle extensions are kept in the local syscall
  fork but the [patch.crates-io] chain is not yet
  active because libredox 0.1.17 has its own vendored
  syscall dep. The kstop string-arg path is the
  cross-version-safe coordination.

Build artifacts: redbear-mini.iso (512 MB) builds
successfully. QEMU boot reaches the Red Bear login
prompt. Inner forks: redbear-os-kernel 9f6a428,
redbear-os-base 76b53f4.
2026-07-01 12:45:07 +03:00
vasilito b504d78448 CHANGELOG: document Phase H cpufreqd oscillation fix (kernel + cpufreqd)
The fix has three parts:

1. Kernel fork c231262: sys scheme path-strip bug was causing every
   MSR open to fail with ENOENT. Pass full 'msr/{cpu}/0x{msr}' path
   to msr::open.

2. cpufreqd 68b1f74db: replace Linux-path DMI detection
   (/sys/class/dmi/id/...) with the Redox-correct
   /scheme/acpi/dmi/... paths, plus CPUID hypervisor bit
   fallback. Mirrors redbear-power/src/cpuid.rs:168.

3. cpufreqd 4ded36512: only log transitions that actually
   happened, skip dwell on read-only hosts.

Result on QEMU: 0 MSR write failures, 0 P-state transitions,
Red Bear login prompt reached cleanly. Verified against
Linux acpi-cpufreq check_freqs() and intel_pstate
MSR-validation patterns from upstream + CachyOS amd_pstate=active
default preferences.
2026-07-01 00:28:04 +03:00
vasilito 7d62a7c0ab docs: document content-hash cache system, binary store, package groups
- AGENTS.md: add cache system to STRUCTURE, WHERE TO LOOK, BUILD FLOW,
  BUILD COMMANDS (--force-rebuild), and CONVENTIONS (dep_hashes.toml,
  binary store restore, package_groups syntax)
- CHANGELOG.md: comprehensive entry for Phase 1-3 + kernel MWAIT +
  ninja-build Redox support
- local/AGENTS.md: note installer fork adds package groups support
- BUILD-CACHE-PLAN.md: fix TOML syntax (underscores not hyphens),
  update all phases to COMPLETE with implementation details, add cache
  flow diagram, add verification results
2026-06-30 17:39:35 +03:00
Red Bear OS 616a9ad8fc docs: add Phase G entry to CHANGELOG (Arrow Lake / LG Gram 2025 hardware port) 2026-06-30 14:49:34 +03:00
Red Bear OS 7a24b854c3 docs: Phase E — _TTS/_WAK hooks and DMAR opt-in
- CHANGELOG.md: added Phase E entry describing the new
  transition_to_s_state / wake_from_s_state / enter_sleep_state
  methods on AcpiContext, and the opt-in DMAR init with hard
  cap. Includes the final gap-closure status table showing
  9 closed, 1 closed-in-part, 2 still open (both require
  hardware-specific work).

- local/docs/ACPI-FORK-SYNC-STRATEGY-2026-06-30.md: added
  Phase E outcome section with the changes applied and
  out-of-scope items.
2026-06-30 07:16:39 +03:00
Red Bear OS cab9655a8b docs: comprehensive Phase D updates — CHANGELOG, strategy, improvement plan, boot-logs README
- CHANGELOG.md: added comprehensive 2026-06-30 entry covering
  the full ACPI fork-sync (Phases A-D) and the redbear-sessiond
  consumer port. Lists the 7 critical gaps that are now fully closed
  and the 2 still open (DMAR + _WAK infrastructure).

- local/docs/ACPI-FORK-SYNC-STRATEGY-2026-06-30.md: added Phase D
  outcome section with the Linux 7.1 cross-reference findings
  (acpi_enter_sleep_state pattern), the changes applied to acpid
  and redbear-sessiond, and the final gap-closure table.

- local/docs/ACPI-IMPROVEMENT-PLAN.md: updated "Current Truthful
  Status" to reflect that acpid now follows the Linux 7.1 sleep
  pattern with _PTS/_SST evaluation, thermal/power enumeration
  works, AML mutex is real, parse_lnk_irc validates ranges, and
  S5 works end-to-end. S1-S4 paths still need _WAK + wakeup
  vector + P-state preservation (Gap #4b scaffolded but not
  implemented). DMAR init still disabled (Gap #2 needs real-HW
  investigation).

- local/docs/boot-logs/README.md: added
  REDBEAR-MINI-BOOT-PS2D-INPUTD-LOG-FIX.md to the inventory.

Also:
- Removed scratch file local/docs/ACPI-FIX-PLAN-2026-06-30.md
  (superseded by the longer ACPI-FORK-SYNC-STRATEGY-2026-06-30.md).
2026-06-30 06:38:51 +03:00
vasilito 7dfebab9bf docs: comprehensive cross-references for 2026-06-30 input-stack fix
Updates six documentation files to point readers to the new
input-stack observability evidence and changelog entry. No
content claims are altered — only "see also" pointers and inventory
updates.

- CHANGELOG.md: new 2026-06-30 entry documenting the input-stack
  fix (commit de9d1f4 in local/sources/base/), the git server
  docs rewrite (commit 0c60adc6b), and the build-system
  hardening addendum (commit 41045fd2f). Includes the verified
  end-to-end interactive login evidence from the rebuilt ISO.

- local/docs/boot-logs/README.md: add the new
  REDBEAR-MINI-BOOT-PS2D-INPUTD-LOG-FIX.md file to the
  inventory table.

- local/docs/IRQ-AND-LOWLEVEL-CONTROLLERS-ENHANCEMENT-PLAN.md:
  see-also pointer in the inputd validation deliverables
  section.

- local/docs/REDBEAR-BOOT-EXPERIENCE-PLAN.md: see-also pointer
  in the bootanim handoff section, noting that step 6
  (REBIND_DISPLAY drm to inputd) now has companion
  observability via the new inputd startup log.

- local/docs/USB-IMPLEMENTATION-PLAN.md: see-also pointer in
  the HID producer modernization section, noting that the fix
  lets operators distinguish "usbhidd dead" from
  "usbhidd alive but not enumerated by XHCI".

- local/docs/GREETER-LOGIN-IMPLEMENTATION-PLAN.md: see-also
  pointer in the service wiring section, noting that the greeter
  can rely on the new inputd/ps2d startup lines being present
  before inputd -A 3 runs.
2026-06-30 03:17:30 +03:00
vasilito 9852f7f8a5 test: verify all recipes, fix CPU compatibility, harden daemons
Test results: 229 tests pass across 8 crates.
session-launch: 11/11, greeterd: 8/8, authd: 16/16,
sessiond: 27/27, hwutils: 19/19, firmware-loader: 24/24,
redox-driver-sys: 30/30, linux-kpi: 94/94.

Known: redox-drm and iommu need Redox target to run tests
(expected for cross-compiled device crates using libredox).

Fixes applied:
- Qt6 toolchain: -march=x86-64 -fpermissive (CPU compat + headers)
- dhcpd: auto-detect interface from /scheme/netcfg/ifaces/
- i2c-gpio-expanderd: decode retry (3x with 50ms delay)
- ucsid: same I2C decode hardening
- CHANGELOG and DESKTOP-STACK-STATUS updated
2026-04-28 06:41:03 +01:00
vasilito 024beab5a1 Link implementation plan from the main README 2026-04-14 11:20:02 +01:00
vasilito 2d4baebbe0 Refresh status docs and add a visible changelog 2026-04-14 10:50:04 +01:00