1. 08 1月, 2019 1 次提交
  2. 02 1月, 2019 2 次提交
  3. 01 1月, 2019 2 次提交
  4. 18 12月, 2018 1 次提交
  5. 17 12月, 2018 1 次提交
  6. 16 12月, 2018 1 次提交
  7. 13 12月, 2018 2 次提交
  8. 04 12月, 2018 4 次提交
  9. 30 11月, 2018 1 次提交
    • S
      test: Add a 'make qcheck' target for quicker testing · 499fde5c
      Simon Glass 提交于
      At present tests are quite slow to run, over a minute on my machine. This
      presents a considerable barrier to bisecting for failures.
      
      The slowest tests are the filesystem ones and the buildman --fetch-arch
      test. Add a new 'qcheck' target that skips these tests. This reduces test
      time down to about 40 second, still too long, but bearable.
      Signed-off-by: NSimon Glass <sjg@chromium.org>
      499fde5c
  10. 29 11月, 2018 1 次提交
  11. 21 11月, 2018 1 次提交
  12. 15 11月, 2018 1 次提交
  13. 30 10月, 2018 1 次提交
  14. 20 10月, 2018 1 次提交
  15. 16 10月, 2018 1 次提交
  16. 09 10月, 2018 1 次提交
  17. 08 10月, 2018 1 次提交
  18. 05 10月, 2018 1 次提交
  19. 02 10月, 2018 1 次提交
  20. 28 9月, 2018 1 次提交
  21. 26 9月, 2018 1 次提交
    • B
      Makefile: Use -fno-strict-aliasing globally · 5bc11922
      Bin Meng 提交于
      The -fstrict-aliasing option is implicitly enabled at levels -O2,
      -O3, -Os by GCC. This option allows the compiler to assume the
      strictest aliasing rules applicable to the language being compiled.
      For example, the practice of reading from a different union member
      than the one most recently written to (called "type-punning") is
      common. In this case, "type-punning" only works if the memory is
      accessed through the union type, but might not work by taking the
      address, casting the resulting pointer and dereferencing the result,
      which is an undefined behavior per the "strict aliasing rules".
      
      GCC's -Wstrict-aliasing (included in -Wall) option does not catch
      all cases, but does attempt to catch the more common pitfalls. So
      there are cases that GCC does not report but the codes are violating
      the "strict aliasing rules".
      
      Given lots of codes that may be written to rely on "type-punning",
      and Linux kernel disables it by -fno-strict-aliasing globally, since
      U-Boot currently does this on nds32/riscv/x86 builds only, extend
      this for all architecture builds.
      Signed-off-by: NBin Meng <bmeng.cn@gmail.com>
      Reviewed-by: NTom Rini <trini@konsulko.com>
      Reviewed-by: NSimon Glass <sjg@chromium.org>
      5bc11922
  22. 20 9月, 2018 1 次提交
  23. 15 9月, 2018 1 次提交
  24. 11 9月, 2018 1 次提交
  25. 04 9月, 2018 1 次提交
  26. 20 8月, 2018 1 次提交
  27. 14 8月, 2018 1 次提交
  28. 31 7月, 2018 1 次提交
  29. 27 7月, 2018 2 次提交
  30. 26 7月, 2018 1 次提交
  31. 24 7月, 2018 1 次提交
    • M
      doc: Replace DocBook with sphinx-based docs · 78a88f79
      Mario Six 提交于
      The Linux kernel moved to sphinx-based documentation and got rid of the
      DocBook based documentation quite a while ago. Hence, the DocBook
      documentation for U-Boot should be converted as well.
      
      To achieve this, import the necessary files from Linux v4.17, and
      convert the current DocBook documentation (three files altogether) to
      sphinx/reStructuredText.
      
      For now, all old DocBook documentation was merged into a single
      handbook, tentatively named "U-Boot Hacker Manual".
      
      For some source files, the documentation style was changed to comply
      with kernel-doc; no functional changes were applied.
      Signed-off-by: NMario Six <mario.six@gdsys.cc>
      78a88f79
  32. 11 7月, 2018 2 次提交