Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OS support #99

Merged
merged 5 commits into from
Aug 24, 2022
Merged

OS support #99

merged 5 commits into from
Aug 24, 2022

Conversation

JonathonHall-Purism
Copy link
Collaborator

Includes changes related to linuxboot/heads#1188 as well as general OS recommendations discussed during that PR.

I included the qemu-coreboot-fbwhiptail-tpm1-hotp setup instructions, so maybe README.md in Heads should link here instead? On the other hand since these instructions may change, maybe it is better that they are versioned with Heads?

Signed-off-by: Jonathon Hall <jonathon.hall@puri.sm>
Add OS recommendations and compatibility notes.  Live desktop images
are recommended.  Debian netinst now works in qemu, but it does not
work for me on Librem 14 or L1UM (installer is unable to initialize
the display after kexec).

Minor fixes to formatting.

Signed-off-by: Jonathon Hall <jonathon.hall@puri.sm>
@JonathonHall-Purism
Copy link
Collaborator Author

Development/Emulating-Heads.md Outdated Show resolved Hide resolved
Nitrokey3NFC isn't documented as OTP support is still in development.

Signed-off-by: Jonathon Hall <jonathon.hall@puri.sm>
@tlaurion
Copy link
Collaborator

@JonathonHall-Purism your questions in OP here are important for maintainership.

I tend to document board specific instructions in board configurations, but that might be impractical for users, while developers will understand.

Documenting into board config would ease maintainership, since changing a board config and its make statements and operations guidelines would directly reflect a specific commit.

I think you are completely right, and the current qemu relative documentation might be wiser to point directly into the board configuration, and have heads repo README and emulation guidelines point to the board configuration directly?

Otherwise by experience, we will change the boards and will forget to update the docs.

Unfortunately heads-wiki is separated from heads repo and this disjunction creates discreoencies and duplicate of efforts.

I wish we could merge the two and have heads rendered over osresearch.net only for the documentation section butnthisnis not how this is setuped right now.

@osresearch?

Move documentation to board directory in heads repo.

Signed-off-by: Jonathon Hall <jonathon.hall@puri.sm>
Signed-off-by: Jonathon Hall <jonathon.hall@puri.sm>
@tlaurion tlaurion merged commit a058e2d into linuxboot:master Aug 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants