-
Notifications
You must be signed in to change notification settings - Fork 77
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 service to acquire hw information for swupdate #434
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: Felix Moessbauer <[email protected]>
This patch adds a one-shot systemd service that reads the hardware revision part from /proc/device-tree/compatible and writes that to /etc/hwrevision. By that, the hardware-compatibility node in the swupdate description file can be used to limit the boards an update can be applied to. This helps to avoid that images are applied to unsupported boards (e.g. due to lack of RAM, no M2, etc...). Signed-off-by: Felix Moessbauer <[email protected]>
8f05508
to
ae38b90
Compare
But this service is neither used nor otherwise described in meta-iot2050 right now, correct? I'd like to see a demo use case here as well so that user get an idea what it can be good for. |
The service is integrated into the swupdate image, so it is used. However, the data that is written to
That's why I would like to only integrate this service, but not enforce compatibility by now. |
That leaves us with documenting this option at minimum. |
Tell me where and I'll add it. |
Also Hardware compatibility check is currently disabled when using SWUpdate 2021.11 from isar-cip-core. See https://gitlab.com/cip-project/cip-core/isar-cip-core/-/blob/master/recipes-core/swupdate/swupdate_2021.11-1%2Bdebian-gbp.bb#L32 |
What's the status? |
This patch adds a one-shot systemd service that reads the hardware revision part from /proc/device-tree/compatible and writes that to /etc/hwrevision. By that, the hardware-compatibility node in the swupdate description file can be used to limit the boards an update can be applied to. This helps to avoid that images are applied to unsupported boards (e.g. due to lack of RAM, no M2, etc...).