This instance will be upgraded to Heptapod 0.21.0 (final) on 2021-04-23 at 10:30 UTC+2 (a few minutes of down time)

  1. 24 Mar, 2021 1 commit
  2. 01 Jan, 2021 1 commit
    • Alex's avatar
      Merge branch... · 682a0f7c837a
      Alex authored
      Merge branch 'topic/Ant/correct-uart_rx_interrupt-number-for-eos-1588612772652/bitbucket-pr-963' into 'branch/qemu'
      
      correct uart_rx_interrupt number for EOS M3
      
      See merge request !963
      
      --HG--
      branch : qemu
      682a0f7c837a
  3. 29 Dec, 2020 1 commit
  4. 28 Dec, 2020 1 commit
  5. 29 Dec, 2020 7 commits
  6. 15 Dec, 2020 1 commit
  7. 14 Dec, 2020 2 commits
  8. 29 Dec, 2020 1 commit
  9. 17 Dec, 2020 1 commit
  10. 14 Dec, 2020 2 commits
  11. 04 May, 2020 1 commit
  12. 16 Apr, 2019 2 commits
  13. 15 Apr, 2019 2 commits
  14. 09 Apr, 2019 1 commit
    • alex@thinkpad's avatar
      QEMU: script for reverting changes made in qemu-eos · 43b9e467ed5a
      alex@thinkpad authored
      (i.e. go back to some vanilla version without full reinstallation)
      
      Usage: ./sure_copy_from_contrib.sh [-q]  (from qemu-eos directory)
      
      Name starts with different letter to avoid typing ./copy_back_to_contrib.sh by mistake.
      
      --HG--
      branch : qemu
      43b9e467ed5a
  15. 12 Apr, 2019 1 commit
  16. 11 Apr, 2019 2 commits
    • alex@thinkpad's avatar
      QEMU install: reworked toolchain options · b1db6a5b131f
      alex@thinkpad authored
      - on all x86_64 Linux systems, user can choose between 32-bit and 64-bit toolchain
      - on all Intel systems, user can choose to override the existing ARM toolchain (and install a precompiled version that's known to work)
      - on x86 Linux systems, the script should install a 32-bit toolchain without asking
      - on all systems, user may keep the existing ARM compiler (arm-none-eabi-gdb) and compile gdb 8.1 from source
      - on non-Intel systems, the script should just check for a valid toolchain, and ask the user to install it manually (not tested)
      
      --HG--
      branch : qemu
      b1db6a5b131f
    • alex@thinkpad's avatar
      QEMU install: dropped support for arm-none-eabi-gdb installed from Ubuntu package manager · b671b1404ae7
      alex@thinkpad authored
      Too much of a moving target, e.g. working on Xenial and Bionic (with different packages!) but broken on Cosmic.
      
      Keeping arm-none-eabi-gcc from package manager as an option.
      
      For gdb, we'll use either a precompiled toolchain (64-bit 7-2018-q2, or any 32-bit version), or compile gdb 8.1 from source.
      
      --HG--
      branch : qemu
      b671b1404ae7
  17. 10 Apr, 2019 4 commits
  18. 09 Apr, 2019 4 commits
  19. 08 Apr, 2019 1 commit
  20. 09 Apr, 2019 1 commit
    • alex@thinkpad's avatar
      QEMU logging: updated DryOS and VxWorks task switch handling · 9049426c8cce
      alex@thinkpad authored
      It was quite hard to pass the test suite, as there were lots of edge cases:
      
      - context switch may happen either in a timer interrupt, or in a regular task (e.g. msleep, sempahores and so on)
      - context switch is not atomic - it happens a few instructions (or function calls!) afterh updating the current task pointer
      - until the registers are swapped for the new task, we are still on the stack of the previous task
      - there may be dummy task switches (i.e. from one task to the same task)
      - an interrupt can occur in the middle of a (non-atomic) context switch (!)
      - VxWorks models do not even use a unique task ID (!)
      
      Result: QEMU no longer crashes during logging tests!
      
      Issue: these cameras do not appear to use an unique task ID. Workaround: assign our own task IDs.
      
      --HG--
      branch : qemu
      9049426c8cce
  21. 08 Apr, 2019 1 commit
  22. 06 Apr, 2019 2 commits