From 6c0acf5772b30482083b7a247bcbf71c67382c21 Mon Sep 17 00:00:00 2001 From: orchestration-renewed Date: Wed, 18 Nov 2026 15:18:35 +0100 Subject: [PATCH] docs(bringup-steps): research, decision and queue for bring-up steps as data The author asked for every small step of a bring-up as data - what it needs, what it enables, its proof - generic in docs, each device base recording where it stands, so a guidebook, helpers and a runner can be made from it. Measured: walleye's real road is 26 steps (17 done with checks and records, the charger failing); surya took another road; nobody outside keeps steps with edges and proofs. Decided: generic steps and hard/soft edges in docs, claimed per device base by a template-shipped contract and pulled like parts, unclaimed = not known yet. Drafts (schema, records, chain query, seed) and the failing test in research/bringup-steps/2026-11-18/; ten items unranked. Co-Authored-By: Claude Opus 5.5 --- data/backlog.json | 11 + data/decisions.json | 1 + data/research.json | 2 + data/session_log.json | 1 + data/sources.json | 18 + data/summaries.json | 1 + docs/backlog.md | 275 +++++++++++++++ docs/decisions.md | 39 +++ docs/index.md | 12 +- docs/research.md | 55 +++ docs/session_log.md | 24 ++ docs/sources.md | 315 ++++++++++++++++++ docs/summaries.md | 15 + research/bringup-steps/2026-11-18/README.md | 85 +++++ .../2026-11-18/bringup-chain-walleye.sh | 32 ++ .../bringup-steps/2026-11-18/chain-walleye.md | 32 ++ .../2026-11-18/claims-walleye.sh | 28 ++ .../2026-11-18/queries/bringup-chain.sql | 29 ++ .../2026-11-18/records/bringup-edge.sql | 13 + .../2026-11-18/records/bringup-step.sql | 21 ++ research/bringup-steps/2026-11-18/schema.toml | 183 ++++++++++ research/bringup-steps/2026-11-18/seed.sh | 151 +++++++++ 22 files changed, 1337 insertions(+), 6 deletions(-) create mode 100644 research/bringup-steps/2026-11-18/README.md create mode 100644 research/bringup-steps/2026-11-18/bringup-chain-walleye.sh create mode 100644 research/bringup-steps/2026-11-18/chain-walleye.md create mode 100644 research/bringup-steps/2026-11-18/claims-walleye.sh create mode 100644 research/bringup-steps/2026-11-18/queries/bringup-chain.sql create mode 100644 research/bringup-steps/2026-11-18/records/bringup-edge.sql create mode 100644 research/bringup-steps/2026-11-18/records/bringup-step.sql create mode 100644 research/bringup-steps/2026-11-18/schema.toml create mode 100755 research/bringup-steps/2026-11-18/seed.sh diff --git a/data/backlog.json b/data/backlog.json index f88ff5c0..48045f0b 100644 --- a/data/backlog.json +++ b/data/backlog.json @@ -180,3 +180,14 @@ {"project":"linux-phone-oco/device-template","id":"template-followed-by-update-pins","title":"The hourly update-pins moves a lab's template pin as it moves idealkb's: the template lists its consumers, each bump lands through the lab's CI","status":"open","note":"Step 3. A change to the device layer then lands in the template only; no more parallel hand PRs. idealkb first, then the template, in one run.","opened":"2026-11-18","waits":"grenudi/ideal-knowledge-base item follow-source-from-pin (follow.sh and update-pins read their source from the pin file)","blocked_by":"template-releases","hardware":null,"needs":null,"device":null,"proof":"the first template release after v0.1.0 reaches surya-lab and google-walleye-lab as one bot PR each, landed by their CI, with template-drift exit 0 after","rank":null,"about":"device-template"} {"project":"linux-phone-oco/surya-lab","id":"surya-follows-template","title":"surya-lab follows device-template's release: its copy of the list gone, check.yml and tests/health/README.md taken, the pin a release","status":"open","note":"Migration for decision 2026-11-18-device-template-follows-by-release; no phone. Measured drift today: generic copy 5 entries behind, check.yml without xargs -r, tests/health/README.md missing, devicebase.toml template = 2026-11-17. AGENTS.md outside the idealkb part stays its own until the template:begin part exists, then the general conventions come from the template.","opened":"2026-11-18","waits":null,"blocked_by":"template-releases","hardware":null,"needs":"build","device":"xiaomi-surya","proof":"docs research/device-template/2026-11-18/template-drift.sh device-template ideal-knowledge-base surya-lab: every surya-lab line says ok","rank":null,"about":"device-template"} {"project":"linux-phone-oco/google-walleye-lab","id":"walleye-follows-template","title":"google-walleye-lab follows device-template's release: its copy of the list gone, its rust job in its own workflow, the pin a release, stale PR 208 closed","status":"open","note":"Migration for decision 2026-11-18-device-template-follows-by-release; no phone. Measured drift today: generic copy 5 entries behind, ffs-acm-rs job inside the template's check.yml, devicebase.toml template = 2026-11-17, PR #208 (the template's #15 by hand) open though main has it.","opened":"2026-11-18","waits":null,"blocked_by":"template-releases","hardware":null,"needs":"build","device":"google-walleye","proof":"docs research/device-template/2026-11-18/template-drift.sh device-template ideal-knowledge-base google-walleye-lab: every google-walleye-lab line says ok","rank":null,"about":"device-template"} +{"project":"linux-phone-oco/docs","id":"bringup-steps","title":"Bring-up steps as data: every step that makes Linux run on a machine, generic in docs, each device's status claimed in its own base, a guidebook and helpers made from it","status":"open","note":"Decided 2026-11-18-bringup-steps-generic-in-docs-status-in-each-base (research bringup-steps-landscape). The pieces are the items about bringup-steps, unranked for the author.","opened":"2026-11-18","waits":null,"blocked_by":"bringup-steps-schema,bringup-steps-seed,feed-device-steps,walleye-steps-claimed","hardware":null,"needs":null,"device":null,"proof":"research/bringup-steps/2026-11-18/bringup-chain-walleye.sh passes in docs: tad q bringup-chain --device google-walleye lists walleye's steps in order, each proven one with its proof and run, none unknown (fails today: no query bringup-chain)","rank":null,"about":"commons-only"} +{"project":"linux-phone-oco/docs","id":"bringup-steps-schema","title":"The bring-up step tables in docs: bringup_steps, bringup_step_edges, step_status, the records bringup-step and bringup-edge, and the query bringup-chain","status":"open","note":"Ready to land as drafted in research/bringup-steps/2026-11-18 (schema.toml, records/, queries/): tried in a scratch clone at 3596bb3. The owner's to land (AGENTS.md: schema, records, queries).","opened":"2026-11-18","waits":null,"blocked_by":null,"hardware":null,"needs":null,"device":null,"proof":"tad check passes with the three tables; tad r bringup-edge refuses an edge that closes a cycle; tad q bringup-chain answers with no device (every status unknown)","rank":null,"about":"bringup-steps"} +{"project":"linux-phone-oco/docs","id":"bringup-steps-seed","title":"Seed the generic steps: 26 steps and 37 edges from walleye's real chain, surya's road checked against it","status":"open","note":"sh research/bringup-steps/2026-11-18/seed.sh in docs, through the records","opened":"2026-11-18","waits":null,"blocked_by":"bringup-steps-schema","hardware":null,"needs":null,"device":null,"proof":"tad q bringup-chain lists 26 steps, bootloader and stock steps at depth 0, health-suite-runs last; tad check passes","rank":null,"about":"bringup-steps"} +{"project":"linux-phone-oco/device-template","id":"steps-contract","title":"The steps contract in the template: a steps table, the record step, contract steps = 1 in devicebase.toml, data/steps.json empty, in the template's followed files","status":"open","note":"Reaches labs by the template release (decision 2026-11-18-device-template-follows-by-release), never by hand. A new device starts with no claim: every step not known yet.","opened":"2026-11-18","waits":null,"blocked_by":"bringup-steps-schema,template-releases","hardware":null,"needs":null,"device":null,"proof":"in the template, tad check passes with an empty steps table; tad r step --step shell-on-console --status done --proof X --run Y writes one row and refuses a status outside the six","rank":null,"about":"bringup-steps"} +{"project":"linux-phone-oco/docs","id":"feed-device-steps","title":"Pull each device base's steps into step_status: records/feed-device-steps.sql and a device-steps-unknown fallback in bin/run-feeds.sh","status":"open","note":"As feed-device-parts: read devicebase.toml (steps = 1) and data/steps.json from the base on main; a step not claimed is unknown, not known yet; a claim of a step docs does not know is dropped and named.","opened":"2026-11-18","waits":null,"blocked_by":"bringup-steps-schema,steps-contract","hardware":null,"needs":null,"device":null,"proof":"run against a base without steps = 1, every step of that device is unknown with the reason; against google-walleye-lab after its claims, research/bringup-steps/2026-11-18/bringup-chain-walleye.sh passes","rank":null,"about":"bringup-steps"} +{"project":"linux-phone-oco/google-walleye-lab","id":"walleye-steps-claimed","title":"walleye claims its bring-up steps in its own base, from its records","status":"open","note":"The 26 claims are written out in research/bringup-steps/2026-11-18/claims-walleye.sh, each run a record of google-walleye-lab. Data only; no phone.","opened":"2026-11-18","waits":null,"blocked_by":"steps-contract,walleye-follows-template","hardware":null,"needs":"build","device":"google-walleye","proof":"research/bringup-steps/2026-11-18/bringup-chain-walleye.sh passes in docs after make feeds","rank":null,"about":"bringup-steps"} +{"project":"linux-phone-oco/surya-lab","id":"surya-steps-claimed","title":"surya claims its bring-up steps in its own base, from its records (its road: a booting distribution, the image steps not-needed)","status":"open","note":"The claims are listed in research/bringup-steps/2026-11-18/README.md (Surya's path); PMIC and charger stay unknown until measured.","opened":"2026-11-18","waits":null,"blocked_by":"steps-contract,surya-follows-template","hardware":null,"needs":"build","device":"xiaomi-surya","proof":"tad q bringup-chain --device xiaomi-surya in docs shows health-suite-runs done with run 2026-11-17-1550-lpoco-health-v017, and no step unknown but pmic-bound and charger-online","rank":null,"about":"bringup-steps"} +{"project":"linux-phone-oco/docs","id":"bringup-guidebook","title":"The guidebook rendered from the steps: docs/guidebook.md by make render, a chapter per stage, each step's done-when, needs, proof, helper or gap, guide, and a column per device","status":"open","note":null,"opened":"2026-11-18","waits":null,"blocked_by":"bringup-steps-seed","hardware":null,"needs":null,"device":null,"proof":"make verify fails when docs/guidebook.md is stale against the rows, and the page lists the 26 steps in bringup-chain's order with every hard need before its step","rank":null,"about":"bringup-steps"} +{"project":"linux-phone-oco/lab-tools","id":"bringup-steps-helpers","title":"The helper map: lpoco bringup steps reads docs' chain and names, per step, its lpoco command or the gap","status":"open","note":"Today: image pack/check/swap/bisect, initramfs build, lab fastboot, flash, provision, suite. Gaps: UART, banner, shell, dmesg map, PMIC, charger, storage. Each gap filled becomes its own item.","opened":"2026-11-18","waits":null,"blocked_by":"bringup-steps-seed","hardware":null,"needs":null,"device":null,"proof":"a test in lab-tools: every helper named in docs' bringup_steps is a subcommand lpoco --help lists at the pinned release, and lpoco bringup steps --device google-walleye prints the gaps","rank":null,"about":"bringup-steps"} +{"project":"linux-phone-oco/lab-tools","id":"bringup-step-runner","title":"Research: a runner that walks a device's ready steps - helper, then proof, then the claim in its base; a step that changes the phone queued to its keeper","status":"open","note":null,"opened":"2026-11-18","waits":null,"blocked_by":"bringup-steps-helpers,feed-device-steps","hardware":null,"needs":null,"device":null,"proof":"a research row and a decision with what was rejected, and its failing test: the runner on a made-up device with two ready steps runs each helper and proof and writes two claims","rank":null,"about":"bringup-steps"} +{"project":"linux-phone-oco/docs","id":"milestones-step-terms","title":"Milestones name steps: step:ID@device in criteria, read from step_status by milestone-readiness","status":"open","note":null,"opened":"2026-11-18","waits":null,"blocked_by":"feed-device-steps","hardware":null,"needs":null,"device":null,"proof":"milestone-readiness counts a step term done only when step_status says done for that device; a walleye milestone 'reaches a shell' over step:shell-on-console@google-walleye reads ready","rank":null,"about":"bringup-steps"} diff --git a/data/decisions.json b/data/decisions.json index e02ed3a1..af2d98d5 100644 --- a/data/decisions.json +++ b/data/decisions.json @@ -69,3 +69,4 @@ {"id":"2026-11-18-device-manifest-schema-from-rust","brief":"device.toml stays data, declared once in Rust: one manifest crate for every lpoco program, its schema projected per release and checked in editors and CI","project":"linux-phone-oco/lab-tools","date":"2026-11-18","decision":"device.toml stays a data file, declared once in Rust: one manifest crate holds its types with their doc comments, every lpoco program (lab, host, bringup) reads it, unknown fields are refused at every level, and its JSON Schema is projected from the types (schemars, draft-07) and published with each lpoco release; each device.toml names the schema of its pin on its first line (#:schema), so editors complete, validate and explain it, and CI of lab-tools (the committed schema equals the types) and of each device repository (its file against its pinned schema) catch drift before a lane does. What a phone-side piece is - its files, path, unit, version - is Rust in the roof, an enum with tokens; a device only names tokens. Backlog manifest-one-schema, then surya-manifest-schema, walleye-manifest-schema, template-manifest-schema.","why":"The author asked for declarations a machine relates, not a manual that drifts (2026-11-18). Today device.toml has three parsers in three shapes and devlab ignores a misspelled table, while the template's header claims unknown fields are refused - the drifting manual itself. Projecting the schema from the types is rust-with-argenv applied to a file: declared once in code, the contract derived, never written twice. It costs about an agent-day in lab-tools and one line plus a CI step per device repository, keeps device repositories data (decision 2026-11-17-the-phone-is-data) and the pin-and-follow route (research bringup-home-follow-and-rhizoid). It leaves rename and go-to-definition from a TOML key to Rust undone; that is the one thing given up. Research device-declaration-typed-landscape.","rejected":"A typed Rust crate or rust-script per device (rename and go-to-definition across devices, but every device change becomes a build of that device's code at the lab, a 0.x library pin in every device, code from each device repository run by the lab, and the-phone-is-data reversed; migrating surya-lab and google-walleye-lab to crates and teaching devlab, host and bringup to build and load them is 3-5 agent-days against one); a hand-written schema beside the types (two artifacts drift - argenv's own reason); confique or figment (a rewrite of the types; confique's generated template is taken as an idea, without the crate); status quo serde (caught at load, on the lane, after merge, and not at all where deny_unknown_fields is missing).","about":"phone-side-pieces","research":"device-declaration-typed-landscape","supersedes":null,"amends":null,"scope":null,"tracked_by":null} {"id":"2026-11-18-upstream-forks","brief":"Our forks live under grenudi (the org copies transferred there); topic per upstream item, never-rebased lab branch, phones via a tagged lab apk and the labs kernel routes; one upstreams lane","project":"linux-phone-oco/docs","date":"2026-11-18","decision":"Forks: grenudi/sxmo-utils (upstream fork-sxmo-utils, a mirror of sr.ht) and grenudi/linux (fork-linux, a fork of sm7150-mainline/linux) - the organisation's two repositories transferred to the author's account, so one home holds the history; old linux-phone-oco/ URLs redirect, and new references name grenudi. Branches in each: the tracking branch (sxmo master; the kernel's upstream tags and v7.x) mirrors upstream and is never edited; one topic branch per upstream item, named topic/ITEM-ID (sxmo) or topic/ITEM-ID, fix/, dt/ (kernel), off the base its upstream takes, a series of its own, rebased only before a send (it is unsent, so ours); an integration branch per consumer that merges the topics and is never rebased - sxmo lab, kernel test/DEVICE-WHAT - tagged lab-YYYYMMDD.N where a build pins it; a topic is retired when upstream carries it (upstream-state landed, carried-in none, the branch deleted). Each patch carried is an upstream item with --carried-in FORK/BRANCH, so tad q carried says what to keep at the next rebase. How it reaches the phones: sxmo-utils as an APKBUILD in lab-tools packaging forked from Alpine's (all subpackages, source the fork's lab tag, pkgver 1.18.1_pDATE), built and signed by the package conveyor, installed as sxmo-utils@lab from the tagged lab repository so an apk upgrade keeps it; kernels by each lab's own route from a test/ branch (surya-lab test kernels from branches, walleye v7.3 + own dts). rhizoid is not used yet: plain git with this rule; what rhizoid needs to carry it is sent to git-rhizoid as a finding (rhizoid-carries-mail-forks).\nWho coordinates: one upstreams lane - a lane coordinator for all forks and every outgoing series, started by orchestration when its queue holds work (now: two series); it keeps the branch rule, prepares each series and its upstream item, and queues the proofs: needs=phone rows go to the device keepers (surya, walleye), needs=build to the builders. Split into a lane per upstream project when one project holds more than about five open items or its own review traffic.\nThe fixes, each on its topic and proven before any mail: (1) sxmo autosuspend backs off 1..64 s after failed suspends; (2) the device profile names services stopped around suspend (SXMO_SUSPEND_STOP_SERVICES), stopped before a second read of the wakeup count, started after - the Pixel 3a case moves into its profile; (3) surya's profiles name its sensors daemon - one sxmo series of three. (4) The way back from a suspend that never returns is the PMIC watchdog (pm8916_wdt on gen2 PON: pm6150, pm8998) kept running through suspend only when its bark may wake the system and a pretimeout is set - an RFC series of four to linux-watchdog; the qcom-wdt module parameter stays lab-only until (4) is proven, and its upstream question is superseded. Mail only on the author's word, from his clone, signed off by him (kernel: Assisted-by: LLM).","why":"The author's direction: forks of each project, the best fixes worked there per project, then mailed upstream as concrete working patches (research upstream-forks-landscape). The forks he asks for already exist under his organisation, and the organisation is where the project's repositories and records already live; a second fork elsewhere would split history and records, and sourcehut cannot be forked on GitHub anyway. A topic per upstream item is what a mailing list takes (a series per question, rebased on master), and a never-rebased integration branch is what a consumer can pin - rhizoid's tracking/patch split, with the patch branch cut per item. The tagged apk repository is the only route an apk upgrade does not undo, and the package conveyor already signs and publishes. One lane is enough for two series; a lane per project would hold two idle coordinators. Fix 2's form answers the reason the same idea was refused in 2024 (research sxmo-suspend-fixes); fix 4 follows the only shape upstream has taken (a wake IRQ watchdog) on the one watchdog that keeps counting while the SoC sleeps, and the APSS watchdog is known to freeze there - why try 4 had no bite (research pmic-wdt-way-back). Amended the same day on the author's word ('yes, and lets keeps them under my account for simplisity'): the forks live under grenudi. The org's two repositories were transferred to grenudi (GitHub transfer: one history, branches, issues and the fork link to sm7150-mainline kept; old linux-phone-oco/ URLs redirect), so there is one home and no duplicate.","rejected":"Keeping the forks in the organisation (the first form of this decision): the author chose his account for simplicity. New grenudi forks beside the org copies, or archiving the org copies: two histories, and the open issues and PRs of linux-phone-oco/linux (7) and the lane branches would stay behind - a transfer moves them whole. A fork of pmaports or of Alpine aports for sxmo: our own APKBUILD in lab-tools packaging carries it without a third fork. make install or pmbootstrap build --src onto the phone: undone by the next apk upgrade, no identity. rhizoid as the tool now: its CLI is stubbed and parked, and it lacks non-GitHub tracking, topic series, mail send-back, retirement and apk pins. A lane coordinator per upstream project (sxmo, kernel): two long-lived sessions for two series, each needing the keepers anyway; one patch branch per fork merged from tracking (rhizoid's literal form): a mailing list needs a series per item, and one branch mixes them. For fix 2: a list stopped inside sxmo_suspend.sh (refused 2024: the wakeup count race); suspending through logind/systemd so distro sleep hooks run (asynchronous against sxmo's time accounting, the same race, and the lab's systemctl suspend path is the one surya did not return from). For fix 3: the qcom-wdt keep_armed_in_suspend parameter upstream (refused as policy for imx2 in 2025-26, and the APSS counter freezes in the deepest sleep); qcom-wdt with its bark as a wake IRQ (the freeze makes it useless); a DT property that keeps a watchdog running (OS policy, not DT).","about":"upstream-forks","research":"upstream-forks-landscape","supersedes":null,"amends":null,"scope":null,"tracked_by":null} {"id":"2026-11-18-device-template-follows-by-release","brief":"device-template is followed like idealkb: it names every file followed or made once, releases, labs pin it and update-pins lays it; template-drift fails CI on drift; no more hand fan-out","project":"linux-phone-oco/device-template","date":"2026-11-18","decision":"device-template becomes a second source in the pin-and-follow slice that idealkb already runs (carrying out idealkb decision 2026-11-17-chain-follow-by-slice for the template, and docs item device-template-follow):\n1. It names every file it has: `generic` (followed - laid at the pinned release, never edited in a lab unless the lab names it in own) and a new `made-once` list (laid at creation, then the lab's own: device.toml, oco.toml, README.md, devicebase.toml, idealkb.toml, provision/packages.txt, .oco/uncommitted, data/). The skeleton moves into generic: Makefile, bin/install-tad.sh, tad.yml, gather.yml, .gitignore, tests/health/README.md and the template's script check, in a workflow file a lab does not extend (a lab's own jobs go in its own file). AGENTS.md's general conventions get a template:begin/end part laid like idealkb's. The three hardware files leave the template's list: idealkb gives them; a file has one source.\n2. It releases (release-please, from v0.1.0); devicebase.toml names the release (template = \"0.1.0\") and own = [...] for template files a lab keeps as its own; a lab carries no copy of the list.\n3. idealkb's follow.sh and update-pins take their source from the pin (idealkb item follow-source-from-pin), and the template lists its consumers: one hourly job moves both pins, each through the lab's CI, idealkb first.\n4. template-drift (research material, failing today) runs in the template's CI (classified, one-source) and in each lab's (pin, equal, no-copy), so a hand edit or a stale lab fails at the PR, not at the next bump.\n5. A change to the device layer lands in the template only; labs get it by the release bump. What proves general for every base goes on to idealkb, as hardware did, and leaves the template's list in the same release.\nLogic never enters the template (decision 2026-11-17-the-phone-is-data): it reaches labs as lpoco by pin. device.toml's shape is the schema's (decision 2026-11-18-device-manifest-schema-from-rust, template-manifest-schema), not this list's. When git-rhizoid's slice-consumption works, the job moves there; follow.sh is its prototype.\nMigration: surya-lab - drop the list copy, take check.yml and tests/health/README.md, pin the release (about an hour, through its first bump); google-walleye-lab - drop the copy, move its rust job to its own workflow, close stale #208, pin (about an hour). Template: classify and release (2-3 h), the check in CI (2 h); idealkb's follow-source-from-pin (about 3 h, idealkb's owner). About one agent-day in all, no phone.","why":"The author asked how drift is prevented (2026-11-18). Measured (research device-template-drift-measured): it is not - 13 statements were carried to each lab by hand in parallel PRs (9 PRs, one still open and stale), each lab carries a stale copy of the list, three files have two sources and every idealkb release since 0.14.0 opened a false-alarm PR in all three bases, closed by hand; devicebase.toml's pin is a date true of no lab. The mechanism to fix it exists and was already chosen for the template (chain-follow-by-slice); what is missing is small and named: the template's release, its classification, a check that fails, and follow.sh reading its source from the pin. Others agree (research device-template-follow-world): cruft and copier carry a template by a pin and a failing check; projen and copier name which files are kept in step and which are made once.","rejected":"Keep carrying changes by hand into each lab: it does not scale past two labs; it already left a stale PR, stale list copies and a date for a pin; nothing names drift. Copier or cruft: Python (refused here), a second state file beside the pin, a template engine and three-way merge for repositories that are data. GitHub template plus actions-template-sync: -X theirs overwrites a lab's data and surya-lab has no template history. git subtree or submodule: tad reads queries/, records/ and tables.toml at the root; a prefix breaks it. git-rhizoid now: its slice-consumption is open and its CLI stubbed - the later home, not today's (its items stay on its backlog). The device layer moved wholesale into idealkb: idealkb is domain-free; only what proves general moves, one file at a time. The device layer shipped by lpoco as a 'base follow' command: a third follow mechanism beside follow.sh. Generating every lab file from device.toml (no template files at all): tad needs its statements in the tree, and the schema decision already removes the one file worth generating.","about":"device-template","research":"device-template-drift-measured","supersedes":null,"amends":null,"scope":null,"tracked_by":"device-template-follow"} +{"id":"2026-11-18-bringup-steps-generic-in-docs-status-in-each-base","brief":"Bring-up steps: generic steps and their hard/soft edges in docs; each device base claims its status per step with proof and run; docs pulls it, unclaimed = not known yet","project":"linux-phone-oco/docs","date":"2026-11-18","decision":"Bring-up steps become data, in two halves joined the way parts already are (decision 2026-11-17-commons-and-device-bases).\n1. docs, the commons, keeps the generic steps: bringup_steps (id, title, stage of prepare/boot/console/kernel/power/storage/userspace/lab, ord, applies: any or a class such as boot:android, usb:gadget, power:battery, done_when, proof: a stable check name, proof_kind of host-check/phone-suite/build-check/witness/research, helper: the lpoco command or none, component: the catalogue part whose first light it is, guide: how it is done and the traps met with the records that met them, sources, checked_on) and bringup_step_edges (step, requires, kind hard or soft, group: edges sharing one are alternatives, why). Recorded by tad r bringup-step and bringup-edge; the edge record refuses a cycle. A step first met on one device goes in the catalogue scoped by applies, so there is one graph.\n2. Each device base claims its own status per step: a steps table (step, status of done/partial/failing/open/not-needed/unknown, proof: the check it ran, run: the record or test run, proven_on: the image or kernel hash, notes, updated), contract steps = 1 in devicebase.toml, recorded by tad r step. It ships in device-template only and reaches the labs by the template's release (decision 2026-11-18-device-template-follows-by-release); never copied by hand.\n3. docs pulls the claims into step_status (device x step) by records/feed-device-steps.sql, as feed-device-parts does. A step a base never claimed is unknown, \"not known yet\"; a base unreadable or without steps = 1 gives every step unknown and why. A new device made from the template starts with data/steps.json empty, so every step is not known yet until its base claims it - measured-not-claimed. A claim does not expire by age (a passed step stays passed for what it was proven on); proven_on lets a later kernel be told from it, and the runner re-proves.\n4. tad q bringup-chain [--device D] reads them: each step in order (depth over all edges, then stage, then ord), its status, proof, run, needs, and ready (every hard need done or not-needed, one per group) or waits - readiness computed, never stored.\n5. The guidebook is rendered from the same rows by make render into docs/guidebook.md: a chapter per stage, each step's done-when, needs, proof, helper or the gap, guide, and a column per device; verify keeps it fresh.\n6. The helpers map by the helper field: today lpoco bringup image pack/check/swap/bisect, initramfs build, lpoco lab fastboot, flash, provision, suite; a step with none is a helper to write. Later one runner walks ready steps: runs the helper, then the proof, and claims the result in the device's base; a step that changes the phone goes to its keeper's queue (half automated).\n7. Milestones may name step:ID@device as they name component: and feature:, so \"boots\" becomes a set of steps.\nSchema, records, query, seed (26 steps, 37 edges) and the failing test: research/bringup-steps/2026-11-18/. The tables, records and queries are docs' owner's to land (AGENTS.md); they are queued, not landed here.","why":"The author: the precise work of a bring-up is folded under \"boots\"; he wants every step, how it relates to the ones before and after, a guidebook made from the data, small helpers per step and later a runner; and the general table used by each device base for where it stands (2026-11-18). Measured (research bringup-steps-landscape): walleye's 26 steps are real and each done one has a check and a record; surya's road shows why steps need applies and not-needed; nobody outside keeps steps with edges and proofs, but each piece exists (Nura's per-device Cargo table, LAVA ids and expected lists, BitBake typed edges and stale stamps, Taskwarrior's computed READY, openQA hard/soft). The parts join already works between docs and two bases, so the step status needs no new mechanism. The draft ran in a scratch clone: checks pass, the chain orders, walleye's ready steps are its keeper's real queue.","rejected":"Steps as more components or more feature_support rows (a step is not a part: it has order and edges, and parts would mix \"the kernel reaches init\" with \"the speaker plays\"); steps per device only, in each lab (no shared graph, no guidebook, the next device starts from nothing); status typed in docs (decided against for parts on 2026-11-17: copies drift); edges as a comma list in the step row (no kind, no alternatives, no cycle check); the backlog as the step graph (backlog is one device's work and its tries; a step is generic and outlives the items that did it - items stay linked by run); an issue tracker DAG (beads, GitHub blocked-by: edges without proofs, outside the base); per-driver probe assertions as steps (bootrr's lesson: unstable names, per-board lists; a probe check can be a step's proof, derived from the devicetree as Collabora's kselftest does); a 30-day expiry as for parts (a step proven on an image stays proven for it; proven_on and the runner's re-proof answer regressions); a generated guidebook from prose pages (Nura's guide is hand-written and being rewritten).","about":"bringup-steps","research":"bringup-steps-landscape","supersedes":null,"amends":null,"scope":null,"tracked_by":"bringup-steps"} diff --git a/data/research.json b/data/research.json index 77baa1e7..23953713 100644 --- a/data/research.json +++ b/data/research.json @@ -55,3 +55,5 @@ {"id":"device-template-drift-measured","brief":"Two labs inherit device-template, carried by hand: the 13 generic files equal, but 8 drifts named and none caught; the template has no release, so nothing follows it","project":"linux-phone-oco/device-template","date":"2026-11-18","question":"Where does device-template come from, which repositories use it and how, and how is drift between it and each lab prevented? (the author, 2026-11-18)","found":"Origin: asked for 2026-11-10 (backlog device-template: the conveyor as its own repo, surya the first instance not the mould); made 2026-11-17 from what surya proved (dt-made, a GitHub template repository; decision 2026-11-17-the-phone-is-data: a lab holds data, every tool is lpoco's). Its device-base layer (#4-#15: parts, phone queries, lane-next, phone-stands, blocked_by, hardware, decision fields) grew on 11-17/18.\nUse: two children and no others (gh repo list linux-phone-oco, grenudi). surya-lab is older (2026-11-09) and was re-based by hand (dt-surya-from-template, surya-lab #81, #134); google-walleye-lab was made by Use this template (decision walleye-lab-repo: a one-shot squashed copy, no link back). Neither is a fork or subtree. Two slices reach them: idealkb's generic files by update-pins (consumers lists all three; idealkb.toml pins 0.15.0 everywhere) - and the template's own generic list (13 statements), which nothing follows: the template has no release, and every template change was landed again by hand in each lab within minutes (surya-lab #134 #136 #139 #155 #218, walleye #15 #20 #29 #80; walleye #208 still open and stale). devicebase.toml says template = \"2026-11-17\" in all three - true of no lab.\nDrift, measured by blob id (template 78fb062 vs surya-lab 972cebf, google-walleye-lab 87c4f4e): equal - every idealkb file, the 13 template statements, Makefile, install scripts, tad.yml, gather.yml, .gitignore, tables.toml. Named: (1) both labs carry a copy of the template's generic list, 5 entries behind; (2) records/hardware.sql, records/hardware-status.sql, queries/hardware.sql have two sources - born in the template, taken into idealkb 0.15.0, still listed by the template - so the 0.15.0 bump opened 'this base changed a generic file' PRs in all three (#21, #241, #233), each closed by hand; 0.14.0 did the same for the own records/backlog.sql (#16, #220, #212); (3) surya-lab's check.yml lacks the template's xargs -r, walleye extends the same file with a rust job; (4) surya-lab lacks tests/health/README.md; (5) AGENTS.md outside idealkb's part is per lab, unclassified; (6) device.toml shape: surya lacks [fastboot], the labs use keys the template does not show ([[flash.overlay]], [[hazard]], [hear], [[provision.install]], [host]) - the schema decision's; (7) the date pin; (8) walleye #208.\nHow drift is prevented today: it is not. No CI in a lab compares it to the template; idealkb's exit 3 sees only idealkb's files and fires false alarms when a file moves between sources. The template does not say which of its files are followed and which are made once. Failing test: template-drift.sh in the material (exit 1 today, 21 FAIL lines on the template, 2 per lab).","sources":"rhizoid-repo,idealkb-chain-follow","about":"device-template","material":"research/device-template/2026-11-18/","supersedes":null} {"id":"device-template-follow-world","brief":"Others carry a template forward by a pin and a failing check (cruft, copier), or not at all (GitHub templates, Yeoman); logic belongs in a pinned input (Nix), only files in the child","project":"linux-phone-oco/device-template","date":"2026-11-18","question":"How do others carry a template's later changes into its children and catch drift, and where do git-rhizoid and the manifest schema fit?","found":"cruft pins the template commit in .cruft.json; cruft check exits 1 when the child is behind, cruft diff --exit-code when it changed a template file; a weekly action opens the update as a PR. copier keeps _commit in an answers file, updates three-way (re-render the old version, diff, apply the new), marks conflicts inline or .rej, separates files made once (_skip_if_exists) and excluded ones, and check-update exits 2 when behind - behind and edited are two checks. GitHub template repositories copy once with no link and no update; actions-template-sync merges the template with -X theirs onto a branch (it would overwrite a lab's data; no failing check). Yeoman re-runs with an interactive conflicter, no pin. Nix: flake init -t copies once and never overwrites; logic consumed as a flake input is pinned in flake.lock and cannot drift (update-flake-lock opens the bump). projen names the files it synthesizes and fails the build when one is edited by hand. Renovate bumps a pin in any file but lays no files.\nInside the commons: idealkb's follow.sh/update-pins already is cruft's pair for a slice - a pin, the generic list, own files, exit 3 when the base changed a generic file, an hourly job landing through each base's CI (decision 2026-11-17-chain-follow-by-slice, which chose it for the template too; idealkb item follow-source-from-pin makes it source-agnostic). git-rhizoid is for whole forks (cuttings); its slice-consumption, followers-one-pin-bump and send-back-writes-the-upstream-item are open, CLI stubbed - the later home of the slice job, not today's. Decision 2026-11-18-device-manifest-schema-from-rust takes device.toml's shape out of the template's hands: the schema is projected from lpoco's types per release and each device.toml names its pin, so the example in the template stops being a manual (template-manifest-schema).\nTake: a release pin per source, the template naming which files it owns and which are made once (projen, copier's _skip_if_exists), two checks - behind and edited - failing in CI (cruft), the bump as a bot PR (update-pins). Set aside: template engines and three-way merges (labs are data; Python is refused here), -X theirs syncs, interactive conflicters, a third follow mechanism.","sources":"cruft,copier-updating,github-template-repos,actions-template-sync,yeoman-file-system,nix-flake-init,update-flake-lock,projen,renovate-regex-manager,rhizoid-repo,rhizoid-design-log","about":"device-template","material":"research/device-template/2026-11-18/","supersedes":null} {"id":"device-template-how-it-stands","brief":"device-template's children follow it by hand and drift unseen; decided: followed by release like idealkb, template-drift failing in CI; 6 items queued, first the classification","project":"linux-phone-oco/device-template","date":"2026-11-18","question":"Where does device-template's inheritance stand, and what is next?","found":"How it stands, 2026-11-18. device-template (a GitHub template, made 2026-11-17 from what surya proved) has two children: surya-lab (re-based by hand) and google-walleye-lab (Use this template). idealkb's slice reaches all three by update-pins; the template's own slice reaches the labs only by hand - its 13 statements are equal today because each change was landed three times, and 8 drifts are named that nothing catches (research device-template-drift-measured: stale list copies, three files with two sources and false-alarm bump PRs each idealkb release, surya's check.yml and tests/health/README.md, a date for a pin, walleye's stale PR 208, the manifest's shape).\nDecided (2026-11-18-device-template-follows-by-release, research device-template-follow-world): the template is followed like idealkb - every file named generic or made-once, a release pinned in devicebase.toml, laid by the same hourly update-pins once idealkb's follow-source-from-pin lands, and template-drift failing CI on drift. Queue, unranked: device-template template-classifies-its-files, template-releases, template-drift-in-ci, template-followed-by-update-pins; surya-lab surya-follows-template; google-walleye-lab walleye-follows-template. The failing test: research/device-template/2026-11-18/template-drift.sh (exit 1 today). device.toml's shape is template-manifest-schema's. The umbrella is docs item device-template-follow (orchestration's), which this carries out.","sources":"rhizoid-repo,idealkb-chain-follow","about":"device-template","material":null,"supersedes":null} +{"id":"bringup-steps-landscape","brief":"No one keeps bring-up steps as data with edges and proofs; walleye's real chain is 26 steps (17 done with proofs), surya's another road; docs' parts join carries step status as is","project":"linux-phone-oco/docs","date":"2026-11-18","question":"How should linux-phone keep every small step of bringing Linux up on a machine - what it needs, what it enables, its proof - generic for any machine, with each device base recording where it stands, so a guidebook, helpers and later a step runner can be made from it; and how do others do it?","found":"What is: the step-level truth of a bring-up lives only in each lab's backlog, session logs and research, folded on the face into \"boots\" or \"kernel\". Walleye's chain, rebuilt from google-walleye-lab: 26 steps from the bootloader read to the health suite, 17 done (each with a host check and a record: y1 alive by gpio-reserved-ranges and no earlycon, y2's gadget, banner2, z6's shell, z7's dmesg-clean and PMIC), 2 partial (stock measure, crash window: pstore yes, UART no), 1 failing (charger: c2 defers on tps61099), 6 open (UART, watchdog, UFS, USB network, rootfs, suite). Surya's chain (27 steps from surya-lab and docs) took another road: a distribution that already booted through U-Boot, systemd-boot and EFI, so its image, dtbo and stock-kernel steps are not-needed and PMIC and charger are not known. lab-tools has helpers for the image (lpoco bringup image pack/check/swap/bisect, initramfs build), fastboot, flash, provision, suite and suspend; none for UART, devicetree, banner, shell, PMIC, charger. The health suite's checks prove only the steps after a rootfs. docs already has the join this needs: components in docs, parts claimed in each device base (contract parts = 1), pulled by feed-device-parts into support_status, unclaimed = not known yet (decision 2026-11-17-commons-and-device-bases).\nOthers: nobody keeps bring-up steps as data with edges and a proof per step. Order is prose (Nura's porting and mainlining guides, UBports, Sailfish HADK, Qualcomm cover letters: boot to shell first); per-device status is a person's tick (Nura's Infobox Cargo table, Asahi's feature pages); proofs are flat lists (bootrr, dropped for unstable names and per-board lists; Collabora's DT probe kselftest; LAVA boot stages and test-case ids); dependencies are data only where machines run them (BitBake typed edges and input-keyed stamps, KernelCI, openQA fatal/ignore_failure, beads and Taskwarrior's computed READY). Nura's categories are levels as sets of checks.\nTried: the three tables, two records and the chain query in a scratch clone of docs: tad check passes, the edge record refuses a cycle, the generic chain orders 26 steps in 13 depths, walleye's claims give the queue walleye's keeper already has as ready (charger, watchdog, UFS, USB network), and the failing test passes with them and fails when one is removed.","sources":"nura-porting-guide,nura-infobox-device,nura-device-categorization,nura-hardware-ci,nura-mainlining-guide,asahi-feature-support,bootrr,collabora-dt-probe-kselftest,yocto-bsp-guide,yocto-compatible,bitbake-task-deps,lava-boot-action,lava-test-definition,kernelci-pipeline-config,openqa-docs,beads-issue-graph,github-issue-dependencies,taskwarrior-virtual-tags,ubports-porting,sailfish-hadk-subsystems","about":"bringup-steps","material":"research/bringup-steps/2026-11-18/","supersedes":null} +{"id":"bringup-steps-how-it-stands","brief":"Bring-up steps: decided (generic in docs, claimed per device base, pulled like parts), not built; 10 items unranked, first the schema the owner lands; the failing test is in the material","project":"linux-phone-oco/docs","date":"2026-11-18","question":"Where do bring-up steps as data stand, and what comes first?","found":"How it stands, 2026-11-18. Decided, not built: decision 2026-11-18-bringup-steps-generic-in-docs-status-in-each-base (research bringup-steps-landscape). Drafted and tried in a scratch clone, in research/bringup-steps/2026-11-18/: the three tables (schema.toml), the records bringup-step and bringup-edge, the query bringup-chain, a seed of 26 steps and 37 edges, walleye's 26 claims (17 done, 2 partial, 1 failing, 6 open), and the failing test bringup-chain-walleye.sh (fails on main: no query). Queue, unranked, for the author: docs bringup-steps-schema (the owner's to land), bringup-steps-seed, feed-device-steps, bringup-guidebook, milestones-step-terms; device-template steps-contract (after template-releases); google-walleye-lab walleye-steps-claimed and surya-lab surya-steps-claimed (after their template follow); lab-tools bringup-steps-helpers, then the research bringup-step-runner. Umbrella: bringup-steps. Open for the author: the stage list and the size of a step (26 for walleye's road so far); whether milestones should be rewritten as step sets; whether a claim should ever lapse by age (decided no: proven_on instead).","sources":"bitbake-task-deps,lava-test-definition,nura-infobox-device","about":"bringup-steps","material":null,"supersedes":null} diff --git a/data/session_log.json b/data/session_log.json index bb7ce05f..f5e24eb1 100644 --- a/data/session_log.json +++ b/data/session_log.json @@ -116,3 +116,4 @@ {"project":"linux-phone-oco/lab-tools","id":"2026-11-18-lpoco-host-check-names-stale-phone-side-pieces","entry_date":"2026-11-18","title":"lpoco host check names stale phone-side pieces","done":"Wrote host/tests/phone_pieces.rs first (failing), built blob_id, stale_pieces, Stale and check's print_stale_pieces in lpoco-host; landed as lab-tools PR 165, read back from main.","considered":"Making a stale piece fail the check: it only names it, as the item asks. Naming a missing piece as its own finding.","rejected":"My first report format (test piece / blob word): invented; review found health's 94-lab-pieces.sh writes piece-file:PATH and piece-package-NAME rows, so the parser follows those. Silent skips of unreadable lines: now an error and 'not measured'.","date":null,"about":"phone-pieces-drift-named"} {"project":"linux-phone-oco/lab-tools","id":"2026-11-18-lab-names-stale-phone-pieces","entry_date":"2026-11-18","title":"lab names stale phone pieces","done":"lpoco-lab test/health print which phone-side piece the run's report holds off origin/main; logic moved to lpoco_host::stale_lines and shared with lpoco host check (#170).","considered":"Printing from run_checks; judging only the report's JSON rows since phone stdout can carry noise; naming the oldest commit holding the blob.","rejected":"Reading device.toml from the manifest dir (a --device file of another name would be misjudged): the given file path is used. Printing before the pass/fail table: now printed after.","date":null,"about":"phone-pieces-drift-named"} {"project":"linux-phone-oco/device-template","id":"2026-11-18-template-research","entry_date":"2026-11-18","title":"Research: device-template, its children and drift","done":"Asked by the author through orchestration. Read the template's, labs' and idealkb's history and PRs (no phone, no lab changed); measured drift by blob id and manifest keys; a researcher read cruft, copier, GitHub templates, actions-template-sync, Yeoman, Nix, projen, Renovate at source. Recorded research device-template-drift-measured and device-template-follow-world, decision 2026-11-18-device-template-follows-by-release, six backlog items unranked, the hand-over device-template-how-it-stands, the subject's summary, and the failing test template-drift.sh (exit 1 today) in research/device-template/2026-11-18/.","considered":"Landing the test in device-template or a lab: neither has a failing-test convention and the labs are not this session's, so it lives in the research material and each item's proof names it. Checking device.toml's shape in the test: left to the schema decision (optional tables would give false failures).","rejected":"Re-recording device-template-follow (orchestration's, in progress): its rank would drop; the decision is tracked by it instead.","date":null,"about":"device-template"} +{"project":"linux-phone-oco/docs","id":"2026-11-18-research-bringup-steps","entry_date":"2026-11-18","title":"Research: bring-up steps as data","done":"bringup-steps-research.r1 (research lead, from orchestration). Mined google-walleye-lab (161 backlog items, 120 session logs, the bring-up order plan), surya-lab and docs' surya records, lab-tools' lpoco-bringup and lpoco-health tests (a researcher subagent), and docs' tables (components, features, feature_support, support_status, milestones, tests, the parts feed). Looked around at 22 outside sources (a researcher subagent). Drafted the tables, records, query, seed and failing test and ran them in a scratch clone of docs. Recorded 18 sources, the research, the decision, 11 backlog items unranked, the hand-over row; landed data and the material only.","considered":"Landing the schema myself; steps as components; status typed in docs; edges as a list field; an issue tracker; per-driver probe steps; a 30-day expiry","rejected":"Landing tables.toml, records and queries here: AGENTS.md sends them to the owner, orchestration. The rest: see the decision's rejected.","date":null,"about":"bringup-steps"} diff --git a/data/sources.json b/data/sources.json index 59f38189..2ae72cf8 100644 --- a/data/sources.json +++ b/data/sources.json @@ -239,3 +239,21 @@ {"project":"linux-phone-oco/docs","id":"update-flake-lock","title":"update-flake-lock: a PR per flake input update","url":"https://github.com/DeterminateSystems/update-flake-lock","author":null,"year":null,"by":"orchestration-renewed","takes":"A pinned input cannot drift; a scheduled job opens the bump as a PR"} {"project":"linux-phone-oco/docs","id":"projen","title":"projen: project files synthesized and kept read-only","url":"https://github.com/projen/projen","author":null,"year":null,"by":"orchestration-renewed","takes":"The template names the files it owns and an anti-tamper check fails the build when one is edited by hand"} {"project":"linux-phone-oco/docs","id":"renovate-regex-manager","title":"Renovate: custom regex managers","url":"https://docs.renovatebot.com/modules/manager/regex/","author":null,"year":null,"by":"orchestration-renewed","takes":"A pin in any file can be bumped by PR; it bumps numbers, it does not lay files"} +{"project":"linux-phone-oco/docs","id":"nura-porting-guide","title":"Porting to a new device","url":"https://wiki.nura.eco/wiki/Porting_to_a_new_device","author":null,"year":2026,"by":"Nura","takes":"the first steps' order (device package, kernel package, flash, USB networking); no proof per step"} +{"project":"linux-phone-oco/docs","id":"nura-infobox-device","title":"Template:Infobox device","url":"https://wiki.nura.eco/wiki/Template:Infobox_device","author":null,"year":2026,"by":"Nura","takes":"per-device status fields (Y/P/N) stored as a Cargo table and queried: the instance side, without proofs"} +{"project":"linux-phone-oco/docs","id":"nura-device-categorization","title":"Device categorization","url":"https://docs.nura.eco/pmaports/main/packaging/device-categorization.html","author":null,"year":2026,"by":"Nura","takes":"levels as gate sets over checks: our milestones over step proofs"} +{"project":"linux-phone-oco/docs","id":"nura-hardware-ci","title":"Hardware CI","url":"https://docs.nura.eco/pmaports/main/ci/hardware-ci.html","author":null,"year":2026,"by":"Nura","takes":"generic test packages a device opts into; boot and system test layers not built yet"} +{"project":"linux-phone-oco/docs","id":"nura-mainlining-guide","title":"Mainlining Guide","url":"https://wiki.nura.eco/wiki/Mainlining_Guide","author":null,"year":2026,"by":"Nura","takes":"minimal boot = RAM + serial, then one feature after another; dtbs_check"} +{"project":"linux-phone-oco/docs","id":"asahi-feature-support","title":"Asahi Linux feature support (M3)","url":"https://asahilinux.org/docs/platform/feature-support/m3/","author":null,"year":2026,"by":"Asahi Linux","takes":"SoC blocks apart from device integration; a state that says where the code lives"} +{"project":"linux-phone-oco/docs","id":"collabora-dt-probe-kselftest","title":"A new kselftest for verifying driver probe of devicetree-based platforms","url":"https://www.collabora.com/news-and-blog/blog/2023/12/11/a-new-kselftest-for-verifying-driver-probe-of-devicetree-based-platforms","author":null,"year":2023,"by":"Collabora","takes":"derive probed-or-not from the live devicetree instead of a hand list"} +{"project":"linux-phone-oco/docs","id":"yocto-bsp-guide","title":"Yocto Project Board Support Package Developer's Guide","url":"https://docs.yoctoproject.org/5.0.13/bsp-guide/bsp.html","author":null,"year":null,"by":"Yocto Project","takes":"a checklist of artefacts, not of bring-up steps"} +{"project":"linux-phone-oco/docs","id":"yocto-compatible","title":"Yocto Project Compatible","url":"https://docs.yoctoproject.org/test-manual/yocto-project-compatible.html","author":null,"year":null,"by":"Yocto Project","takes":"a declared answer kept apart from a checked one"} +{"project":"linux-phone-oco/docs","id":"bitbake-task-deps","title":"BitBake user manual: syntax and operators, task dependencies","url":"https://docs.yoctoproject.org/bitbake/bitbake-user-manual/bitbake-user-manual-metadata.html","author":null,"year":null,"by":"Yocto Project","takes":"typed task edges (after/before, deptask, rdeptask); stamps keyed on inputs, so a changed input makes a task stale"} +{"project":"linux-phone-oco/docs","id":"lava-boot-action","title":"LAVA boot action: common","url":"https://docs.lavasoftware.org/lava/technical-references/job-definition/actions/boot/common.html","author":null,"year":null,"by":"Linaro","takes":"boot stages proven by console matchers: bootloader message, kernel-start-message, prompts"} +{"project":"linux-phone-oco/docs","id":"kernelci-pipeline-config","title":"KernelCI pipeline configuration","url":"https://docs.kernelci.org/components/maestro/pipeline/config-reference/","author":null,"year":null,"by":"KernelCI","takes":"generic jobs x platforms; a job waits on another's result"} +{"project":"linux-phone-oco/docs","id":"openqa-docs","title":"openQA documentation","url":"https://open.qa/docs/","author":null,"year":null,"by":"openSUSE","takes":"fatal vs ignore_failure (hard vs soft), START_AFTER_TEST, screenshot needles as proof"} +{"project":"linux-phone-oco/docs","id":"beads-issue-graph","title":"beads","url":"https://github.com/steveyegge/beads","author":"Steve Yegge","year":2025,"by":"orchestration-renewed","takes":"blocks edges and bd ready: ready computed from open blockers"} +{"project":"linux-phone-oco/docs","id":"github-issue-dependencies","title":"Creating issue dependencies","url":"https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/creating-issue-dependencies","author":null,"year":null,"by":"GitHub","takes":"blocked-by edges as data; no proof"} +{"project":"linux-phone-oco/docs","id":"taskwarrior-virtual-tags","title":"Taskwarrior tags and virtual tags","url":"https://taskwarrior.org/docs/tags/","author":null,"year":null,"by":"Taskwarrior","takes":"READY and BLOCKED computed at query time, never stored"} +{"project":"linux-phone-oco/docs","id":"ubports-porting","title":"Ubuntu Touch porting introduction","url":"https://docs.ubports.com/en/latest/porting/introduction/index.html","author":null,"year":null,"by":"UBports","takes":"porting stages without a proof per stage"} +{"project":"linux-phone-oco/docs","id":"sailfish-hadk-subsystems","title":"Sailfish HADK: subsystems","url":"https://hadk.sailfishos.org/subsystems/","author":null,"year":null,"by":"Jolla","takes":"concrete proof commands for phone subsystems (test_gps, list-modems)"} diff --git a/data/summaries.json b/data/summaries.json index 80c94fc3..0704aff3 100644 --- a/data/summaries.json +++ b/data/summaries.json @@ -6,3 +6,4 @@ {"about":"phone-side-pieces","date":"2026-11-18","says":"Phone-side pieces (what lpoco puts on a phone) are decided, not built. Every lab phone's pieces ride the lab-tools package - the keep-awake first, as lpoco-health awake (lpoco-awake) - and walleye's gadget init and ACM console go under lpoco bringup (bringup-generic-init); a device names roof pieces by token and keeps only its own files (decision 2026-11-18-phone-side-pieces-under-the-roof). Drift is named, not trusted: the phone reports each package version and each declared file's git blob id every boot (health-reports-pieces), and lpoco host check names a stale one from the last gathered report (phone-pieces-drift-named, its failing test written first; text in research/phone-side-pieces/2026-11-18/). device.toml stays data, declared once in Rust with a schema projected per release (decision 2026-11-18-device-manifest-schema-from-rust, manifest-one-schema and one row per device repository). Upstream: three questions (sxmo autosuspend backoff, sxmo suspend stops by profile, qcom_wdt armed in suspend) wait on the author's word. Hand-over: phone-side-pieces-how-it-stands.","condenses":"2026-11-18-device-manifest-schema-from-rust, 2026-11-18-phone-side-pieces-under-the-roof, 2026-11-18-research-phone-side-pieces, device-declaration-typed-landscape, phone-side-pieces-how-it-stands, phone-side-pieces-landscape"} {"about":"upstream-forks","date":"2026-11-18","says":"Our forks live under the author's account - grenudi/sxmo-utils (fork-sxmo-utils, a mirror of sr.ht) and grenudi/linux (fork-linux), transferred from the organisation so one history stays (decision 2026-11-18-upstream-forks, research upstream-forks-landscape). Each upstream item is a topic branch off the untouched tracking branch; a never-rebased lab/test branch is what phones run - sxmo-utils as a tagged lab apk (sxmo-utils-lab-apk), kernels by each lab's route. One upstreams lane coordinates (upstreams-lane, waiting on orchestration). Written, unsent, each waiting on its phone proof then the author's word: the sxmo series of three (sxmo-autosuspend-backoff, sxmo-suspend-stop-by-profile, sxmo-surya-sensors-suspend; research sxmo-suspend-fixes; spec in the series) and the RFC kernel series pmic-wdt-wake-in-suspend, which supersedes qcom-wdt-armed-in-suspend (research pmic-wdt-way-back; proofs surya-pmic-wdt-proof, walleye-pmic-wdt-proof in the device bases). rhizoid is not used yet; what it needs went to it as rhizoid-carries-mail-forks.","condenses":"2026-11-18-upstream-forks, sxmo-suspend-fixes, upstream-forks-landscape"} {"about":"device-template","date":"2026-11-18","says":"device-template (asked for 2026-11-10, made 2026-11-17 as a GitHub template from what surya proved; a lab holds data, tools are lpoco's) has two children: surya-lab, re-based by hand, and google-walleye-lab, made by Use this template. idealkb's generic files reach all three by update-pins; the template's own 13 statements reach the labs only by hand, landed three times per change, and 8 drifts nothing catches are named in research device-template-drift-measured (stale list copies, three files with two sources and false-alarm bump PRs each idealkb release, surya's check.yml and tests/health/README.md, a date as pin, walleye's stale PR 208, the manifest's shape). Decision 2026-11-18-device-template-follows-by-release (research device-template-follow-world: cruft, copier, projen, Nix): the template is followed like idealkb - each file generic or made-once, a release pinned in devicebase.toml, laid by update-pins, template-drift failing CI. Queue, unranked: template-classifies-its-files first, then template-releases, template-drift-in-ci, template-followed-by-update-pins (waits on idealkb follow-source-from-pin), surya-follows-template, walleye-follows-template. The failing test: research/device-template/2026-11-18/template-drift.sh. Hand-over: device-template-how-it-stands; umbrella device-template-follow; device.toml's shape is template-manifest-schema's.","condenses":"2026-11-18-device-template-follows-by-release, device-template-drift-measured, device-template-follow-world, device-template-how-it-stands"} +{"about":"bringup-steps","date":"2026-11-18","says":"Bring-up steps as data are decided, not built (decision 2026-11-18-bringup-steps-generic-in-docs-status-in-each-base, research bringup-steps-landscape). The generic steps and their hard/soft edges (with alternatives) live in docs, the commons; each device base claims its own status per step - proof, run, proven_on - by a steps contract that device-template ships and labs follow by release; docs pulls the claims into step_status as it pulls parts, and a step no base claimed is not known yet, so a new device starts all unknown. tad q bringup-chain orders the steps and says which are ready; a guidebook is rendered from the same rows; each step names its lpoco helper or the gap, and a runner later walks the ready steps. Walleye's real road is 26 steps: 17 done with checks and records, the charger failing on its tps61099 supplier. Drafts and the failing test: research/bringup-steps/2026-11-18/. Queue unranked under bringup-steps: first bringup-steps-schema, the owner's to land (bringup-steps-how-it-stands).","condenses":"2026-11-18-bringup-steps-generic-in-docs-status-in-each-base, 2026-11-18-research-bringup-steps, bringup-steps-how-it-stands, bringup-steps-landscape"} diff --git a/docs/backlog.md b/docs/backlog.md index 925fdbe4..9e201a6c 100644 --- a/docs/backlog.md +++ b/docs/backlog.md @@ -4528,3 +4528,278 @@ Proof About : device-template + + + +### Bring-up steps as data: every step that makes Linux run on a machine, generic in docs, each device's status claimed in its own base, a guidebook and helpers made from it + +Project +: linux-phone-oco/docs + +Status +: open + +Note +: Decided 2026-11-18-bringup-steps-generic-in-docs-status-in-each-base (research bringup-steps-landscape). The pieces are the items about bringup-steps, unranked for the author. + +Opened +: 2026-11-18 + +Blocked by +: bringup-steps-schema,bringup-steps-seed,feed-device-steps,walleye-steps-claimed + +Proof +: research/bringup-steps/2026-11-18/bringup-chain-walleye.sh passes in docs: tad q bringup-chain --device google-walleye lists walleye's steps in order, each proven one with its proof and run, none unknown (fails today: no query bringup-chain) + +About +: commons-only + + + +### The bring-up step tables in docs: bringup_steps, bringup_step_edges, step_status, the records bringup-step and bringup-edge, and the query bringup-chain + +Project +: linux-phone-oco/docs + +Status +: open + +Note +: Ready to land as drafted in research/bringup-steps/2026-11-18 (schema.toml, records/, queries/): tried in a scratch clone at 3596bb3. The owner's to land (AGENTS.md: schema, records, queries). + +Opened +: 2026-11-18 + +Proof +: tad check passes with the three tables; tad r bringup-edge refuses an edge that closes a cycle; tad q bringup-chain answers with no device (every status unknown) + +About +: bringup-steps + + + +### Seed the generic steps: 26 steps and 37 edges from walleye's real chain, surya's road checked against it + +Project +: linux-phone-oco/docs + +Status +: open + +Note +: sh research/bringup-steps/2026-11-18/seed.sh in docs, through the records + +Opened +: 2026-11-18 + +Blocked by +: bringup-steps-schema + +Proof +: tad q bringup-chain lists 26 steps, bootloader and stock steps at depth 0, health-suite-runs last; tad check passes + +About +: bringup-steps + + + +### The steps contract in the template: a steps table, the record step, contract steps = 1 in devicebase.toml, data/steps.json empty, in the template's followed files + +Project +: linux-phone-oco/device-template + +Status +: open + +Note +: Reaches labs by the template release (decision 2026-11-18-device-template-follows-by-release), never by hand. A new device starts with no claim: every step not known yet. + +Opened +: 2026-11-18 + +Blocked by +: bringup-steps-schema,template-releases + +Proof +: in the template, tad check passes with an empty steps table; tad r step --step shell-on-console --status done --proof X --run Y writes one row and refuses a status outside the six + +About +: bringup-steps + + + +### Pull each device base's steps into step_status: records/feed-device-steps.sql and a device-steps-unknown fallback in bin/run-feeds.sh + +Project +: linux-phone-oco/docs + +Status +: open + +Note +: As feed-device-parts: read devicebase.toml (steps = 1) and data/steps.json from the base on main; a step not claimed is unknown, not known yet; a claim of a step docs does not know is dropped and named. + +Opened +: 2026-11-18 + +Blocked by +: bringup-steps-schema,steps-contract + +Proof +: run against a base without steps = 1, every step of that device is unknown with the reason; against google-walleye-lab after its claims, research/bringup-steps/2026-11-18/bringup-chain-walleye.sh passes + +About +: bringup-steps + + + +### walleye claims its bring-up steps in its own base, from its records + +Project +: linux-phone-oco/google-walleye-lab + +Status +: open + +Note +: The 26 claims are written out in research/bringup-steps/2026-11-18/claims-walleye.sh, each run a record of google-walleye-lab. Data only; no phone. + +Opened +: 2026-11-18 + +Blocked by +: steps-contract,walleye-follows-template + +Needs +: build + +Device +: google-walleye + +Proof +: research/bringup-steps/2026-11-18/bringup-chain-walleye.sh passes in docs after make feeds + +About +: bringup-steps + + + +### surya claims its bring-up steps in its own base, from its records (its road: a booting distribution, the image steps not-needed) + +Project +: linux-phone-oco/surya-lab + +Status +: open + +Note +: The claims are listed in research/bringup-steps/2026-11-18/README.md (Surya's path); PMIC and charger stay unknown until measured. + +Opened +: 2026-11-18 + +Blocked by +: steps-contract,surya-follows-template + +Needs +: build + +Device +: xiaomi-surya + +Proof +: tad q bringup-chain --device xiaomi-surya in docs shows health-suite-runs done with run 2026-11-17-1550-lpoco-health-v017, and no step unknown but pmic-bound and charger-online + +About +: bringup-steps + + + +### The guidebook rendered from the steps: docs/guidebook.md by make render, a chapter per stage, each step's done-when, needs, proof, helper or gap, guide, and a column per device + +Project +: linux-phone-oco/docs + +Status +: open + +Opened +: 2026-11-18 + +Blocked by +: bringup-steps-seed + +Proof +: make verify fails when docs/guidebook.md is stale against the rows, and the page lists the 26 steps in bringup-chain's order with every hard need before its step + +About +: bringup-steps + + + +### The helper map: lpoco bringup steps reads docs' chain and names, per step, its lpoco command or the gap + +Project +: linux-phone-oco/lab-tools + +Status +: open + +Note +: Today: image pack/check/swap/bisect, initramfs build, lab fastboot, flash, provision, suite. Gaps: UART, banner, shell, dmesg map, PMIC, charger, storage. Each gap filled becomes its own item. + +Opened +: 2026-11-18 + +Blocked by +: bringup-steps-seed + +Proof +: a test in lab-tools: every helper named in docs' bringup_steps is a subcommand lpoco --help lists at the pinned release, and lpoco bringup steps --device google-walleye prints the gaps + +About +: bringup-steps + + + +### Research: a runner that walks a device's ready steps - helper, then proof, then the claim in its base; a step that changes the phone queued to its keeper + +Project +: linux-phone-oco/lab-tools + +Status +: open + +Opened +: 2026-11-18 + +Blocked by +: bringup-steps-helpers,feed-device-steps + +Proof +: a research row and a decision with what was rejected, and its failing test: the runner on a made-up device with two ready steps runs each helper and proof and writes two claims + +About +: bringup-steps + + + +### Milestones name steps: step:ID@device in criteria, read from step_status by milestone-readiness + +Project +: linux-phone-oco/docs + +Status +: open + +Opened +: 2026-11-18 + +Blocked by +: feed-device-steps + +Proof +: milestone-readiness counts a step term done only when step_status says done for that device; a walleye milestone 'reaches a shell' over step:shell-on-console@google-walleye reads ready + +About +: bringup-steps diff --git a/docs/decisions.md b/docs/decisions.md index 9a687508..3d6db8af 100644 --- a/docs/decisions.md +++ b/docs/decisions.md @@ -1752,3 +1752,42 @@ Research Tracked by : device-template-follow + + + +### 2026-11-18-bringup-steps-generic-in-docs-status-in-each-base + +Brief +: Bring-up steps: generic steps and their hard/soft edges in docs; each device base claims its status per step with proof and run; docs pulls it, unclaimed = not known yet + +Project +: linux-phone-oco/docs + +Date +: 2026-11-18 + +Decision +: Bring-up steps become data, in two halves joined the way parts already are (decision 2026-11-17-commons-and-device-bases). +1. docs, the commons, keeps the generic steps: bringup_steps (id, title, stage of prepare/boot/console/kernel/power/storage/userspace/lab, ord, applies: any or a class such as boot:android, usb:gadget, power:battery, done_when, proof: a stable check name, proof_kind of host-check/phone-suite/build-check/witness/research, helper: the lpoco command or none, component: the catalogue part whose first light it is, guide: how it is done and the traps met with the records that met them, sources, checked_on) and bringup_step_edges (step, requires, kind hard or soft, group: edges sharing one are alternatives, why). Recorded by tad r bringup-step and bringup-edge; the edge record refuses a cycle. A step first met on one device goes in the catalogue scoped by applies, so there is one graph. +2. Each device base claims its own status per step: a steps table (step, status of done/partial/failing/open/not-needed/unknown, proof: the check it ran, run: the record or test run, proven_on: the image or kernel hash, notes, updated), contract steps = 1 in devicebase.toml, recorded by tad r step. It ships in device-template only and reaches the labs by the template's release (decision 2026-11-18-device-template-follows-by-release); never copied by hand. +3. docs pulls the claims into step_status (device x step) by records/feed-device-steps.sql, as feed-device-parts does. A step a base never claimed is unknown, "not known yet"; a base unreadable or without steps = 1 gives every step unknown and why. A new device made from the template starts with data/steps.json empty, so every step is not known yet until its base claims it - measured-not-claimed. A claim does not expire by age (a passed step stays passed for what it was proven on); proven_on lets a later kernel be told from it, and the runner re-proves. +4. tad q bringup-chain [--device D] reads them: each step in order (depth over all edges, then stage, then ord), its status, proof, run, needs, and ready (every hard need done or not-needed, one per group) or waits - readiness computed, never stored. +5. The guidebook is rendered from the same rows by make render into docs/guidebook.md: a chapter per stage, each step's done-when, needs, proof, helper or the gap, guide, and a column per device; verify keeps it fresh. +6. The helpers map by the helper field: today lpoco bringup image pack/check/swap/bisect, initramfs build, lpoco lab fastboot, flash, provision, suite; a step with none is a helper to write. Later one runner walks ready steps: runs the helper, then the proof, and claims the result in the device's base; a step that changes the phone goes to its keeper's queue (half automated). +7. Milestones may name step:ID@device as they name component: and feature:, so "boots" becomes a set of steps. +Schema, records, query, seed (26 steps, 37 edges) and the failing test: research/bringup-steps/2026-11-18/. The tables, records and queries are docs' owner's to land (AGENTS.md); they are queued, not landed here. + +Why +: The author: the precise work of a bring-up is folded under "boots"; he wants every step, how it relates to the ones before and after, a guidebook made from the data, small helpers per step and later a runner; and the general table used by each device base for where it stands (2026-11-18). Measured (research bringup-steps-landscape): walleye's 26 steps are real and each done one has a check and a record; surya's road shows why steps need applies and not-needed; nobody outside keeps steps with edges and proofs, but each piece exists (Nura's per-device Cargo table, LAVA ids and expected lists, BitBake typed edges and stale stamps, Taskwarrior's computed READY, openQA hard/soft). The parts join already works between docs and two bases, so the step status needs no new mechanism. The draft ran in a scratch clone: checks pass, the chain orders, walleye's ready steps are its keeper's real queue. + +Rejected +: Steps as more components or more feature_support rows (a step is not a part: it has order and edges, and parts would mix "the kernel reaches init" with "the speaker plays"); steps per device only, in each lab (no shared graph, no guidebook, the next device starts from nothing); status typed in docs (decided against for parts on 2026-11-17: copies drift); edges as a comma list in the step row (no kind, no alternatives, no cycle check); the backlog as the step graph (backlog is one device's work and its tries; a step is generic and outlives the items that did it - items stay linked by run); an issue tracker DAG (beads, GitHub blocked-by: edges without proofs, outside the base); per-driver probe assertions as steps (bootrr's lesson: unstable names, per-board lists; a probe check can be a step's proof, derived from the devicetree as Collabora's kselftest does); a 30-day expiry as for parts (a step proven on an image stays proven for it; proven_on and the runner's re-proof answer regressions); a generated guidebook from prose pages (Nura's guide is hand-written and being rewritten). + +About +: bringup-steps + +Research +: bringup-steps-landscape + +Tracked by +: bringup-steps diff --git a/docs/index.md b/docs/index.md index 47035b52..a38eff4d 100644 --- a/docs/index.md +++ b/docs/index.md @@ -4,10 +4,10 @@ The memory of linux-phone-oco, whose goal is Linux phones as good as Android for everyday use, and better: which phone supports which hardware, how we know, why decisions were made, and what is next. Plain versioned data; see AGENTS.md. The plan, and where Linux phones stand against Android and iOS: [the grand picture](picture.md), and the main screen, [features against Android and iOS](feature_support.md). -- [Backlog](backlog.md): 182 +- [Backlog](backlog.md): 193 - [Components](components.md): 21 - [Concepts](concepts.md): 10 -- [Decisions](decisions.md): 71 +- [Decisions](decisions.md): 72 - [Devices](devices.md): 3 - [Feature Support](feature_support.md): 101 - [Features](features.md): 46 @@ -21,11 +21,11 @@ The memory of linux-phone-oco, whose goal is Linux phones as good as Android for - [Milestones](milestones.md): 23 - [Platforms](platforms.md): 7 - [Problems](problems.md): 17 -- [Research](research.md): 57 -- [Session Log](session_log.md): 118 +- [Research](research.md): 59 +- [Session Log](session_log.md): 119 - [Shell Releases](shell_releases.md): 2 -- [Sources](sources.md): 241 -- [Summaries](summaries.md): 8 +- [Sources](sources.md): 259 +- [Summaries](summaries.md): 9 - [Support Status](support_status.md): 63 - [Test Results](test_results.md): 0 - [Test Runs](test_runs.md): 0 diff --git a/docs/research.md b/docs/research.md index ee3fa865..7046236d 100644 --- a/docs/research.md +++ b/docs/research.md @@ -1485,3 +1485,58 @@ Sources About : device-template + + + +### bringup-steps-landscape + +Brief +: No one keeps bring-up steps as data with edges and proofs; walleye's real chain is 26 steps (17 done with proofs), surya's another road; docs' parts join carries step status as is + +Project +: linux-phone-oco/docs + +Date +: 2026-11-18 + +Question +: How should linux-phone keep every small step of bringing Linux up on a machine - what it needs, what it enables, its proof - generic for any machine, with each device base recording where it stands, so a guidebook, helpers and later a step runner can be made from it; and how do others do it? + +Found +: What is: the step-level truth of a bring-up lives only in each lab's backlog, session logs and research, folded on the face into "boots" or "kernel". Walleye's chain, rebuilt from google-walleye-lab: 26 steps from the bootloader read to the health suite, 17 done (each with a host check and a record: y1 alive by gpio-reserved-ranges and no earlycon, y2's gadget, banner2, z6's shell, z7's dmesg-clean and PMIC), 2 partial (stock measure, crash window: pstore yes, UART no), 1 failing (charger: c2 defers on tps61099), 6 open (UART, watchdog, UFS, USB network, rootfs, suite). Surya's chain (27 steps from surya-lab and docs) took another road: a distribution that already booted through U-Boot, systemd-boot and EFI, so its image, dtbo and stock-kernel steps are not-needed and PMIC and charger are not known. lab-tools has helpers for the image (lpoco bringup image pack/check/swap/bisect, initramfs build), fastboot, flash, provision, suite and suspend; none for UART, devicetree, banner, shell, PMIC, charger. The health suite's checks prove only the steps after a rootfs. docs already has the join this needs: components in docs, parts claimed in each device base (contract parts = 1), pulled by feed-device-parts into support_status, unclaimed = not known yet (decision 2026-11-17-commons-and-device-bases). +Others: nobody keeps bring-up steps as data with edges and a proof per step. Order is prose (Nura's porting and mainlining guides, UBports, Sailfish HADK, Qualcomm cover letters: boot to shell first); per-device status is a person's tick (Nura's Infobox Cargo table, Asahi's feature pages); proofs are flat lists (bootrr, dropped for unstable names and per-board lists; Collabora's DT probe kselftest; LAVA boot stages and test-case ids); dependencies are data only where machines run them (BitBake typed edges and input-keyed stamps, KernelCI, openQA fatal/ignore_failure, beads and Taskwarrior's computed READY). Nura's categories are levels as sets of checks. +Tried: the three tables, two records and the chain query in a scratch clone of docs: tad check passes, the edge record refuses a cycle, the generic chain orders 26 steps in 13 depths, walleye's claims give the queue walleye's keeper already has as ready (charger, watchdog, UFS, USB network), and the failing test passes with them and fails when one is removed. + +Sources +: nura-porting-guide,nura-infobox-device,nura-device-categorization,nura-hardware-ci,nura-mainlining-guide,asahi-feature-support,bootrr,collabora-dt-probe-kselftest,yocto-bsp-guide,yocto-compatible,bitbake-task-deps,lava-boot-action,lava-test-definition,kernelci-pipeline-config,openqa-docs,beads-issue-graph,github-issue-dependencies,taskwarrior-virtual-tags,ubports-porting,sailfish-hadk-subsystems + +About +: bringup-steps + +Material +: research/bringup-steps/2026-11-18/ + + + +### bringup-steps-how-it-stands + +Brief +: Bring-up steps: decided (generic in docs, claimed per device base, pulled like parts), not built; 10 items unranked, first the schema the owner lands; the failing test is in the material + +Project +: linux-phone-oco/docs + +Date +: 2026-11-18 + +Question +: Where do bring-up steps as data stand, and what comes first? + +Found +: How it stands, 2026-11-18. Decided, not built: decision 2026-11-18-bringup-steps-generic-in-docs-status-in-each-base (research bringup-steps-landscape). Drafted and tried in a scratch clone, in research/bringup-steps/2026-11-18/: the three tables (schema.toml), the records bringup-step and bringup-edge, the query bringup-chain, a seed of 26 steps and 37 edges, walleye's 26 claims (17 done, 2 partial, 1 failing, 6 open), and the failing test bringup-chain-walleye.sh (fails on main: no query). Queue, unranked, for the author: docs bringup-steps-schema (the owner's to land), bringup-steps-seed, feed-device-steps, bringup-guidebook, milestones-step-terms; device-template steps-contract (after template-releases); google-walleye-lab walleye-steps-claimed and surya-lab surya-steps-claimed (after their template follow); lab-tools bringup-steps-helpers, then the research bringup-step-runner. Umbrella: bringup-steps. Open for the author: the stage list and the size of a step (26 for walleye's road so far); whether milestones should be rewritten as step sets; whether a claim should ever lapse by age (decided no: proven_on instead). + +Sources +: bitbake-task-deps,lava-test-definition,nura-infobox-device + +About +: bringup-steps diff --git a/docs/session_log.md b/docs/session_log.md index 0974d287..384933e4 100644 --- a/docs/session_log.md +++ b/docs/session_log.md @@ -2624,3 +2624,27 @@ Rejected About : device-template + +--- + + + +### Research: bring-up steps as data + +Project +: linux-phone-oco/docs + +Entry date +: 2026-11-18 + +Done +: bringup-steps-research.r1 (research lead, from orchestration). Mined google-walleye-lab (161 backlog items, 120 session logs, the bring-up order plan), surya-lab and docs' surya records, lab-tools' lpoco-bringup and lpoco-health tests (a researcher subagent), and docs' tables (components, features, feature_support, support_status, milestones, tests, the parts feed). Looked around at 22 outside sources (a researcher subagent). Drafted the tables, records, query, seed and failing test and ran them in a scratch clone of docs. Recorded 18 sources, the research, the decision, 11 backlog items unranked, the hand-over row; landed data and the material only. + +Considered +: Landing the schema myself; steps as components; status typed in docs; edges as a list field; an issue tracker; per-driver probe steps; a 30-day expiry + +Rejected +: Landing tables.toml, records and queries here: AGENTS.md sends them to the owner, orchestration. The rest: see the decision's rejected. + +About +: bringup-steps diff --git a/docs/sources.md b/docs/sources.md index b7ac4002..3404a68a 100644 --- a/docs/sources.md +++ b/docs/sources.md @@ -4048,3 +4048,318 @@ By Takes : A pin in any file can be bumped by PR; it bumps numbers, it does not lay files + + + +### Porting to a new device + +Project +: linux-phone-oco/docs + +Url +: https://wiki.nura.eco/wiki/Porting_to_a_new_device + +Year +: 2026 + +By +: Nura + +Takes +: the first steps' order (device package, kernel package, flash, USB networking); no proof per step + + + +### Template:Infobox device + +Project +: linux-phone-oco/docs + +Url +: https://wiki.nura.eco/wiki/Template:Infobox_device + +Year +: 2026 + +By +: Nura + +Takes +: per-device status fields (Y/P/N) stored as a Cargo table and queried: the instance side, without proofs + + + +### Device categorization + +Project +: linux-phone-oco/docs + +Url +: https://docs.nura.eco/pmaports/main/packaging/device-categorization.html + +Year +: 2026 + +By +: Nura + +Takes +: levels as gate sets over checks: our milestones over step proofs + + + +### Hardware CI + +Project +: linux-phone-oco/docs + +Url +: https://docs.nura.eco/pmaports/main/ci/hardware-ci.html + +Year +: 2026 + +By +: Nura + +Takes +: generic test packages a device opts into; boot and system test layers not built yet + + + +### Mainlining Guide + +Project +: linux-phone-oco/docs + +Url +: https://wiki.nura.eco/wiki/Mainlining_Guide + +Year +: 2026 + +By +: Nura + +Takes +: minimal boot = RAM + serial, then one feature after another; dtbs_check + + + +### Asahi Linux feature support (M3) + +Project +: linux-phone-oco/docs + +Url +: https://asahilinux.org/docs/platform/feature-support/m3/ + +Year +: 2026 + +By +: Asahi Linux + +Takes +: SoC blocks apart from device integration; a state that says where the code lives + + + +### A new kselftest for verifying driver probe of devicetree-based platforms + +Project +: linux-phone-oco/docs + +Url +: https://www.collabora.com/news-and-blog/blog/2023/12/11/a-new-kselftest-for-verifying-driver-probe-of-devicetree-based-platforms + +Year +: 2023 + +By +: Collabora + +Takes +: derive probed-or-not from the live devicetree instead of a hand list + + + +### Yocto Project Board Support Package Developer's Guide + +Project +: linux-phone-oco/docs + +Url +: https://docs.yoctoproject.org/5.0.13/bsp-guide/bsp.html + +By +: Yocto Project + +Takes +: a checklist of artefacts, not of bring-up steps + + + +### Yocto Project Compatible + +Project +: linux-phone-oco/docs + +Url +: https://docs.yoctoproject.org/test-manual/yocto-project-compatible.html + +By +: Yocto Project + +Takes +: a declared answer kept apart from a checked one + + + +### BitBake user manual: syntax and operators, task dependencies + +Project +: linux-phone-oco/docs + +Url +: https://docs.yoctoproject.org/bitbake/bitbake-user-manual/bitbake-user-manual-metadata.html + +By +: Yocto Project + +Takes +: typed task edges (after/before, deptask, rdeptask); stamps keyed on inputs, so a changed input makes a task stale + + + +### LAVA boot action: common + +Project +: linux-phone-oco/docs + +Url +: https://docs.lavasoftware.org/lava/technical-references/job-definition/actions/boot/common.html + +By +: Linaro + +Takes +: boot stages proven by console matchers: bootloader message, kernel-start-message, prompts + + + +### KernelCI pipeline configuration + +Project +: linux-phone-oco/docs + +Url +: https://docs.kernelci.org/components/maestro/pipeline/config-reference/ + +By +: KernelCI + +Takes +: generic jobs x platforms; a job waits on another's result + + + +### openQA documentation + +Project +: linux-phone-oco/docs + +Url +: https://open.qa/docs/ + +By +: openSUSE + +Takes +: fatal vs ignore_failure (hard vs soft), START_AFTER_TEST, screenshot needles as proof + + + +### beads + +Project +: linux-phone-oco/docs + +Url +: https://github.com/steveyegge/beads + +Author +: Steve Yegge + +Year +: 2025 + +By +: orchestration-renewed + +Takes +: blocks edges and bd ready: ready computed from open blockers + + + +### Creating issue dependencies + +Project +: linux-phone-oco/docs + +Url +: https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/creating-issue-dependencies + +By +: GitHub + +Takes +: blocked-by edges as data; no proof + + + +### Taskwarrior tags and virtual tags + +Project +: linux-phone-oco/docs + +Url +: https://taskwarrior.org/docs/tags/ + +By +: Taskwarrior + +Takes +: READY and BLOCKED computed at query time, never stored + + + +### Ubuntu Touch porting introduction + +Project +: linux-phone-oco/docs + +Url +: https://docs.ubports.com/en/latest/porting/introduction/index.html + +By +: UBports + +Takes +: porting stages without a proof per stage + + + +### Sailfish HADK: subsystems + +Project +: linux-phone-oco/docs + +Url +: https://hadk.sailfishos.org/subsystems/ + +By +: Jolla + +Takes +: concrete proof commands for phone subsystems (test_gps, list-modems) diff --git a/docs/summaries.md b/docs/summaries.md index 12339766..7127e19a 100644 --- a/docs/summaries.md +++ b/docs/summaries.md @@ -120,3 +120,18 @@ Says Condenses : 2026-11-18-device-template-follows-by-release, device-template-drift-measured, device-template-follow-world, device-template-how-it-stands + + +### Row 9 + +About +: bringup-steps + +Date +: 2026-11-18 + +Says +: Bring-up steps as data are decided, not built (decision 2026-11-18-bringup-steps-generic-in-docs-status-in-each-base, research bringup-steps-landscape). The generic steps and their hard/soft edges (with alternatives) live in docs, the commons; each device base claims its own status per step - proof, run, proven_on - by a steps contract that device-template ships and labs follow by release; docs pulls the claims into step_status as it pulls parts, and a step no base claimed is not known yet, so a new device starts all unknown. tad q bringup-chain orders the steps and says which are ready; a guidebook is rendered from the same rows; each step names its lpoco helper or the gap, and a runner later walks the ready steps. Walleye's real road is 26 steps: 17 done with checks and records, the charger failing on its tps61099 supplier. Drafts and the failing test: research/bringup-steps/2026-11-18/. Queue unranked under bringup-steps: first bringup-steps-schema, the owner's to land (bringup-steps-how-it-stands). + +Condenses +: 2026-11-18-bringup-steps-generic-in-docs-status-in-each-base, 2026-11-18-research-bringup-steps, bringup-steps-how-it-stands, bringup-steps-landscape diff --git a/research/bringup-steps/2026-11-18/README.md b/research/bringup-steps/2026-11-18/README.md new file mode 100644 index 00000000..b6b0df77 --- /dev/null +++ b/research/bringup-steps/2026-11-18/README.md @@ -0,0 +1,85 @@ +# Bring-up steps as data: material + +Research `bringup-steps-landscape` and decision `2026-11-18-bringup-steps-generic-in-docs-status-in-each-base` +(bringup-steps-research.r1). The author's question: a table, below features and components, of every small +step that makes Linux run on a machine, with how the steps need each other and the proof of each; later a +guidebook and helpers from it, and each device base recording where it stands on each step. + +## What is here + +| file | what | +|---|---| +| `schema.toml` | the three tables in tables.toml's form: `bringup_steps`, `bringup_step_edges` (docs), `step_status` (docs, filled by the feed) | +| `records/bringup-step.sql`, `records/bringup-edge.sql` | the two records (the edge record refuses a cycle) | +| `queries/bringup-chain.sql` | the chain in order (depth over all edges, then stage, then ord) with a device's status, proof, run and ready/waits | +| `seed.sh` | 26 generic steps and 37 edges, through the records: walleye's real chain generalised, surya's path checked against it | +| `claims-walleye.sh` | walleye's 26 claims as its own base will make them, each run a record of google-walleye-lab | +| `chain-walleye.md` | what the query answers with those claims: 17 done, 2 partial, 1 failing, 6 open; ready: charger, watchdog, storage, USB network, UART, stock measure | +| `bringup-chain-walleye.sh` | the failing test: fails on main (no query); passed in a scratch copy with the claims; fails again when one claim is removed (checked) | + +All of it was run in a scratch clone of docs at 3596bb3 (`tad check`: all is well, 36 tables). Nothing of it is +in docs' tables yet: that is item `bringup-steps-schema`. + +## The design in one picture + + docs (the commons) device base (google-walleye-lab, surya-lab, a new one) + bringup_steps --< bringup_step_edges steps (contract steps = 1 in devicebase.toml): + id, stage, ord, applies, done_when, step, status, proof, run, proven_on, notes, updated + proof, proof_kind, helper, component, guide claimed with tad r step, never typed in docs + | | + +---- step_status (device x step) <---- feed-device-steps.sql pulls data/steps.json + a step the base never claimed: unknown, "not known yet" + a base unreadable or without steps = 1: every step unknown, and why + + tad q bringup-chain [--device D] -> the chain in order, status, proof, run, ready/waits + make render -> docs/guidebook.md: per stage, each step's done-when, needs, proof, helper, guide, and a column per device + lpoco bringup steps -> the same chain read by the helpers; later the runner walks "ready" + +## Surya's path, against the catalogue (from surya-lab and docs' records) + +Surya came in through a distribution that already booted: U-Boot, systemd-boot and an EFI kernel, from Nura's +generic qcom-sm7150 port. Its claims will be: bootloader-unlocked done (first-fastboot-probe, getvar); +stock-facts-read, slot-state-known, control-image-boots, boot-image-packs, dtbo-accepted, +stock-kernel-runs-our-init, initramfs-gadget-emulated, reference-kernel-boots not-needed (UEFI chain, the +distribution's kernel); crash-window partial (uart8 exists, no cable); kernel-builds done (linux-phone-oco/linux +-wcd branches, 2026-11-11); kernel-reaches-init, gadget-enumerates, usb-network done (job 0004, ping +172.16.42.1); shell-on-console done by ssh (2026-11-09); dmesg-clean done (boot-warnings, no-oops, +20261116-232330); rootfs-boots done (2026-11-10-flashed-by-devlab); health-suite-runs done +(2026-11-17-1550-lpoco-health-v017); watchdog-way-back done (2026-11-17-way-back-proven); pmic-bound and +charger-online unknown (no record, no test: not known yet). Steps surya met that walleye has not yet: a test +kernel as a second EFI entry with one try (decision 2026-11-11-efi-kernel), the USB wake lock (usb-awake), the +DT boot hang removed (wcd937x-dt-aoncc) - the first two are lab steps and go in as `lab` stage rows when +surya's claims are made; the third is a case of kernel-reaches-init. + +## Looking around (22 sources read by a researcher, 2026-11-18) + +Nobody keeps bring-up steps as data with edges and a proof per step. The pieces exist apart: + +- Step order is prose: Nura's porting guide (pages chained by order, one downstream/mainline fork) and its + Mainlining Guide (minimal boot = RAM + serial, then one feature after another); Ubuntu Touch and Sailfish HADK + stages; Qualcomm's "initial support" cover letters (boot to shell with a ramdisk first; USB, Ethernet later). +- Per-device status is a person's tick: Nura's Infobox device (about 60 status_* fields, Y/P/N, stored as a + Cargo table the device lists query) and Asahi's feature-support pages (SoC blocks apart from device + integration; states say where the code lives, from linux-asahi to a mainline version). +- Proofs are flat lists: bootrr (Linaro, one assertion per driver/device with a LAVA test-case id, dropped + because kernel names are unstable ABI and every board needs its own list), Collabora's DT probe kselftest + (derives "probed" from the live devicetree), LAVA's boot stages (bootloader message, kernel-start-message, + login prompt) and `lava-test-case ID --result`, with `expected:` turning a missing case into a fail. +- Dependencies are data only where machines run them: BitBake (addtask after/before, deptask, rdeptask, + stamps keyed on input hashes, so a changed input makes a task stale), KernelCI (a job waits on another's + result), openQA (fatal vs ignore_failure, START_AFTER_TEST; needles as screenshot proof), issue trackers + (beads blocks/related and `bd ready`; GitHub blocked-by; Taskwarrior's READY and BLOCKED computed, never + stored). Yocto's BSP guide and "Yocto Project Compatible" keep a declared answer apart from a checked one. +- Nura's device categories are levels as gate sets (builds and boots; kconfig check and kernel upgrades; + hardware CI in two places) - a milestone over step proofs. + +What we take: a generic catalogue plus per-device instances (Nura's pmtest opt-in, LAVA expected, KernelCI +job x platform); typed edges, hard and soft, with alternatives; readiness computed, never stored; a proof +per step that names a stable check, never a kernel driver name; what a proof ran on, so a changed kernel can +be told; levels as sets of steps (our milestones). What we would be first at: one graph from which both the +guidebook and the device's status are made, with each cell proven. + +Sources (recorded): nura-porting-guide, nura-infobox-device, nura-device-categorization, nura-hardware-ci, +nura-mainlining-guide, asahi-feature-support, bootrr, collabora-dt-probe-kselftest, yocto-bsp-guide, +yocto-compatible, bitbake-task-deps, lava-boot-action, lava-test-definition, kernelci-pipeline-config, openqa-docs, +beads-issue-graph, github-issue-dependencies, taskwarrior-virtual-tags, ubports-porting, sailfish-hadk-subsystems. diff --git a/research/bringup-steps/2026-11-18/bringup-chain-walleye.sh b/research/bringup-steps/2026-11-18/bringup-chain-walleye.sh new file mode 100644 index 00000000..3fb17236 --- /dev/null +++ b/research/bringup-steps/2026-11-18/bringup-chain-walleye.sh @@ -0,0 +1,32 @@ +#!/bin/sh +# The failing test of decision 2026-11-18-bringup-steps-generic-in-docs-status-in-each-base: docs answers +# walleye's bring-up as data - every step in an order where each comes after what it needs, walleye's status +# pulled from its own base, and the steps it has done each with its proof and its run. Run in docs. +# Fails today: no query bringup-chain. Fails after the schema lands until google-walleye-lab claims its steps +# (contract steps = 1) and records/feed-device-steps.sql pulls them. +set -eu +out=$(tad q bringup-chain --device google-walleye --format csv) || { echo "FAIL: no query bringup-chain"; exit 1; } +n=$(printf '%s\n' "$out" | tail -n +2 | wc -l) +[ "$n" -ge 20 ] || { echo "FAIL: $n steps, expected at least 20"; exit 1; } +# every edge points backwards: what a step needs comes before it +order="${TMPDIR:-/tmp}/bringup-chain-order.csv" +printf '%s\n' "$out" | awk -F, 'NR>1{print $1","$2}' > "$order" +bad=$( + tad sql "SELECT e.step || ' before ' || e.requires FROM bringup_step_edges e + JOIN read_csv('$order', header=false, columns={'n':'INT','id':'VARCHAR'}) a ON a.id = e.step + JOIN read_csv('$order', header=false, columns={'n':'INT','id':'VARCHAR'}) b ON b.id = e.requires + WHERE a.n < b.n" --format csv | tail -n +2) +[ -z "$bad" ] || { echo "FAIL: out of order: $bad"; exit 1; } +# walleye's proven steps, each done with a proof and a run (its base's word, pulled) +for s in kernel-reaches-init gadget-enumerates banner-on-console shell-on-console dmesg-clean pmic-bound; do + row=$(printf '%s\n' "$out" | awk -F, -v s="$s" '$2==s{print $5"|"$6"|"$7}') + case "$row" in + done\|?*\|?*) : ;; + *) echo "FAIL: walleye $s is '${row:-missing}', expected done|proof|run"; exit 1 ;; + esac + case "$row" in *\|NULL\|*|*\|NULL) echo "FAIL: walleye $s has no proof or run: $row"; exit 1 ;; esac +done +# no step of walleye is left unknown: the base claims each, even as open or not-needed +unk=$(printf '%s\n' "$out" | awk -F, 'NR>1 && $5=="unknown"{print $2}' | tr '\n' ' ') +[ -z "$unk" ] || { echo "FAIL: walleye steps not known yet: $unk"; exit 1; } +echo "PASS: walleye's chain, $n steps in order, proven steps with proof and run" diff --git a/research/bringup-steps/2026-11-18/chain-walleye.md b/research/bringup-steps/2026-11-18/chain-walleye.md new file mode 100644 index 00000000..a15d9a24 --- /dev/null +++ b/research/bringup-steps/2026-11-18/chain-walleye.md @@ -0,0 +1,32 @@ +# walleye's bring-up chain, as tad q bringup-chain --device google-walleye answers it in the draft (2026-11-18) + +A trailing ~ in needs marks a soft need. ready: every hard need done; waits: one is not. + +| n | step | stage | depth | status | proof | run | updated | needs | next | +|---:|----------------------------|-----------|------:|---------|-----------------------------------|----------------------------------------|------------|--------------------------------------------------------------------------------------------------------|-------| +| 1 | stock-measured | prepare | 0 | partial | android-reference | android-reference-walleye-measured | 2026-11-18 | NULL | ready | +| 2 | stock-facts-read | prepare | 0 | done | stock-facts-recorded | walleye-stock-ids-recorded | 2026-11-18 | NULL | | +| 3 | slot-state-known | prepare | 0 | done | slot-report | walleye-load-error-first-state | 2026-11-18 | NULL | | +| 4 | initramfs-gadget-emulated | boot | 0 | done | selftest-initramfs | walleye-initramfs-usb-gadget | 2026-11-18 | NULL | | +| 5 | bootloader-unlocked | prepare | 1 | done | fastboot-unlocked | google-walleye-bootloader-first-look | 2026-11-18 | stock-measured~ | | +| 6 | boot-image-packs | boot | 1 | done | check-bootimg.sh | walleye-bootimage | 2026-11-18 | stock-facts-read | | +| 7 | crash-window | boot | 1 | partial | tests/host/pstore-t1-read.sh | walleye-pstore-t1-try | 2026-11-18 | stock-facts-read~ | ready | +| 8 | kernel-builds | kernel | 1 | done | dtb-builds-with-ids | walleye-kernel-dts | 2026-11-18 | stock-facts-read~ | | +| 9 | control-image-boots | boot | 2 | done | fastboot-boot-control | walleye-try-vendor-gadget4 | 2026-11-18 | bootloader-unlocked slot-state-known | | +| 10 | dtbo-accepted | boot | 2 | done | tests/host/dtbo-overlay-merges.sh | walleye-dtb-overlay-symbols-build | 2026-11-18 | kernel-builds | | +| 11 | uart-console | console | 2 | open | uart-log | NULL | 2026-11-18 | kernel-builds | ready | +| 12 | stock-kernel-runs-our-init | boot | 3 | done | tests/host/massstorage-read.sh | walleye-retry-massstorage-after-reboot | 2026-11-18 | boot-image-packs control-image-boots initramfs-gadget-emulated~ | | +| 13 | reference-kernel-boots | kernel | 3 | done | reference-alive | walleye-try-bisect-pk | 2026-11-18 | boot-image-packs control-image-boots | | +| 14 | kernel-reaches-init | kernel | 4 | done | kernel-alive | walleye-y-tried | 2026-11-18 | boot-image-packs control-image-boots crash-window~ dtbo-accepted kernel-builds reference-kernel-boots~ | | +| 15 | gadget-enumerates | console | 5 | done | tests/host/mainline-light-up.sh | walleye-y-tried | 2026-11-18 | initramfs-gadget-emulated kernel-reaches-init | | +| 16 | banner-on-console | console | 6 | done | tests/host/banner-check.sh | walleye-banner2-tried | 2026-11-18 | gadget-enumerates uart-console | | +| 17 | usb-network | userspace | 6 | open | gadget-up | NULL | 2026-11-18 | gadget-enumerates | ready | +| 18 | shell-on-console | console | 7 | done | tests/host/mainline-shell-read.sh | walleye-z6-tried | 2026-11-18 | banner-on-console | | +| 19 | first-dmesg-mapped | kernel | 8 | done | dmesg-map | walleye-z6-dmesg-mapped | 2026-11-18 | shell-on-console | | +| 20 | dmesg-clean | kernel | 9 | done | tests/host/dmesg-clean-check.sh | walleye-z7-tried | 2026-11-18 | first-dmesg-mapped | | +| 21 | pmic-bound | power | 9 | done | tests/host/pmic-dmesg-check.sh | walleye-z7-tried | 2026-11-18 | first-dmesg-mapped~ shell-on-console | | +| 22 | charger-online | power | 10 | failing | tests/host/charger-check.sh | walleye-c2-tried | 2026-11-18 | pmic-bound | ready | +| 23 | watchdog-way-back | power | 10 | open | way-back | NULL | 2026-11-18 | kernel-reaches-init pmic-bound~ | ready | +| 24 | storage-readonly | storage | 10 | open | storage-lists | NULL | 2026-11-18 | dmesg-clean~ shell-on-console | ready | +| 25 | rootfs-boots | userspace | 11 | open | rootfs-ssh | NULL | 2026-11-18 | storage-readonly usb-network | waits | +| 26 | health-suite-runs | userspace | 12 | open | suite-filed | NULL | 2026-11-18 | rootfs-boots | waits | diff --git a/research/bringup-steps/2026-11-18/claims-walleye.sh b/research/bringup-steps/2026-11-18/claims-walleye.sh new file mode 100644 index 00000000..1c54089b --- /dev/null +++ b/research/bringup-steps/2026-11-18/claims-walleye.sh @@ -0,0 +1,28 @@ +#!/bin/sh +# walleye's claims as its own base will make them (item walleye-steps-claimed: tad r step in google-walleye-lab). +# Tried in a scratch copy of docs through a stand-in record (step-claim) that wrote step_status directly, as the +# feed will: with it bringup-chain-walleye.sh passes. Every run named is a record id in google-walleye-lab. +set -eu +k() { tad r step-claim --device google-walleye --updated 2026-11-18 "$@" >/dev/null; } +k --step bootloader-unlocked --status done --proof fastboot-unlocked --run google-walleye-bootloader-first-look +k --step stock-measured --status partial --proof android-reference --run android-reference-walleye-measured +k --step stock-facts-read --status done --proof stock-facts-recorded --run walleye-stock-ids-recorded +k --step slot-state-known --status done --proof slot-report --run walleye-load-error-first-state +k --step control-image-boots --status done --proof fastboot-boot-control --run walleye-try-vendor-gadget4 +k --step boot-image-packs --status done --proof check-bootimg.sh --run walleye-bootimage +k --step dtbo-accepted --status done --proof tests/host/dtbo-overlay-merges.sh --run walleye-dtb-overlay-symbols-build +k --step initramfs-gadget-emulated --status done --proof selftest-initramfs --run walleye-initramfs-usb-gadget +k --step stock-kernel-runs-our-init --status done --proof tests/host/massstorage-read.sh --run walleye-retry-massstorage-after-reboot +k --step crash-window --status partial --proof tests/host/pstore-t1-read.sh --run walleye-pstore-t1-try +k --step kernel-builds --status done --proof dtb-builds-with-ids --run walleye-kernel-dts +k --step reference-kernel-boots --status done --proof reference-alive --run walleye-try-bisect-pk +k --step kernel-reaches-init --status done --proof kernel-alive --run walleye-y-tried +k --step uart-console --status open --notes "waits the cable: walleye-get-uart-setup" +k --step gadget-enumerates --status done --proof tests/host/mainline-light-up.sh --run walleye-y-tried +k --step banner-on-console --status done --proof tests/host/banner-check.sh --run walleye-banner2-tried +k --step shell-on-console --status done --proof tests/host/mainline-shell-read.sh --run walleye-z6-tried +k --step first-dmesg-mapped --status done --proof dmesg-map --run walleye-z6-dmesg-mapped +k --step dmesg-clean --status done --proof tests/host/dmesg-clean-check.sh --run walleye-z7-tried +k --step pmic-bound --status done --proof tests/host/pmic-dmesg-check.sh --run walleye-z7-tried +k --step charger-online --status failing --proof tests/host/charger-check.sh --run walleye-c2-tried +for s in watchdog-way-back storage-readonly usb-network rootfs-boots health-suite-runs; do k --step $s --status open; done diff --git a/research/bringup-steps/2026-11-18/queries/bringup-chain.sql b/research/bringup-steps/2026-11-18/queries/bringup-chain.sql new file mode 100644 index 00000000..f0a08dc9 --- /dev/null +++ b/research/bringup-steps/2026-11-18/queries/bringup-chain.sql @@ -0,0 +1,29 @@ +-- A device's bring-up, step by step in the order the steps need each other: each step's depth (the longest +-- chain of needs under it, soft ones too: they order the guide), its stage, its status on the device with the proof and the run, what it +-- needs, and whether it is ready (every hard need done, or one of each group). Without --device: the generic +-- chain, every status unknown - the guidebook's order. A step the device's base never claimed is unknown. +-- --device string? the device (devices id); omitted: the generic chain +WITH RECURSIVE depth(id, d) AS ( + SELECT id, 0 FROM bringup_steps WHERE id NOT IN (SELECT step FROM bringup_step_edges) + UNION ALL + SELECT e.step, depth.d + 1 FROM bringup_step_edges e JOIN depth ON e.requires = depth.id +), +lvl AS (SELECT id, max(d) AS depth FROM depth GROUP BY id), +st AS ( + SELECT s.id, coalesce(ss.status, 'unknown') AS status, ss.proof, ss.run, ss.proven_on, ss.updated + FROM bringup_steps s LEFT JOIN step_status ss ON ss.step_id = s.id AND ss.device_id = $device +), +need AS ( + SELECT e.step, e.requires, e.kind, coalesce(e."group", e.requires) AS g, st.status = 'done' OR st.status = 'not-needed' AS met + FROM bringup_step_edges e JOIN st ON st.id = e.requires +), +ready AS ( + SELECT step, bool_and(gmet) AS ok FROM (SELECT step, g, bool_or(met) AS gmet FROM need WHERE kind = 'hard' GROUP BY step, g) GROUP BY step +) +SELECT row_number() OVER (ORDER BY l.depth, array_position(['prepare','boot','console','kernel','power','storage','userspace','lab'], s.stage), s.ord, s.id) AS n, + s.id AS step, s.stage, l.depth, st.status, + coalesce(st.proof, s.proof) AS proof, st.run, st.updated, + (SELECT string_agg(requires || CASE WHEN kind = 'soft' THEN '~' ELSE '' END, ' ' ORDER BY requires) FROM need WHERE need.step = s.id) AS needs, + CASE WHEN st.status IN ('done', 'not-needed') THEN '' WHEN coalesce(r.ok, true) THEN 'ready' ELSE 'waits' END AS next +FROM bringup_steps s JOIN lvl l ON l.id = s.id JOIN st ON st.id = s.id LEFT JOIN ready r ON r.step = s.id +ORDER BY n; diff --git a/research/bringup-steps/2026-11-18/records/bringup-edge.sql b/research/bringup-steps/2026-11-18/records/bringup-edge.sql new file mode 100644 index 00000000..3ab51324 --- /dev/null +++ b/research/bringup-steps/2026-11-18/records/bringup-edge.sql @@ -0,0 +1,13 @@ +-- What a step needs before it (an edge of that pair is replaced). hard: it cannot be done first; soft: it can, +-- but blind or at much greater cost. Edges of one step sharing a group are alternatives: one done is enough. +-- --step string the step +-- --requires string the step it needs +-- --kind string hard or soft +-- --group string? the alternatives it is one of (console: UART or the USB gadget) +-- --why string why, in a line - the record that showed it, when one did +SELECT CASE WHEN $step = $requires THEN error('a step cannot require itself') END; +SELECT CASE WHEN EXISTS ( + WITH RECURSIVE up(id) AS (SELECT $requires UNION SELECT e.requires FROM bringup_step_edges e JOIN up ON e.step = up.id) + SELECT 1 FROM up WHERE id = $step) THEN error('this edge makes a cycle: ' || $requires || ' already needs ' || $step) END; +DELETE FROM bringup_step_edges WHERE step = $step AND requires = $requires; +INSERT INTO bringup_step_edges (step, requires, kind, "group", why) VALUES ($step, $requires, $kind, $group, $why); diff --git a/research/bringup-steps/2026-11-18/records/bringup-step.sql b/research/bringup-steps/2026-11-18/records/bringup-step.sql new file mode 100644 index 00000000..119dfb19 --- /dev/null +++ b/research/bringup-steps/2026-11-18/records/bringup-step.sql @@ -0,0 +1,21 @@ +-- A step of bringing Linux up on a machine, for every machine it applies to (a step of that id is replaced). +-- Generic: what the step is, when it is done and how that is proven - never one device's state, which its own +-- base claims (its steps table) and docs pulls into step_status. What it needs goes in bringup-edge. +-- --id string a-short-name: kernel-reaches-init, shell-on-console ... +-- --title string what it is, in a few words +-- --stage string prepare, boot, console, kernel, power, storage, userspace or lab +-- --ord integer its place in the stage, where the edges leave two steps unordered +-- --applies string = any any, or the class it holds for: boot:android, boot:uefi, usb:gadget, soc:qcom ... +-- --done-when string what done means, checkably +-- --proof string the test that proves it (a tests id, or the check a device's test must make) +-- --proof-kind string host-check, phone-suite, build-check, witness or research +-- --helper string? the lpoco command that does it; none yet is the gap a helper fills +-- --component string? the part of the catalogue whose first light it is +-- --guide string how it is done, and the traps met so far with the records that met them +-- --sources string? ids of the sources, comma-separated +-- --checked-on date = today when its text was last checked +SELECT CASE WHEN $sources IS NOT NULL AND EXISTS (SELECT 1 FROM unnest(string_split($sources, ',')) AS t(x) WHERE trim(t.x) NOT IN (SELECT id FROM sources)) + THEN error('sources names no source of this base: ' || (SELECT string_agg(trim(t.x), ', ') FROM unnest(string_split($sources, ',')) AS t(x) WHERE trim(t.x) NOT IN (SELECT id FROM sources)) || ' (tad r source records one)') END; +DELETE FROM bringup_steps WHERE id = $id; +INSERT INTO bringup_steps (id, title, stage, ord, applies, done_when, proof, proof_kind, helper, component, guide, sources, checked_on) +VALUES ($id, $title, $stage, $ord, $applies, $done_when, $proof, $proof_kind, $helper, $component, $guide, $sources, $checked_on); diff --git a/research/bringup-steps/2026-11-18/schema.toml b/research/bringup-steps/2026-11-18/schema.toml new file mode 100644 index 00000000..161d2973 --- /dev/null +++ b/research/bringup-steps/2026-11-18/schema.toml @@ -0,0 +1,183 @@ + +# Bring-up steps (decision 2026-11-18-bringup-steps-generic-in-docs-status-in-each-base): every small step that +# makes Linux run on a machine, once for all machines, in the commons. A device never writes here: its own base +# claims each step (the steps table, contract steps = 1 in devicebase.toml) and docs pulls the claims into +# step_status, as it pulls parts into support_status. A step a base never claimed is not known yet. +[tables.bringup_steps] +key = ["id"] + +[[tables.bringup_steps.fields]] +name = "id" +type = "string" +required = true +pattern = "^[a-z0-9]+(-[a-z0-9]+)*$" + +# what the step is, in a few words +[[tables.bringup_steps.fields]] +name = "title" +type = "string" +required = true + +# the phase it belongs to, in the order a bring-up meets them: the guidebook's chapters +[[tables.bringup_steps.fields]] +name = "stage" +type = "string" +required = true +enum = ["prepare", "boot", "console", "kernel", "power", "storage", "userspace", "lab"] + +# its place within the stage when the edges leave two steps unordered (the guidebook's tie-break) +[[tables.bringup_steps.fields]] +name = "ord" +type = "integer" +required = true +minimum = 1.0 + +# which machines it holds for: any, or a class - boot:android (an Android bootloader), boot:uefi, usb:gadget, +# soc:qcom, power:battery ... A device whose class does not match records not-needed, with why. +[[tables.bringup_steps.fields]] +name = "applies" +type = "string" +required = true +pattern = "^(any|[a-z]+:[a-z0-9-]+)$" + +# what done means, checkably: the sentence the proof tests +[[tables.bringup_steps.fields]] +name = "done_when" +type = "string" +required = true + +# the generic proof: a tests id, or the check a device's own test must make (named, to write) +[[tables.bringup_steps.fields]] +name = "proof" +type = "string" +required = true + +# how the proof is had: a host-side check on what the phone printed, the phone's own suite, a build check, +# a person's witness, or a research row (a reading that is not a test) +[[tables.bringup_steps.fields]] +name = "proof_kind" +type = "string" +required = true +enum = ["host-check", "phone-suite", "build-check", "witness", "research"] + +# the lpoco command that does the step or most of it; none yet = the gap a helper fills +[[tables.bringup_steps.fields]] +name = "helper" +type = "string" + +# the part of docs' catalogue whose first light this step is, when it is one +[[tables.bringup_steps.fields]] +name = "component" +type = "string" + +# the guidebook's paragraph: how it is done, and the traps met so far with the records that met them +[[tables.bringup_steps.fields]] +name = "guide" +type = "string" +required = true + +# the sources, comma-separated ids +[[tables.bringup_steps.fields]] +name = "sources" +type = "string" + +[[tables.bringup_steps.fields]] +name = "checked_on" +type = "date" +required = true + +# What a step needs before it. hard: it cannot be done before the other is done; soft: it can, but blind or +# at much greater cost (a crash window before the first kernel). Edges sharing a group are alternatives: one +# done is enough (a console over UART or over the USB gadget). +[tables.bringup_step_edges] +key = ["step", "requires"] + +[[tables.bringup_step_edges.fields]] +name = "step" +type = "string" +required = true + +[[tables.bringup_step_edges.fields]] +name = "requires" +type = "string" +required = true + +[[tables.bringup_step_edges.fields]] +name = "kind" +type = "string" +required = true +enum = ["hard", "soft"] + +[[tables.bringup_step_edges.fields]] +name = "group" +type = "string" + +[[tables.bringup_step_edges.fields]] +name = "why" +type = "string" +required = true + +# Each device's steps as its own base claims them: filled by records/feed-device-steps.sql, never typed here. +# Every step x every registered device has a row; what the base does not claim is unknown, "not known yet". +[tables.step_status] +key = ["device_id", "step_id"] + +[[tables.step_status.fields]] +name = "device_id" +type = "string" +required = true + +[[tables.step_status.fields]] +name = "step_id" +type = "string" +required = true + +[[tables.step_status.fields]] +name = "status" +type = "string" +required = true +enum = ["done", "partial", "failing", "open", "not-needed", "unknown"] + +# the test or check that proved it on this device (a tests id, or the base's own script) +[[tables.step_status.fields]] +name = "proof" +type = "string" + +# where the proof ran: a test_runs id, a research row, a pull request +[[tables.step_status.fields]] +name = "run" +type = "string" + +# what it was proven on: the image, kernel or dtb (its hash), so a later change can be told from it +[[tables.step_status.fields]] +name = "proven_on" +type = "string" + +[[tables.step_status.fields]] +name = "notes" +type = "string" + +[[tables.step_status.fields]] +name = "updated" +type = "date" +required = true + +[[rules.references]] +field = "bringup_step_edges.step" +to = ["bringup_steps"] + +[[rules.references]] +field = "bringup_step_edges.requires" +to = ["bringup_steps"] + +[[rules.references]] +field = "bringup_steps.component" +to = ["components"] + +[[rules.references]] +field = "step_status.device_id" +to = ["devices"] + +[[rules.references]] +field = "step_status.step_id" +to = ["bringup_steps"] diff --git a/research/bringup-steps/2026-11-18/seed.sh b/research/bringup-steps/2026-11-18/seed.sh new file mode 100755 index 00000000..e5ec2c24 --- /dev/null +++ b/research/bringup-steps/2026-11-18/seed.sh @@ -0,0 +1,151 @@ +#!/bin/sh +# Seeds the generic bring-up steps and their edges through the records (decision +# 2026-11-18-bringup-steps-generic-in-docs-status-in-each-base). Run in docs once records/bringup-step.sql and +# records/bringup-edge.sql exist. The steps are walleye's real chain generalised; surya's path checked them. +set -eu +st() { tad r bringup-step --checked-on 2026-11-18 "$@" >/dev/null; } +ed() { tad r bringup-edge "$@" >/dev/null; } + +st --id bootloader-unlocked --title "Bootloader unlocked" --stage prepare --ord 1 --applies boot:android \ + --done-when "fastboot getvar all says unlocked: yes" --proof fastboot-unlocked --proof-kind host-check \ + --helper "lpoco lab fastboot getvar" \ + --guide "Unlocking wipes the user's data and is the owner's act. Read the state before anything else (walleye google-walleye-bootloader-first-look, surya first-fastboot-probe)." +st --id stock-measured --title "The stock system measured" --stage prepare --ord 2 --applies any \ + --done-when "what works on the stock system, its battery and its partitions are recorded as the reference" \ + --proof android-reference --proof-kind research \ + --guide "Measure the stock system before anything is flashed: it is the reference 'as good as Android' is judged by, and an unlock may wipe it (walleye android-reference-walleye-measured)." +st --id stock-facts-read --title "The stock boot's facts read" --stage prepare --ord 3 --applies any \ + --done-when "the stock cmdline, boot header and offsets, dtb ids (msm-id, board-id), running fdt and ramoops region are recorded" \ + --proof stock-facts-recorded --proof-kind research --helper "lpoco bringup image info" \ + --guide "Read them from the running stock system and its boot image (walleye walleye-stock-ids-recorded, walleye-boot-cmdline-known). The running fdt is worth keeping whole: on walleye it named the cause of the dead dtbs (walleye-our-dts-gpio-reserved)." +st --id slot-state-known --title "Slots read, a way back known" --stage prepare --ord 4 --applies boot:android-ab \ + --done-when "both slots' flags are reported before and after every try, and the phone returns to the stock system by itself" \ + --proof slot-report --proof-kind host-check --helper "lpoco lab fastboot state" \ + --guide "On walleye the Load Error was the slot state left by refusals, not the image: restore the first state (Android booted to completion on a good slot) before each try (walleye-load-error-first-state)." +st --id control-image-boots --title "A known-good image boots from memory" --stage boot --ord 1 --applies boot:android \ + --done-when "fastboot boot of a known-good stock-format image leaves fastboot and runs, nothing written" \ + --proof fastboot-boot-control --proof-kind host-check --helper "lpoco lab fastboot boot" \ + --guide "The control tells 'the bootloader refuses' from 'our image is wrong' (walleye walleye-loaderror-control)." +st --id boot-image-packs --title "Our boot image packs as the device wants" --stage boot --ord 2 --applies boot:android \ + --done-when "header version, offsets, page size, dtb placement and os word match the control where they should" \ + --proof bringup-pack-matches-mkbootimg --proof-kind build-check --helper "lpoco bringup image pack, check" \ + --guide "Pack from the device's [boot] declaration and count it against the control (walleye walleye-bootimage). The helper packs header v0 only." +st --id dtbo-accepted --title "The bootloader's dtbo overlay accepted" --stage boot --ord 3 --applies boot:android-dtbo \ + --done-when "our dtb, built with -@ and the overlay's labels, merges with the stock dtbo, or the bootloader does not need it" \ + --proof dtbo-overlay-merges --proof-kind build-check \ + --guide "On walleye our dtb with -@ and the 137 labels merged; the dtbo stub that was planned was never needed (walleye-dtb-overlay-symbols-build, walleye-loaderror-dtbo-stub)." +st --id initramfs-gadget-emulated --title "Our initramfs brings the gadget up, emulated" --stage boot --ord 4 --applies usb:gadget \ + --done-when "in QEMU with dummy_hcd our initramfs makes the gadget (ACM console and a window) and the host side sees it" \ + --proof selftest-initramfs --proof-kind build-check --helper "lpoco bringup initramfs build" \ + --guide "Prove the init before any phone time (walleye walleye-initramfs-usb-gadget). The generic init under lpoco is backlog bringup-generic-init." +st --id stock-kernel-runs-our-init --title "The stock kernel runs our init" --stage boot --ord 5 --applies boot:android \ + --done-when "the stock kernel with only our ramdisk swapped runs our /init, and it shows (a gadget, a mass-storage window)" \ + --proof massstorage-window-read --proof-kind host-check --helper "lpoco bringup image swap" \ + --guide "Proves the image path apart from our kernel. On walleye the NCM function panics the vendor 4.4 kernel; a mass-storage window works (walleye-ncm-split, walleye-massstorage-window)." +st --id crash-window --title "A window on a dead boot" --stage boot --ord 6 --applies any \ + --done-when "a dead or hung boot leaves something the host reads: UART, pstore at the phone's own ramoops region, or a timing channel" \ + --proof crash-window-read --proof-kind host-check \ + --guide "On walleye ramoops survives only at the region the stock fdt names and only across a warm reset (walleye-pstore-warm-reset, walleye-pstore-t1-try); a timing channel told alive from dead (walleye-ml4-timing-channel); UART waits a cable (walleye-get-uart-setup)." +st --id kernel-builds --title "Our kernel and dts build" --stage kernel --ord 1 --applies any \ + --done-when "the mainline kernel and the device's dts build with no dtc warning from our file, and the dtb carries the ids the bootloader matches" \ + --proof dtb-builds-with-ids --proof-kind build-check \ + --guide "Start from the nearest sibling's dts in mainline (walleye from taimen, walleye-kernel-dts)." +st --id reference-kernel-boots --title "Someone else's mainline kernel boots here" --stage kernel --ord 2 --applies any \ + --done-when "another project's mainline kernel and dtb for this device or a sibling reach their init on this phone" \ + --proof reference-alive --proof-kind host-check --helper "lpoco bringup image bisect" \ + --guide "The reference to bisect against when ours is dead: swap one part at a time (walleye pk5 alive against ours dead: walleye-bisect-porthole-vs-ours, walleye-our-dtb-bisect, walleye-property-bisect)." +st --id kernel-reaches-init --title "Our kernel reaches our init" --stage kernel --ord 3 --applies any \ + --done-when "our kernel and our dtb reach /init: the phone stays up as long as /init says, with no early reset" \ + --proof kernel-alive --proof-kind host-check --helper "lpoco bringup image bisect" \ + --guide "Two traps on walleye: earlycon on an undeclared UART kills the kernel (walleye-no-earlycon); a pinctrl node without gpio-reserved-ranges touches the secure world's pins and resets the phone (walleye-our-dts-gpio-reserved)." +st --id uart-console --title "Kernel log on UART" --stage console --ord 1 --applies any \ + --done-when "the kernel's log reaches the host over the debug UART" \ + --proof uart-log --proof-kind host-check \ + --guide "Needs the device's debug cable or pads; on walleye it waits the cable (walleye-get-uart-setup), so the USB gadget was the console." +st --id gadget-enumerates --title "The host sees our gadget" --stage console --ord 2 --applies usb:gadget \ + --done-when "the host enumerates our own kernel's gadget by its vendor:product and serial" \ + --proof gadget-enumerates --proof-kind host-check \ + --guide "walleye y2: 1d6b:0104 18 s after the jump (walleye-try-y)." +st --id banner-on-console --title "The banner on the console" --stage console --ord 3 --applies any \ + --done-when "/init's banner with a heartbeat reaches the host on the console, read as the lab user" \ + --proof banner-seen --proof-kind host-check \ + --guide "The gadget serial must be the one the host's udev rule names, or the tty is root's (walleye-banner-serial-fix, walleye-try-banner2)." +st --id shell-on-console --title "A shell answers on the console" --stage console --ord 4 --applies any \ + --done-when "commands sent on the console answer, one at a time, reliably across hangups" \ + --proof shell-answers --proof-kind host-check \ + --guide "On walleye an interactive ash stayed silent; a plain read/exec loop and the host tty raw and -hupcl made it answer (walleye-shell-reliable, walleye-command-loop, walleye-try-z6)." +st --id first-dmesg-mapped --title "The first dmesg mapped" --stage kernel --ord 4 --applies any \ + --done-when "the first full dmesg of our kernel is read and every line placed: works, defers, fails, and whose" \ + --proof dmesg-map --proof-kind research \ + --guide "The map orders what follows (walleye-z6-dmesg-map, research walleye-bringup-order-plan)." +st --id dmesg-clean --title "dmesg clean" --stage kernel --ord 5 --applies any \ + --done-when "no WARN, oops or -110, and no probe deferred but the known ones" \ + --proof dmesg-clean --proof-kind host-check \ + --guide "walleye z7: the GPU smmu off cleared the gpu_gx WARNs (walleye-dmesg-clean); on a rootfs the suite's no-oops and boot-warnings carry it." +st --id pmic-bound --title "The PMIC bound" --stage power --ord 1 --applies any \ + --done-when "the PMIC's children bind on their bus, the RTC and the power-on reason read" \ + --proof pmic-bound --proof-kind host-check \ + --guide "walleye: pm8998 and pmi8998 on SPMI (walleye-pmic-spmi, proven in z7). UFS rails are RPM regulators and do not wait for it (walleye-bringup-order-plan)." +st --id charger-online --title "The charger online" --stage power --ord 2 --applies power:battery \ + --done-when "a power_supply of type USB appears, online follows the cable, and the voltage rises while connected" \ + --proof charger-online --proof-kind host-check \ + --guide "Until it works, tries are rationed by the battery. walleye c2: the charger defers on its tps61099 supplier (walleye-charger-wait-tps61099, walleye-charger-supplier)." +st --id watchdog-way-back --title "A hung kernel comes back by itself" --stage power --ord 3 --applies any \ + --done-when "a hung kernel resets by itself and the phone returns to a known system without hands" \ + --proof way-back --proof-kind host-check \ + --guide "surya: qcom_wdt kept armed through sleep (way-back.sh). walleye: the PMIC watchdog (walleye-pmic-wdt-proof)." +st --id storage-readonly --title "Internal storage read-only" --stage storage --ord 1 --applies any \ + --done-when "the internal storage lists its partitions by name, nothing written" \ + --proof storage-lists --proof-kind host-check \ + --guide "Gives the firmware partitions every later part needs (walleye-ufs-readonly)." +st --id usb-network --title "Network over USB" --stage userspace --ord 1 --applies usb:gadget \ + --done-when "ssh over the USB gadget's network answers" \ + --proof gadget-up --proof-kind host-check \ + --guide "walleye: walleye-usb-net. surya had the distribution's own gadget." +st --id rootfs-boots --title "A distribution root boots" --stage userspace --ord 2 --applies any \ + --done-when "a distribution's root filesystem boots to its init and ssh answers" \ + --proof rootfs-ssh --proof-kind host-check --helper "lpoco lab flash, provision" \ + --guide "surya boots Nura through U-Boot, systemd-boot and an EFI kernel (first-fastboot-probe)." +st --id health-suite-runs --title "The health suite runs after every boot" --stage userspace --ord 3 --applies any \ + --done-when "the phone's own suite runs after every boot and its run is filed in the device's base" \ + --proof suite-filed --proof-kind phone-suite --helper "lpoco lab suite put, run" \ + --guide "From here a part's status is measured, not judged (surya 2026-11-17-health-on-the-phone)." + +ed --step bootloader-unlocked --requires stock-measured --kind soft --why "an unlock may wipe the stock system" +ed --step control-image-boots --requires bootloader-unlocked --kind hard --why "fastboot boot needs an unlocked bootloader" +ed --step control-image-boots --requires slot-state-known --kind hard --why "walleye: refusals were the slot state (walleye-load-error-first-state)" +ed --step boot-image-packs --requires stock-facts-read --kind hard --why "the header and offsets are the stock image's" +ed --step kernel-builds --requires stock-facts-read --kind soft --why "the dtb ids the bootloader matches" +ed --step dtbo-accepted --requires kernel-builds --kind hard --why "it is our dtb that must merge" +ed --step stock-kernel-runs-our-init --requires control-image-boots --kind hard --why "the control is the image swapped into" +ed --step stock-kernel-runs-our-init --requires boot-image-packs --kind hard --why "the swap repacks" +ed --step stock-kernel-runs-our-init --requires initramfs-gadget-emulated --kind soft --why "an init proven emulated spends no phone time" +ed --step crash-window --requires stock-facts-read --kind soft --why "the ramoops region is the stock fdt's" +ed --step reference-kernel-boots --requires control-image-boots --kind hard --why "same bootloader path" +ed --step reference-kernel-boots --requires boot-image-packs --kind hard --why "packed the device's way" +ed --step kernel-reaches-init --requires kernel-builds --kind hard --why "it is our kernel" +ed --step kernel-reaches-init --requires boot-image-packs --kind hard --why "packed the device's way" +ed --step kernel-reaches-init --requires control-image-boots --kind hard --why "the bootloader accepts images" +ed --step kernel-reaches-init --requires dtbo-accepted --kind hard --why "walleye: no start without the merge (walleye-dtbo-overlay-merge-why)" +ed --step kernel-reaches-init --requires crash-window --kind soft --why "without one a dead kernel says nothing" +ed --step kernel-reaches-init --requires reference-kernel-boots --kind soft --why "the bisect reference" +ed --step uart-console --requires kernel-builds --kind hard --why "it is our kernel's log" +ed --step gadget-enumerates --requires kernel-reaches-init --kind hard --why "our kernel's gadget" +ed --step gadget-enumerates --requires initramfs-gadget-emulated --kind hard --why "the init makes the gadget" +ed --step banner-on-console --requires gadget-enumerates --kind hard --group console --why "the console over the gadget" +ed --step banner-on-console --requires uart-console --kind hard --group console --why "or over UART" +ed --step shell-on-console --requires banner-on-console --kind hard --why "a console that carries text first" +ed --step first-dmesg-mapped --requires shell-on-console --kind hard --why "dmesg is read through the shell" +ed --step dmesg-clean --requires first-dmesg-mapped --kind hard --why "the map names what to clean" +ed --step pmic-bound --requires shell-on-console --kind hard --why "read through the shell" +ed --step pmic-bound --requires first-dmesg-mapped --kind soft --why "the map names the PMIC's faults" +ed --step charger-online --requires pmic-bound --kind hard --why "the charger is a PMIC child" +ed --step watchdog-way-back --requires kernel-reaches-init --kind hard --why "it is our kernel that hangs" +ed --step watchdog-way-back --requires pmic-bound --kind soft --why "walleye's way is the PMIC watchdog" +ed --step storage-readonly --requires shell-on-console --kind hard --why "read through the shell" +ed --step storage-readonly --requires dmesg-clean --kind soft --why "smmu and supplier faults stop DMA devices" +ed --step usb-network --requires gadget-enumerates --kind hard --why "the network rides the gadget" +ed --step rootfs-boots --requires storage-readonly --kind hard --why "the root is on the storage" +ed --step rootfs-boots --requires usb-network --kind hard --why "ssh is the proof" +ed --step health-suite-runs --requires rootfs-boots --kind hard --why "the suite runs on the root" +echo "seeded: $(tad sql 'SELECT count(*) FROM bringup_steps' --format csv | tail -1) steps, $(tad sql 'SELECT count(*) FROM bringup_step_edges' --format csv | tail -1) edges"