1. 11 Dec, 2020 1 commit
    • Richard Hughes's avatar
      Use honggfuzz to fuzz firmware rather than AFL · c4ca8e25
      Richard Hughes authored
      This has better multi-core performance and can run in persistent mode -- which
      allows us to construct a test harness of all the parsers (which takes time) and
      then just reuse the process for lots of different data.
      c4ca8e25
  2. 03 Nov, 2020 1 commit
  3. 02 Nov, 2020 1 commit
  4. 07 May, 2020 1 commit
  5. 31 Dec, 2019 1 commit
  6. 02 Oct, 2019 1 commit
  7. 22 Aug, 2019 1 commit
  8. 05 Mar, 2019 1 commit
  9. 19 Feb, 2019 1 commit
  10. 04 Dec, 2018 1 commit
  11. 14 Oct, 2018 1 commit
  12. 29 Jan, 2018 1 commit
  13. 17 Dec, 2017 1 commit
  14. 06 Nov, 2017 1 commit
  15. 12 Oct, 2017 1 commit
  16. 08 Sep, 2017 1 commit
  17. 24 Aug, 2017 1 commit
  18. 10 Jul, 2017 1 commit
  19. 14 Jun, 2017 1 commit
  20. 13 Jun, 2017 3 commits
  21. 08 Jun, 2017 1 commit
  22. 07 Jun, 2017 2 commits
  23. 26 May, 2017 4 commits
  24. 12 Dec, 2016 1 commit
    • Richard Hughes's avatar
      Convert the providers to plugins to simplify code and for future features · cff38bcb
      Richard Hughes authored
      This is a large commit that removes all the providers and turns them into
      plugins. I think having both providers _and_ plugins was super confusing.
      
      Plugins are loaded at runtime so you could in theory develop a new plugin
      without putting it in the fwupd source tree, although there are no installed
      headers or PC files as I'm not sure it's a good idea at this stage.
      
      This commit moves all the per-provider docs, tests, notes, debug dumps and test
      data to plugin-specific directories -- these also allows the plugin author to
      "own" more of the source tree so we don't enforce fu- prefixes and the style
      guide everywhere.
      
      This allows us to run the same action on all the plugins in the future, so we
      could have a prepare(FuPlugin, FuDevice) and cleanup(FuPlugin, FuDevice) run
      on *all* plugins, so doing an update using one plugin would allow us to work
      around hardware quirks in other plugins.
      
      If I've broken your out-of-tree provider it's trivial to port to the new API
      with sed and a fixed up build file. If you need help please let me know.
      cff38bcb
  25. 23 Aug, 2016 1 commit
  26. 21 Jul, 2016 1 commit
  27. 20 Jul, 2016 1 commit
  28. 13 Jul, 2016 1 commit
  29. 01 Apr, 2016 6 commits