Read about our upcoming Code of Conduct on this issue

  1. 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
  2. 06 Apr, 2019 1 commit
    • alex@thinkpad's avatar
      QEMU: refactored with eos_get_mem_w · 5619c64e5e66
      alex@thinkpad authored
      Before: uint32_t x; cpu_physical_memory_read(addr, &x, 4)
      After: uint32_t x = eos_get_mem_w(s, addr);
      
      Also, minor cleanups to eos_get_current_task_* (not expected to make a difference)
      
      --HG--
      branch : qemu
      5619c64e5e66
  3. 05 Mar, 2019 1 commit
  4. 03 Mar, 2019 2 commits
  5. 11 Feb, 2019 2 commits
  6. 06 Jan, 2019 1 commit
  7. 30 Dec, 2018 1 commit
  8. 28 Dec, 2018 1 commit
  9. 10 Sep, 2018 2 commits
  10. 07 Aug, 2018 1 commit
  11. 02 Aug, 2018 1 commit
  12. 31 Jul, 2018 1 commit
  13. 30 Jul, 2018 2 commits
  14. 30 Apr, 2018 1 commit
    • alex@thinkpad's avatar
      QEMU: initial support for DIGIC 7 EOS (200D, 77D, 6D2) · a20c79bcfe12
      alex@thinkpad authored
      - added ROMID; updated MemDiv, XDMAC, SDIO
      - emulation starts many tasks, talks to MPU, initializes SD, creates the DCIM directory on the virtual card
      - fails with ERROR WaitPU1 TimeOut
      - dumpf does not save any logs (figure out why)
      - note: M5 ROM should now be loaded as ROM0
      
      --HG--
      branch : qemu
      a20c79bcfe12
  15. 29 Apr, 2018 1 commit
  16. 28 Apr, 2018 1 commit
    • alex@thinkpad's avatar
      QEMU: experimental UTimer emulation · 9416cfa241d7
      alex@thinkpad authored
      - these look pretty much like regular timers (same offsets), but behave like HPTimers!
      - UTimer patches from DIGIC 6 no longer needed!
      - fine-tuned HPTimer messages
      
      --HG--
      branch : qemu
      9416cfa241d7
  17. 25 Apr, 2018 2 commits
  18. 23 Apr, 2018 1 commit
  19. 21 Apr, 2018 1 commit
  20. 14 Apr, 2018 1 commit
  21. 31 Mar, 2018 1 commit
  22. 14 Mar, 2018 1 commit
  23. 13 Mar, 2018 2 commits
  24. 09 Feb, 2018 1 commit
  25. 13 Mar, 2018 2 commits
  26. 07 Jan, 2018 2 commits
  27. 06 Jan, 2018 1 commit
  28. 05 Jan, 2018 1 commit
  29. 06 Jan, 2018 1 commit
  30. 03 Jan, 2018 1 commit
  31. 02 Jan, 2018 2 commits
    • alex@thinkpad's avatar
      QEMU: changed I/O logging behavior · 14755cb30ac4
      alex@thinkpad authored
      - "-d io" implies "-d nochain -singlestep" (this prints correct PC values, but emulation is slower)
      - "-d io_quick" to get the old behavior (faster, with incorrect PC values)
      - "-d io_log" to print mmio_log entries for dm-spy-experiments
      - "-d nochain" always implies "-singlestep" (easier to enable this mode on other kind of logs that may need it)
      - updated README
      
      --HG--
      branch : qemu
      14755cb30ac4
    • alex@thinkpad's avatar
      QEMU: moved 7D2 patches to GDB scripts; · 1eedbfb98e55
      alex@thinkpad authored
      initial GDB script for 7D2 slave
      
      --HG--
      branch : qemu
      1eedbfb98e55