0e61017da8
The HWID is populated on the device tree by the boot loader.
This can be used as a key modifier when encrypting the U-Boot
environment. Some old U-Boot versions however, did not populate
the HWID on the device tree. When updating firmware from an
old version to a new one, the library may not be able to read
the HWID from the DT and then be unable to unencrypt the
environment.
This patch implements a fall-back function to read the HWID
directly from the nvmem node (sysfs). Implementation has been
done for ccimx6 family only, where this case of old U-Boot
can happen.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://onedigi.atlassian.net/browse/DEL-8444
(cherry picked from commit
|
||
|---|---|---|
| .. | ||
| alsa-state | ||
| ath-prop-tools | ||
| digi-sc-firmware | ||
| firmware-atheros | ||
| firmware-murata | ||
| firmware-qualcomm | ||
| formfactor | ||
| libedgetpu | ||
| libubootenv | ||
| tensorflow-lite | ||
| trustfence-cst | ||
| u-boot | ||
| usbutils | ||