-
Notifications
You must be signed in to change notification settings - Fork 330
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
Add support for embedding devicetree into UKI #2440
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -1872,6 +1872,11 @@ def build_uki( | |
"--ro-bind", stub, stub, | ||
] | ||
|
||
if context.config.devicetree: | ||
dtb = context.root / f"usr/lib/linux-image-{kver}" / context.config.devicetree | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This seems like a completely arbitrary location to me for putting device trees. Is there any kind of spec mandating that this is where device trees should be installed? If not, we need such a spec first. See for example uapi-group/specifications#91 where a standard location for UKI addons is proposed. We'd need such a proposal for device trees as well. Until then, I'd prefer if you used a ukify config file in a package manager tree to accomplish this. |
||
cmd += ["--devicetree", dtb] | ||
options += ["--ro-bind", dtb, dtb] | ||
|
||
if context.config.secure_boot: | ||
assert context.config.secure_boot_key | ||
assert context.config.secure_boot_certificate | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There should probably be some checking here for the case that the file does not exist in the image.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The "other" options like e.g. initrds also do not check the existence of the files.
If a non existing dtb will be configured the current output looks like this:
Shall we fail with a nicer looking message?