Open Source Software TODO list: Difference between revisions

From Wiki :-)
Jump to navigation Jump to search
No edit summary
m Savoundg moved page Open Source Software TODO's list to Open Source Software TODO list without leaving a redirect
 
(21 intermediate revisions by the same user not shown)
Line 1: Line 1:
* safe dd: test if the output file in the form /dev/sdXY is a block device before writing it
* <s>ss: test if the output file in the form /dev/sdXY is a block device before writing it</s>: [https://github.com/manoj23/ss https://github.com/manoj23/ee]
* u-boot: generate a u-boot.fit image instead of overwriting u-boot.img
* ee: print progression of the writing (with speed) and the progression of the sync
* meta-swupdate: make use a packageconfig + configuration fragment
* u-boot: generate a u-boot.itb image instead of overwriting u-boot.img
* <s>meta-swupdate: make use a packageconfig + configuration fragment</s>
* swupdate: even when hardware revision check is disabled HW_COMPATIBILITY, it says OK when it shouldn't (v2016.10.0)
* 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
** 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: 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
* Yocto/Poky: factorize the configuration fragment feature
* libkcapi: write a Yocto recipe
** def get_cfg_files(d)
*** return filter(lambda x: x.endsWith('.cfg'), src_patches(d, True))
* <s>libkcapi: write a Yocto recipe</s>
** <s>The libkcapi is Yocto-ready https://github.com/smuellerDD/libkcapi/commit/a039f8a5adca57dc69a19d7361600c2f410e0c26</s>
** Someone wrote it:  [https://slack-redir.net/link?url=http%3A%2F%2Fcgit.openembedded.org%2Fmeta-openembedded%2Ftree%2Fmeta-oe%2Frecipes-crypto%2Flibkcapi%2Flibkcapi_git.bb%3Fh%3Dmaster&v=3 http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/recipes-crypto/libkcapi/libkcapi_git.bb?h=master]
* create a dockerfile that interfaces with repo and Yocto
* create a dockerfile that interfaces with repo and Yocto
* <s>U-Boot: socfpga_devkit node pour gpio0 and gpio2 with Sid sign-off</s>
* 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
* Fix directfb/fbdev memoryleak

Latest revision as of 17:55, 31 March 2020

  • ss: test if the output file in the form /dev/sdXY is a block device before writing it: https://github.com/manoj23/ee
  • ee: print progression of the writing (with speed) and the progression of the sync
  • 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
  • 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
  • Fix directfb/fbdev memoryleak