vasilito
06b316076f
Root cause: the 0.2.4 upstream sync silently removed driver-manager (our
in-house PCI driver orchestrator) and never added a pcid init service,
leaving /scheme/pci uncreated and breaking all PCI device enumeration.
Changes:
- base-initfs/recipe.toml: restore driver-manager dep, binary copy,
drivers.d/ config dir, set -eo pipefail
- redbear-device-services.toml: add driver-manager = {} to packages
- redbear-boot-stages.toml: restore from 0.2.3 (109 lines)
- protected-recipes.toml: restore from 0.2.3 (99 lines)
- redbear-mini.toml: add boot-stages to include chain
- driver-manager Cargo.toml: fix pcid path from symlink to physical
- base fork pointer: acdcb183 (adds 35_pcid.service to initfs)
- UPSTREAM-SYNC-PROCEDURE.md: document sync flaw, never-delete rule,
driver-manager rationale
- PACKAGE-BUILD-QUIRKS.md: document pcid/pcid-spawner architecture,
Redox flag values, kernel kcall on AcpiScheme
Verified: redbear-mini boots to login prompt in QEMU UEFI with working
PCI enumeration (6 devices), e1000d network driver, DHCP, driver-manager.
20 lines
605 B
TOML
20 lines
605 B
TOML
[package]
|
|
name = "driver-manager"
|
|
version = "0.1.0"
|
|
edition = "2024"
|
|
description = "Device driver manager with deferred and async probing"
|
|
|
|
[[bin]]
|
|
name = "driver-manager"
|
|
path = "src/main.rs"
|
|
|
|
[dependencies]
|
|
redox-driver-core = { path = "../../../drivers/redox-driver-core/source" }
|
|
redox-driver-pci = { path = "../../../drivers/redox-driver-pci/source" }
|
|
pcid_interface = { path = "../../../../../local/sources/base/drivers/pcid", package = "pcid" }
|
|
redox-scheme = "0.11"
|
|
syscall = { package = "redox_syscall", version = "0.8" }
|
|
log = "0.4"
|
|
toml = "0.8"
|
|
serde = { version = "1", features = ["derive"] }
|