Commit Graph

1583 Commits

Author SHA1 Message Date
vasilito d8af8e33c2 fix: cookbook cache invalidation — use max(recipe, source) timestamps
Bug: src/cook/cook_build.rs:268 only bumps source_modified when
recipe.toml is STRICTLY newer than source. In normal workflow:
  1. Recipe edited at T1 (adds patch to patches array)
  2. Source re-fetched at T2 > T1 (during make r.<recipe>)
  3. Build caches stage at T3
  4. Next build: recipe(T1) > source(T2) = FALSE → edit ignored

Fix: source_modified = source_modified.max(recipe_modified);
always considers recipe timestamp regardless of relative ordering.

Root cause of kernel rebrand not taking effect was ALSO a missing
.git/HEAD in the source tree (cookbook skips patches for release
archives). Re-fetch with 'repo --allow-protected fetch kernel'
restored the git repo and enabled patch application.

Verified: 'RedBear OS starting...' appears in QEMU boot log.
2026-05-04 20:29:49 +01:00
vasilito eb0718cddb fix: kernel rebrand patch — correct post-consolidated context for fuzz=0
Generated from clean 866dfad0 + consolidated.patch state via diff.
Two hunks for x86_64: comment on line 87 and info! on line 110.
aarch64 (line 94) and riscv64 (line 100) — one hunk each.
Verified: patch applies with --fuzz=0 on top of redbear-consolidated.
Wired into kernel recipe after P8-msi.patch.
2026-05-04 20:07:59 +01:00
vasilito dc59144946 fix: kernel rebrand patch — correct post-consolidated context for fuzz=0
Generated from clean 866dfad0 + consolidated.patch state via diff.
Two hunks for x86_64: comment on line 87 and info! on line 110.
aarch64 (line 94) and riscv64 (line 100) — one hunk each.
Verified: patch applies with --fuzz=0 on top of redbear-consolidated.
Wired into kernel recipe after P8-msi.patch.
2026-05-04 20:07:59 +01:00
vasilito 1aca85e48c fix: greeter compositor — replace bash process substitution with POSIX for loop
redbear-greeter-compositor: line 35 was using 'done < <(cmd)'
bash process substitution which creates /dev/fd/63. Redox kernel
does not implement /dev/fd, causing 'No such file or directory'
error and compositor startup failure.

Replaced 'while read; do ...; done < <(parse_drm_devices)' with
'for device in ; do ...; done' — pure POSIX,
no /dev/fd dependency. Device names contain no whitespace so
word splitting is correct for this use case.
2026-05-04 19:41:04 +01:00
vasilito 3dbfed1323 fix: greeter compositor — replace bash process substitution with POSIX for loop
redbear-greeter-compositor: line 35 was using 'done < <(cmd)'
bash process substitution which creates /dev/fd/63. Redox kernel
does not implement /dev/fd, causing 'No such file or directory'
error and compositor startup failure.

Replaced 'while read; do ...; done < <(parse_drm_devices)' with
'for device in ; do ...; done' — pure POSIX,
no /dev/fd dependency. Device names contain no whitespace so
word splitting is correct for this use case.
2026-05-04 19:41:04 +01:00
vasilito 5eb969cd28 docs: QEMU desktop boot evidence — virtio-gpu works, login prompt reached
redbear-full (4GB) boots in QEMU with virtio-gpu-pci:
  - virtio-gpu detected: display 0 (1280x800px) 
  - framebuffer console: 'RedBear Login:' prompt appears 
  - Wayland compositor: fails on /dev/fd/63 (bash process substitution
    not supported on Redox) — documented as blocker in plan
  - D-Bus system bus: session broker registered 
  - KDE session assembly helper: started 
  - iommu: no AMD-Vi units in QEMU (expected) 

CONSOLE-TO-KDE-DESKTOP-PLAN.md v4.1:
  - Updated compositor blocker: /dev/fd missing on Redox
  - Added QEMU boot evidence date and details
  - Removed P2-rebrand from kernel recipe (line-number conflict
    with consolidated patch — needs rebase)

Remaining errors (pre-existing):
  - fbcond: 'No display present yet' (timing, self-recovers)
  - procmgr: SIGCHLD to PID 1 not permitted
  - cpufreqd: MSR write fails (QEMU, expected)
  - keymapd: Bad file number on scheme read
2026-05-04 19:32:39 +01:00
vasilito 2e6592a7d1 docs: QEMU desktop boot evidence — virtio-gpu works, login prompt reached
redbear-full (4GB) boots in QEMU with virtio-gpu-pci:
  - virtio-gpu detected: display 0 (1280x800px) 
  - framebuffer console: 'RedBear Login:' prompt appears 
  - Wayland compositor: fails on /dev/fd/63 (bash process substitution
    not supported on Redox) — documented as blocker in plan
  - D-Bus system bus: session broker registered 
  - KDE session assembly helper: started 
  - iommu: no AMD-Vi units in QEMU (expected) 

CONSOLE-TO-KDE-DESKTOP-PLAN.md v4.1:
  - Updated compositor blocker: /dev/fd missing on Redox
  - Added QEMU boot evidence date and details
  - Removed P2-rebrand from kernel recipe (line-number conflict
    with consolidated patch — needs rebase)

Remaining errors (pre-existing):
  - fbcond: 'No display present yet' (timing, self-recovers)
  - procmgr: SIGCHLD to PID 1 not permitted
  - cpufreqd: MSR write fails (QEMU, expected)
  - keymapd: Bad file number on scheme read
2026-05-04 19:32:39 +01:00
vasilito 508432e0e5 feat: build system hardening — unwired patch detector + rebrand
check-unwired-patches.sh: scans local/patches/ for .patch files not
referenced in any recipe.toml patches = [...] array. Detects 262
unwired patches (most intentionally kept for reference/rebase).

P2-rebrand-start-message.patch: minimal 39-line patch changing
'Redox OS starting' to 'RedBear OS starting' in x86_64, aarch64,
and riscv64 arch start files. Wired into kernel recipe after
P8-msi.patch. Verified: make r.kernel builds with all 3 patches.

Build system issues surfaced by the detector:
- 250+ kernel individual patches kept for reference (absorbed/)
- ~50 base individual patches — many intentionally unwired
- ~30 relibc patches — may need wiring into relibc recipe
- build-system patches applied by scripts, not recipes
2026-05-04 19:21:02 +01:00
vasilito 3dee740906 feat: build system hardening — unwired patch detector + rebrand
check-unwired-patches.sh: scans local/patches/ for .patch files not
referenced in any recipe.toml patches = [...] array. Detects 262
unwired patches (most intentionally kept for reference/rebase).

P2-rebrand-start-message.patch: minimal 39-line patch changing
'Redox OS starting' to 'RedBear OS starting' in x86_64, aarch64,
and riscv64 arch start files. Wired into kernel recipe after
P8-msi.patch. Verified: make r.kernel builds with all 3 patches.

Build system issues surfaced by the detector:
- 250+ kernel individual patches kept for reference (absorbed/)
- ~50 base individual patches — many intentionally unwired
- ~30 relibc patches — may need wiring into relibc recipe
- build-system patches applied by scripts, not recipes
2026-05-04 19:21:02 +01:00
vasilito 9bc3f24a98 fix: driver-sys MsiAllocation type chain — alloc_cpu_id + u32 irq
Add missing alloc_cpu_id() function (atomic round-robin CPU selection).
Fix type chain: MsiAllocation.irq u8→u32 to match allocate_irq_vector
return type. irq_set_affinity accepts u32 irq for consistency.

Verified: driver-sys compiles on Linux (x86_64-unknown-linux-gnu).
Full redbear-mini image builds and boots in QEMU.
2026-05-04 19:14:28 +01:00
vasilito a8a99c3295 fix: driver-sys MsiAllocation type chain — alloc_cpu_id + u32 irq
Add missing alloc_cpu_id() function (atomic round-robin CPU selection).
Fix type chain: MsiAllocation.irq u8→u32 to match allocate_irq_vector
return type. irq_set_affinity accepts u32 irq for consistency.

Verified: driver-sys compiles on Linux (x86_64-unknown-linux-gnu).
Full redbear-mini image builds and boots in QEMU.
2026-05-04 19:14:28 +01:00
vasilito fd27fe3396 fix: remove P6-e1000d-msi-migration from base patches (conflict)
P6-e1000d-msi-migration.patch conflicts with P6-driver-main-fixes.patch
— both modify e1000d/src/main.rs at overlapping lines. The MSI migration
must be merged into P6-driver-main-fixes during the upcoming P6 rebase.

P6-e1000d-msi-migration.patch preserved in local/patches/base/ for reference.
2026-05-04 19:06:08 +01:00
vasilito 5214621ff8 fix: remove P6-e1000d-msi-migration from base patches (conflict)
P6-e1000d-msi-migration.patch conflicts with P6-driver-main-fixes.patch
— both modify e1000d/src/main.rs at overlapping lines. The MSI migration
must be merged into P6-driver-main-fixes during the upcoming P6 rebase.

P6-e1000d-msi-migration.patch preserved in local/patches/base/ for reference.
2026-05-04 19:06:08 +01:00
vasilito ea380b7daf feat: e1000d MSI/MSI-X migration — use pci_allocate_interrupt_vector
e1000d was the last NIC driver using legacy IRQ (irq.irq_handle()).
Migrated to pci_allocate_interrupt_vector which tries MSI-X first,
then MSI, then falls back to legacy INTx — matching rtl8168d, rtl8139d,
ihdad, ihdgd, and nvmed.

63-line patch at local/patches/base/P6-e1000d-msi-migration.patch,
symlinked and wired into recipes/core/base/recipe.toml.
2026-05-04 19:00:59 +01:00
vasilito e368f56817 feat: e1000d MSI/MSI-X migration — use pci_allocate_interrupt_vector
e1000d was the last NIC driver using legacy IRQ (irq.irq_handle()).
Migrated to pci_allocate_interrupt_vector which tries MSI-X first,
then MSI, then falls back to legacy INTx — matching rtl8168d, rtl8139d,
ihdad, ihdgd, and nvmed.

63-line patch at local/patches/base/P6-e1000d-msi-migration.patch,
symlinked and wired into recipes/core/base/recipe.toml.
2026-05-04 19:00:59 +01:00
vasilito fc5c00cb68 fix: remove P7-scheduler-improvements from kernel recipe patches
P7 failed 3/4 hunks on context.rs at kernel rev 866dfad0.
Consolidated patch already includes P5-sched-rt-policy, P5-context-mod-sched,
P6-percpu-runqueues, P6-futex-sharding which cover most scheduler improvements.
P7 needs rebase — documented in recipe comment.

Verified: full 'make r.kernel' fetch+patch+build chain works:
  git clone + consolidated.patch + P8-msi.patch + cargo build → 1.5MB kernel
2026-05-04 18:35:45 +01:00
vasilito bd1a5320d5 fix: remove P7-scheduler-improvements from kernel recipe patches
P7 failed 3/4 hunks on context.rs at kernel rev 866dfad0.
Consolidated patch already includes P5-sched-rt-policy, P5-context-mod-sched,
P6-percpu-runqueues, P6-futex-sharding which cover most scheduler improvements.
P7 needs rebase — documented in recipe comment.

Verified: full 'make r.kernel' fetch+patch+build chain works:
  git clone + consolidated.patch + P8-msi.patch + cargo build → 1.5MB kernel
2026-05-04 18:35:45 +01:00
vasilito 2ae7ad7afd fix: iommu InterruptRemapTable — add DmaBuffer-backed allocation, fix compile
interrupt.rs:
- InterruptRemapTable now owns optional DmaBuffer for self-allocated tables
- new_allocated(entry_count) constructor allocates physically contiguous
  DMA memory via DmaBuffer::allocate, returns Result
- new(base_addr, size) still works for externally-provided tables
- private addr() helper replaces direct 'base' field access
- len_encoding() returns AMD-Vi log2-encoded IRT length for DTE entries
- physical_address() returns table base physical address
- Remove unused 'warn' and 'error' imports from log crate

amd_vi.rs:
- Use InterruptRemapTable::new_allocated instead of ::new for IRT init
- Cast len_encoding() from u64 to u8 for DeviceTableEntry::set_int_table_len

Verified: iommu crate compiles clean (0 errors, 0 warnings).
2026-05-04 18:27:56 +01:00
vasilito 596ff45011 fix: iommu InterruptRemapTable — add DmaBuffer-backed allocation, fix compile
interrupt.rs:
- InterruptRemapTable now owns optional DmaBuffer for self-allocated tables
- new_allocated(entry_count) constructor allocates physically contiguous
  DMA memory via DmaBuffer::allocate, returns Result
- new(base_addr, size) still works for externally-provided tables
- private addr() helper replaces direct 'base' field access
- len_encoding() returns AMD-Vi log2-encoded IRT length for DTE entries
- physical_address() returns table base physical address
- Remove unused 'warn' and 'error' imports from log crate

amd_vi.rs:
- Use InterruptRemapTable::new_allocated instead of ::new for IRT init
- Cast len_encoding() from u64 to u8 for DeviceTableEntry::set_int_table_len

Verified: iommu crate compiles clean (0 errors, 0 warnings).
2026-05-04 18:27:56 +01:00
vasilito 029472d5e3 feat: IOMMU-aware DmaAllocator + comprehensive DMA/thread audit
dma.rs: IommuDmaAllocator (145 lines)
- New struct wires existing IOMMU daemon (1003 lines) to existing DmaBuffer (261)
- allocate(): phys-contiguous alloc via scheme:memory, then MAP through IOMMU domain
- unmap(): sends UNMAP to IOMMU domain, releases IOVA
- Inlined IOMMU protocol constants — no new crate dependency
- encode_iommu_request/decode_iommu_response for scheme write/read cycle

Documentation updates:
- IMPLEMENTATION-MASTER-PLAN.md: K2 DMA/IOMMU section expanded from 3-line gap
  list to full audit with component inventory, gap analysis, implementation plan
  (D2.1-D2.5), Linux reference table. Added K2b thread/fork audit.
- CPU-DMA-IRQ-MSI-SCHEDULER-FIX-PLAN.md: Phase 1 (MSI) marked complete with
  per-task status. Phase 2 (DMA) re-scoped from 'create' to 'wire' based on
  audit. Phase 3 (scheduler) marked mostly done.
- IRQ-AND-LOWLEVEL-CONTROLLERS-ENHANCEMENT-PLAN.md: kernel MSI support noted
  as materially strong with P8-msi.patch reference.

Audit findings:
- IOMMU daemon is solid: 1003-line lib.rs with full scheme protocol,
  427-line amd_vi.rs, host-runnable tests. Needs wiring, not rewriting.
- DmaBuffer exists but is IOMMU-unaware — IommuDmaAllocator bridges this.
- relibc rlct_clone is correct for threads (shares addr space implicitly).
  '3 IPC hops' claim is microkernel-architectural, not a real perf issue.
- No stale docs to archive at this time.
2026-05-04 18:18:04 +01:00
vasilito 18bba8572c feat: IOMMU-aware DmaAllocator + comprehensive DMA/thread audit
dma.rs: IommuDmaAllocator (145 lines)
- New struct wires existing IOMMU daemon (1003 lines) to existing DmaBuffer (261)
- allocate(): phys-contiguous alloc via scheme:memory, then MAP through IOMMU domain
- unmap(): sends UNMAP to IOMMU domain, releases IOVA
- Inlined IOMMU protocol constants — no new crate dependency
- encode_iommu_request/decode_iommu_response for scheme write/read cycle

Documentation updates:
- IMPLEMENTATION-MASTER-PLAN.md: K2 DMA/IOMMU section expanded from 3-line gap
  list to full audit with component inventory, gap analysis, implementation plan
  (D2.1-D2.5), Linux reference table. Added K2b thread/fork audit.
- CPU-DMA-IRQ-MSI-SCHEDULER-FIX-PLAN.md: Phase 1 (MSI) marked complete with
  per-task status. Phase 2 (DMA) re-scoped from 'create' to 'wire' based on
  audit. Phase 3 (scheduler) marked mostly done.
- IRQ-AND-LOWLEVEL-CONTROLLERS-ENHANCEMENT-PLAN.md: kernel MSI support noted
  as materially strong with P8-msi.patch reference.

Audit findings:
- IOMMU daemon is solid: 1003-line lib.rs with full scheme protocol,
  427-line amd_vi.rs, host-runnable tests. Needs wiring, not rewriting.
- DmaBuffer exists but is IOMMU-unaware — IommuDmaAllocator bridges this.
- relibc rlct_clone is correct for threads (shares addr space implicitly).
  '3 IPC hops' claim is microkernel-architectural, not a real perf issue.
- No stale docs to archive at this time.
2026-05-04 18:18:04 +01:00
vasilito 678980521c feat: T1.1-T2.2 MSI subsystem — kernel MSI, vectors, affinity, validation
Kernel:
- T1.1 msi.rs: MSI message composition (MsiMessage), validation
  (is_valid_msi_address, is_valid_msi_vector), capability parsing
  (MsiCapability, MsixCapability) with bounds-safe .get() access
- T1.2 vector.rs: per-CPU bitmatrix vector allocation/deallocation
- T1.3 IRQ scheme: MSI vector validation gate at irq_trigger,
  iommu_validate_msi_irq hook, msi_vector_is_valid helper
- mod.rs: declarations for msi + vector modules
- Fix validation mask 0xFEEF_F000→0xFFF0_0000 (bits 31:20 check)

T2.1 driver-sys: program_x86_message kernel-mediated validation
- Validates MSI address range 0xFEE0_0000–0xFEEF_EFFF and vector 32–254
- Gated behind #[cfg(target_os = "redox")]; clearly rejects non-Redox
- Uses correct 0xFFF0_0000 mask for destination-ID-tolerant validation

T2.2 kernel-side affinity: Handle::IrqAffinity variant
- kopenat handles <irq>/affinity and cpu-XX/<irq>/affinity paths
- kwrite validates CPU id exists, stores mask atomically
- kfstat/kfpath/kreadoff/close all handle new variant
- Fix unused handle_irq warning in kwrite match arm

T2.3 driver-sys: MsiAllocation struct + irq_set_affinity helper
- MsiAllocation with round-robin CPU allocation via alloc_cpu_id
- irq_set_affinity uses scheme:irq/<irq>/affinity write path
- IrqFd type alias in pci.rs for file descriptor tracking

IOMMU T3.1: InterruptRemapTable, IRTE encode/decode, IrqRemapManager
- IRTE (16-byte) encoding/decoding for AMD-Vi interrupt remapping
- InterruptRemapTable with program/invalidate/find_free
- IrqRemapManager with multi-table remap and validate_msi gate
- Remove arbitrary .min(256) bound on find_free

P8-msi.patch: 281-line durable kernel patch, wired in recipe.toml
2026-05-04 18:00:15 +01:00
vasilito d1c04f2651 feat: T1.1-T2.2 MSI subsystem — kernel MSI, vectors, affinity, validation
Kernel:
- T1.1 msi.rs: MSI message composition (MsiMessage), validation
  (is_valid_msi_address, is_valid_msi_vector), capability parsing
  (MsiCapability, MsixCapability) with bounds-safe .get() access
- T1.2 vector.rs: per-CPU bitmatrix vector allocation/deallocation
- T1.3 IRQ scheme: MSI vector validation gate at irq_trigger,
  iommu_validate_msi_irq hook, msi_vector_is_valid helper
- mod.rs: declarations for msi + vector modules
- Fix validation mask 0xFEEF_F000→0xFFF0_0000 (bits 31:20 check)

T2.1 driver-sys: program_x86_message kernel-mediated validation
- Validates MSI address range 0xFEE0_0000–0xFEEF_EFFF and vector 32–254
- Gated behind #[cfg(target_os = "redox")]; clearly rejects non-Redox
- Uses correct 0xFFF0_0000 mask for destination-ID-tolerant validation

T2.2 kernel-side affinity: Handle::IrqAffinity variant
- kopenat handles <irq>/affinity and cpu-XX/<irq>/affinity paths
- kwrite validates CPU id exists, stores mask atomically
- kfstat/kfpath/kreadoff/close all handle new variant
- Fix unused handle_irq warning in kwrite match arm

T2.3 driver-sys: MsiAllocation struct + irq_set_affinity helper
- MsiAllocation with round-robin CPU allocation via alloc_cpu_id
- irq_set_affinity uses scheme:irq/<irq>/affinity write path
- IrqFd type alias in pci.rs for file descriptor tracking

IOMMU T3.1: InterruptRemapTable, IRTE encode/decode, IrqRemapManager
- IRTE (16-byte) encoding/decoding for AMD-Vi interrupt remapping
- InterruptRemapTable with program/invalidate/find_free
- IrqRemapManager with multi-table remap and validate_msi gate
- Remove arbitrary .min(256) bound on find_free

P8-msi.patch: 281-line durable kernel patch, wired in recipe.toml
2026-05-04 18:00:15 +01:00
vasilito 091f19167b kwin: plugin path fix + KF6Svg stub + QmlPlugins cleanup
- Mirror usr/plugins/*.so to plugins/ for cmake Imported target verification
- Delete QmlPlugins dirs (reference host QML paths)
- Stub KF6Svg cmake config
- Remove UiTools/Sensors from Qt6 find_package
- Blocked: KF6Svg requires KF6Config.cmake component registration
2026-05-04 16:42:19 +01:00
vasilito 439a5e6799 kwin: plugin path fix + KF6Svg stub + QmlPlugins cleanup
- Mirror usr/plugins/*.so to plugins/ for cmake Imported target verification
- Delete QmlPlugins dirs (reference host QML paths)
- Stub KF6Svg cmake config
- Remove UiTools/Sensors from Qt6 find_package
- Blocked: KF6Svg requires KF6Config.cmake component registration
2026-05-04 16:42:19 +01:00
vasilito f5d71b05db plasma-framework: add BLAKE3 hash, kwin cmake fixes (WIP)
- BLAKE3 hash for plasma-framework v6.10.0 tarball
- KWin recipe: remove UiTools/Sensors/KF6::Svg from cmake
- KWin recipe: stub Qt6Plugin targets, QmlPlugins cleanup
- Blocked: Qt6Plugin cmake host-path issue requires deeper qtbase fix
2026-05-04 16:27:58 +01:00
vasilito 73e832504a plasma-framework: add BLAKE3 hash, kwin cmake fixes (WIP)
- BLAKE3 hash for plasma-framework v6.10.0 tarball
- KWin recipe: remove UiTools/Sensors/KF6::Svg from cmake
- KWin recipe: stub Qt6Plugin targets, QmlPlugins cleanup
- Blocked: Qt6Plugin cmake host-path issue requires deeper qtbase fix
2026-05-04 16:27:58 +01:00
vasilito 07c6e422c1 feat: comprehensive scheduler, ACPI, driver, and cpufreqd improvements
Scheduler: LAPIC timer calibration, TSC-deadline mode, work-stealing
load balancer, RT scheduling class, per-CPU nr_running counter.
Direct tick routing via vector 48.

ACPI: S3/S4 sleep states with full AML sequence (_PTS/_GTS/_BFS/_WAK),
NVS save/restore, EC driver hardening, panic-grade behavior removed.

Drivers: 5 driver mains at zero unwrap, 12 new modules across storage,
network, and audio subsystems. AHCI NCQ/PM/TRIM, e1000 ITR/checksum/TSO,
rtl8169 PHY config, HDA codec/jack detection.

cpufreqd: Replaced 26-line stub with 5-governor implementation including
ACPI P-state reading, MSR control, thermal throttle, and error suppression.
thermald: Fan control module with speed curves and emergency mode.

Docs: IMPLEMENTATION-MASTER-PLAN.md, CPU-DMA-IRQ-MSI-SCHEDULER-FIX-PLAN.md.
30 stale docs archived. 3 superseded plans archived.

Patches: P5-named-semaphores (relibc), P6-driver fixes (base),
P7-scheduler (kernel), P6-cpufreqd (local).
2026-05-04 16:08:58 +01:00
vasilito d91c09b54d feat: comprehensive scheduler, ACPI, driver, and cpufreqd improvements
Scheduler: LAPIC timer calibration, TSC-deadline mode, work-stealing
load balancer, RT scheduling class, per-CPU nr_running counter.
Direct tick routing via vector 48.

ACPI: S3/S4 sleep states with full AML sequence (_PTS/_GTS/_BFS/_WAK),
NVS save/restore, EC driver hardening, panic-grade behavior removed.

Drivers: 5 driver mains at zero unwrap, 12 new modules across storage,
network, and audio subsystems. AHCI NCQ/PM/TRIM, e1000 ITR/checksum/TSO,
rtl8169 PHY config, HDA codec/jack detection.

cpufreqd: Replaced 26-line stub with 5-governor implementation including
ACPI P-state reading, MSR control, thermal throttle, and error suppression.
thermald: Fan control module with speed curves and emergency mode.

Docs: IMPLEMENTATION-MASTER-PLAN.md, CPU-DMA-IRQ-MSI-SCHEDULER-FIX-PLAN.md.
30 stale docs archived. 3 superseded plans archived.

Patches: P5-named-semaphores (relibc), P6-driver fixes (base),
P7-scheduler (kernel), P6-cpufreqd (local).
2026-05-04 16:08:58 +01:00
vasilito fab5120f87 kwin: cmake cleanup of host-path Qt6Plugin targets (incomplete)
- Delete QmlPlugins dirs and stub PluginTargets files
- Blocked: Qt6Plugin cmake files reference host paths from QT_HOST_PATH
- Needs qtbase recipe cmake config regeneration for cross-build sysroot
2026-05-04 16:04:00 +01:00
vasilito 1a5ff9a83f kwin: cmake cleanup of host-path Qt6Plugin targets (incomplete)
- Delete QmlPlugins dirs and stub PluginTargets files
- Blocked: Qt6Plugin cmake files reference host paths from QT_HOST_PATH
- Needs qtbase recipe cmake config regeneration for cross-build sysroot
2026-05-04 16:04:00 +01:00
vasilito 93144bf0bf fix: qt5compat blake3 hash, kwin cmake progress
- Add missing blake3 hash to qt5compat recipe
- KWin cmake: Qt6Gui Wayland plugin path references host instead of sysroot
  (needs Qt cmake config regeneration for cross-build)
2026-05-04 15:42:56 +01:00
vasilito d8791a91db fix: qt5compat blake3 hash, kwin cmake progress
- Add missing blake3 hash to qt5compat recipe
- KWin cmake: Qt6Gui Wayland plugin path references host instead of sysroot
  (needs Qt cmake config regeneration for cross-build)
2026-05-04 15:42:56 +01:00
vasilito 30e36e53ec feat: kirigami builds (QML gate cleared)
- QNetworkReply stub header for Redox cross-build
- GuiPrivate + Network in find_package
- QElapsedTimer include fix
- networkAccessManager null stub in icon.cpp
- Primitives target links Qt6::Network for headers
2026-05-04 15:29:00 +01:00
vasilito 765d9f3421 feat: kirigami builds (QML gate cleared)
- QNetworkReply stub header for Redox cross-build
- GuiPrivate + Network in find_package
- QElapsedTimer include fix
- networkAccessManager null stub in icon.cpp
- Primitives target links Qt6::Network for headers
2026-05-04 15:29:00 +01:00
vasilito 15d77b6254 kirigami: fix Qt6::GuiPrivate cmake target, QElapsedTimer include
- Add GuiPrivate to Qt6 find_package in top-level CMakeLists.txt
- Add missing QElapsedTimer include in toolbarlayout.cpp
- Add network stub infrastructure in recipe (incomplete, Qt6Network
  cross-compilation still needed for full build)
2026-05-04 14:49:07 +01:00
vasilito e506611289 kirigami: fix Qt6::GuiPrivate cmake target, QElapsedTimer include
- Add GuiPrivate to Qt6 find_package in top-level CMakeLists.txt
- Add missing QElapsedTimer include in toolbarlayout.cpp
- Add network stub infrastructure in recipe (incomplete, Qt6Network
  cross-compilation still needed for full build)
2026-05-04 14:49:07 +01:00
vasilito 4e439faae5 docs: add authoritative master implementation plan 2026-05-04 14:45:21 +01:00
vasilito bfeedfe268 docs: add authoritative master implementation plan 2026-05-04 14:45:21 +01:00
vasilito 50af2023f6 fix: cpufreqd MSR spam, udev-shim PCI spam, scheme throttle, keymaps dir
- cpufreqd: suppress MSR errors after 1 failure (was 10)
- udev-shim: demote PCI scan failures from WARN to DEBUG
- accessibility/ime/keymapd: throttle EBADF loop with 100ms sleep
- config: create /etc/keymaps directory for keymapd
2026-05-04 14:28:19 +01:00
vasilito b723b276f5 fix: cpufreqd MSR spam, udev-shim PCI spam, scheme throttle, keymaps dir
- cpufreqd: suppress MSR errors after 1 failure (was 10)
- udev-shim: demote PCI scan failures from WARN to DEBUG
- accessibility/ime/keymapd: throttle EBADF loop with 100ms sleep
- config: create /etc/keymaps directory for keymapd
2026-05-04 14:28:19 +01:00
vasilito 8b872979ef fix: udev-shim panic, sessiond duplicate, scheme Bad-fd handling
- udev-shim: replace .expect() with graceful errors (no more panic on Broken pipe)
- P4-initfs: remove duplicate sessiond (conflicted with config)
- accessibility/ime/keymapd: break instead of exit(1) on EBADF
- P6 driver patches rebased
- Docs: archive old reports, add implementation master plan
2026-05-04 14:04:03 +01:00
vasilito 48ec92b486 fix: udev-shim panic, sessiond duplicate, scheme Bad-fd handling
- udev-shim: replace .expect() with graceful errors (no more panic on Broken pipe)
- P4-initfs: remove duplicate sessiond (conflicted with config)
- accessibility/ime/keymapd: break instead of exit(1) on EBADF
- P6 driver patches rebased
- Docs: archive old reports, add implementation master plan
2026-05-04 14:04:03 +01:00
vasilito ce0ac10b6d chore: sync all pending changes — kirigami platform headers, cookbook fix, docs, patches
Kirigami: remove stub .cpp, add Qt platform integration headers for
QML gate. Matches KDE src/pattern for direct header-only builds.

Cookbook: add --no-backup-if-mismatch to patch invocation (fetch.rs).

Kernel: consolidate patch chain, add debug-scheme-serial-fix.

Docs: archive old audit reports, add CHANGELOG and hardware validation
matrix. Update AGENTS.md with Linux reference source policy.

Scripts: add test-network-qemu.sh, test-storage-qemu.sh.

.gitignore: add local/reference/ exclusion.
2026-05-04 11:57:48 +01:00
vasilito 1b5c19b22a chore: sync all pending changes — kirigami platform headers, cookbook fix, docs, patches
Kirigami: remove stub .cpp, add Qt platform integration headers for
QML gate. Matches KDE src/pattern for direct header-only builds.

Cookbook: add --no-backup-if-mismatch to patch invocation (fetch.rs).

Kernel: consolidate patch chain, add debug-scheme-serial-fix.

Docs: archive old audit reports, add CHANGELOG and hardware validation
matrix. Update AGENTS.md with Linux reference source policy.

Scripts: add test-network-qemu.sh, test-storage-qemu.sh.

.gitignore: add local/reference/ exclusion.
2026-05-04 11:57:48 +01:00
vasilito 11993af01f fix: rebase base patches, commit recipe drift, add relibc rlimit/sysconf
Base: fix P6-driver-new-modules.patch (ed format -> unified diff) for new
driver modules (ncq, itr, phy). P6-driver-main-fixes.patch now applies with
offset on current upstream source.

Relibc: remove stale P5-named-semaphores (upstream has stubs), add
P10-stack-size-8mb and P11-getrlimit-getrusage (per-process rlimit table,
sysconf integration, getdtablesize fix, null-pointer safety).

Kernel: consolidate 29 individual patches into single redbear-consolidated.patch.

Userutils: P5-redbear-branding replaces P4-login-rate-limit.

Recipe.toml changes now committed so they survive source resets.
2026-05-04 11:49:15 +01:00
vasilito 7f2bf081c5 fix: rebase base patches, commit recipe drift, add relibc rlimit/sysconf
Base: fix P6-driver-new-modules.patch (ed format -> unified diff) for new
driver modules (ncq, itr, phy). P6-driver-main-fixes.patch now applies with
offset on current upstream source.

Relibc: remove stale P5-named-semaphores (upstream has stubs), add
P10-stack-size-8mb and P11-getrlimit-getrusage (per-process rlimit table,
sysconf integration, getdtablesize fix, null-pointer safety).

Kernel: consolidate 29 individual patches into single redbear-consolidated.patch.

Userutils: P5-redbear-branding replaces P4-login-rate-limit.

Recipe.toml changes now committed so they survive source resets.
2026-05-04 11:49:15 +01:00
vasilito 39b6aa7c54 fix(config): move init services from /usr/lib/init.d to /etc/init.d
Config [[files]] entries for init services used /usr/lib/init.d/ paths,
which get silently overwritten by package staging (Layer 2 over Layer 1).
Per AGENTS.md, config overrides MUST use /etc/init.d/ so the init system's
config_for_dirs() gives them priority over package defaults.

Fixes mini image debug console failure (getty: failed to open TTY
/scheme/fbcon/3: No such file or directory) caused by base package's
31_debug_console.service overwriting minimal.toml's debug scheme override.
2026-05-04 07:10:39 +01:00
vasilito adead56cd0 fix(config): move init services from /usr/lib/init.d to /etc/init.d
Config [[files]] entries for init services used /usr/lib/init.d/ paths,
which get silently overwritten by package staging (Layer 2 over Layer 1).
Per AGENTS.md, config overrides MUST use /etc/init.d/ so the init system's
config_for_dirs() gives them priority over package defaults.

Fixes mini image debug console failure (getty: failed to open TTY
/scheme/fbcon/3: No such file or directory) caused by base package's
31_debug_console.service overwriting minimal.toml's debug scheme override.
2026-05-04 07:10:39 +01:00
vasilito cd29d63533 feat: enable redbear-compositor in redbear-full profile
The Wayland compositor was commented out, causing the greeter to fail
when trying to launch the UI. With the compositor enabled, the full
greeter flow now works: compositor starts, creates Wayland socket,
greeter UI launches on VT 3, and Qt6 client connects successfully.
2026-05-04 01:09:37 +01:00