Read about our upcoming Code of Conduct on this issue

  1. 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: ./ [-q]  (from qemu-eos directory)
      Name starts with different letter to avoid typing ./ by mistake.
      branch : qemu
  2. 12 Apr, 2019 1 commit
  3. 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)
      branch : qemu
    • 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.
      branch : qemu
  4. 10 Apr, 2019 4 commits
  5. 09 Apr, 2019 4 commits
  6. 08 Apr, 2019 1 commit
  7. 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.
      branch : qemu
  8. 08 Apr, 2019 1 commit
  9. 06 Apr, 2019 2 commits
  10. 27 Mar, 2019 1 commit
  11. 25 Mar, 2019 3 commits
  12. 05 Mar, 2019 1 commit
  13. 03 Mar, 2019 1 commit
  14. 04 Mar, 2019 4 commits
  15. 11 Feb, 2019 1 commit
  16. 04 Mar, 2019 1 commit
  17. 11 Feb, 2019 2 commits
  18. 03 Mar, 2019 9 commits