1. 06 10月, 2020 1 次提交
  2. 30 5月, 2020 1 次提交
  3. 11 4月, 2020 1 次提交
  4. 06 2月, 2020 1 次提交
    • S
      sandbox: sdl: Move to use SDL2 · 96d0cd46
      Simon Glass 提交于
      Sandbox currently uses SDL1.2. SDL2 has been around for quite a while and
      is widely supported. It has a number of useful features. It seems
      appropriate to move sandbox over.
      
      Update the code to use SDL2 instead of SDL1.2.
      Signed-off-by: NSimon Glass <sjg@chromium.org>
      96d0cd46
  5. 12 10月, 2019 1 次提交
  6. 08 10月, 2019 1 次提交
  7. 24 7月, 2019 1 次提交
  8. 11 7月, 2019 2 次提交
  9. 24 4月, 2019 2 次提交
    • S
      sandbox: Move pre-console buffer out of the way of tracing · a1396cdc
      Simon Glass 提交于
      These two buffers currently conflict if tracing is enabled. Move the
      pre-console buffer and update the documentation.
      Signed-off-by: NSimon Glass <sjg@chromium.org>
      a1396cdc
    • S
      sandbox: Improve debugging in initcall_run_list() · 001d1885
      Simon Glass 提交于
      At present if one of the initcalls fails on sandbox the address printing
      is not help, e.g.:
      
        initcall sequence 0000557678967c80 failed at call 00005576709dfe1f (err=-96)
      
      This is because U-Boot gets relocated high into memory and the relocation
      offset (gd->reloc_off) does not work correctly for sandbox.
      
      Add support for finding the base address of the text region (at least on
      Linux) and use that to set the relocation offset. This makes the output
      better:
      
        initcall sequence 0000560775957c80 failed at call 0000000000048134 (err=-96)
      
      Then you use can use grep to see which init call failed, e.g.:
      
         $ grep 0000000000048134 u-boot.map
         stdio_add_devices
      
      Of course another option is to run it with a debugger such as gdb:
      
         $ gdb u-boot
         ...
         (gdb) br initcall.h:41
         Breakpoint 1 at 0x4db9d: initcall.h:41. (2 locations)
      
      Note that two locations are reported, since this function is used in both
      board_init_f() and board_init_r().
      
         (gdb) r
         Starting program: /tmp/b/sandbox/u-boot
         [Thread debugging using libthread_db enabled]
         Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
      
         U-Boot 2018.09-00264-ge0c2ba9814-dirty (Sep 22 2018 - 12:21:46 -0600)
      
         DRAM:  128 MiB
         MMC:
      
      Breakpoint 1, initcall_run_list (init_sequence=0x5555559619e0 <init_sequence_f>)
          at /scratch/sglass/cosarm/src/third_party/u-boot/files/include/initcall.h:41
      41				printf("initcall sequence %p failed at call %p (err=%d)\n",
         (gdb) print *init_fnc_ptr
         $1 = (const init_fnc_t) 0x55555559c114 <stdio_add_devices>
         (gdb)
      Signed-off-by: NSimon Glass <sjg@chromium.org>
      001d1885
  10. 26 11月, 2018 1 次提交
  11. 21 11月, 2018 2 次提交
  12. 30 9月, 2018 1 次提交
  13. 07 5月, 2018 2 次提交
    • T
      SPDX: Convert all of our single license tags to Linux Kernel style · 83d290c5
      Tom Rini 提交于
      When U-Boot started using SPDX tags we were among the early adopters and
      there weren't a lot of other examples to borrow from.  So we picked the
      area of the file that usually had a full license text and replaced it
      with an appropriate SPDX-License-Identifier: entry.  Since then, the
      Linux Kernel has adopted SPDX tags and they place it as the very first
      line in a file (except where shebangs are used, then it's second line)
      and with slightly different comment styles than us.
      
      In part due to community overlap, in part due to better tag visibility
      and in part for other minor reasons, switch over to that style.
      
      This commit changes all instances where we have a single declared
      license in the tag as both the before and after are identical in tag
      contents.  There's also a few places where I found we did not have a tag
      and have introduced one.
      Signed-off-by: NTom Rini <trini@konsulko.com>
      83d290c5
    • T
      README.sandbox: small typos · 1f154a63
      Trevor Woerner 提交于
      Signed-off-by: NTrevor Woerner <twoerner@gmail.com>
      1f154a63
  14. 19 2月, 2018 1 次提交
    • M
      sandbox: Add 64-bit sandbox · c6b89f31
      Mario Six 提交于
      To debug device tree issues involving 32- and 64-bit platforms, it is useful to
      have a generic 64-bit platform available.
      
      Add a version of the sandbox that uses 64-bit integers for its physical
      addresses as well as a modified device tree.
      Signed-off-by: NMario Six <mario.six@gdsys.cc>
      Added CONFIG_SYS_TEXT_BASE to configs/sandbox64_defconfig
      Signed-off-by: NSimon Glass <sjg@chromium.org>
      c6b89f31
  15. 15 9月, 2017 1 次提交
  16. 12 9月, 2017 1 次提交
  17. 12 7月, 2017 1 次提交
  18. 19 9月, 2016 1 次提交
  19. 26 7月, 2016 1 次提交
  20. 28 5月, 2016 1 次提交
  21. 15 4月, 2016 1 次提交
  22. 19 4月, 2015 3 次提交
  23. 31 1月, 2015 1 次提交
  24. 22 9月, 2014 1 次提交
  25. 17 5月, 2014 2 次提交
  26. 10 5月, 2014 2 次提交
  27. 10 12月, 2013 1 次提交
    • M
      sandbox: spi: Add new SPI flash driver · ffdb20be
      Mike Frysinger 提交于
      This adds a SPI flash driver which simulates SPI flash clients.
      Currently supports the bare min that U-Boot requires: you can
      probe, read, erase, and write.  Should be easy to extend to make
      it behave more exactly like a real SPI flash, but this is good
      enough to merge now.
      
      sjg@chromium.org added a README and tidied up code a little.
      Added a required map_sysmem() for sandbox.
      Signed-off-by: NMike Frysinger <vapier@gentoo.org>
      Signed-off-by: NSimon Glass <sjg@chromium.org>
      ffdb20be
  28. 15 10月, 2013 1 次提交
  29. 24 7月, 2013 1 次提交
  30. 29 7月, 2012 1 次提交
  31. 18 10月, 2011 1 次提交