Open Source Software TODO list

• ss: test if the output file in the form /dev/sdXY is a block device before writing it: https://github.com/manoj23/ee
• u-boot: generate a u-boot.itb image instead of overwriting u-boot.img
• meta-swupdate: make use a packageconfig + configuration fragment
• swupdate: even when hardware revision check is disabled HW_COMPATIBILITY, it says OK when it shouldn't (v2016.10.0)
  • If CONFIG_HW_COMPATIBILITY is disabled, the option -H is not available and the file /etc/hwrevision is not checked (checked on v2016.10, 9224371491b9cd38b00a5fcde2e1e2845a8443ed after 2017.01) tested with -d and -i
  • But in master if the HW compatibility check fails, the downloader does not exit -> Fix that bug
  • Disable HW_COMPATIBILITY:
    • without the /etc/hwrevision file: run an update; it will say OK but no update has been applied: I cannot reproduce it: the update is still applied
    • with the /etc/hwrevision: it will say OK but the update will be applied: I can reproduce it: why this is an issue?
    • Conclusion: with HW_COMPATIBILITY disabled, the /etc/hwrevision file is ignored.
• swupdate: add an argument to specify the cacert to be passed to curl
• swupdate: -c/check argument expects the -e argument but it should not
  • When the sw-description file contains only an images node, there is no issue because the list &swcfg->images is not empty
  • The issue comes when the sw-description contains multiple software set and and modes; in that case, we have to select one with -e, otherwise the the list &swcfg->images will be empty
• Yocto/Poky: factorize the configuration fragment feature
  • def get_cfg_files(d)
    • return filter(lambda x: x.endsWith('.cfg'), src_patches(d, True))
• libkcapi: write a Yocto recipe
  • The libkcapi is Yocto-ready https://github.com/smuellerDD/libkcapi/commit/a039f8a5adca57dc69a19d7361600c2f410e0c26
• create a dockerfile that interfaces with repo and Yocto
• U-Boot: socfpga_devkit node pour gpio0 and gpio2 with Sid sign-off
• U-Boot: fit_check_sign should be fixed: if the .itb has been generated with -E, the signature checking will fail. Fix it!
• e2tools: write a Yocto recipe
• tpm2_nvrelease: add a '\n' at the end of "tpm2_nvrelease -x 0x1500016 -a 0x40000001 -P 1a1b1c -X"
• ibm tss tools: add listpersistent
• intel tpm tools: add import/importpem