| 671bb8c | Daniel Fort | 28 April 2019, 11:21:42 UTC | Merged in kitorPL/magic-lantern/kitor/eosr_120 (pull request #959) Update EOS R to 1.2.0 firmware | 28 April 2019, 11:21:42 UTC |
| 32e24c4 | Kajetan Krykwinski | 28 April 2019, 11:06:00 UTC | correct bmp_vram_info for EOS R | 28 April 2019, 11:06:00 UTC |
| cf4b8e1 | Kajetan Krykwinski | 27 April 2019, 18:54:28 UTC | R 1.2.0 firmware signature | 27 April 2019, 18:54:28 UTC |
| 545a6a4 | Kajetan Krykwinski | 25 April 2019, 16:09:05 UTC | Fix stubs | 25 April 2019, 16:09:05 UTC |
| 81c8fae | Kajetan Krykwinski | 22 April 2019, 19:45:15 UTC | signature definition for R 1.2.0 | 22 April 2019, 19:45:15 UTC |
| d3a14fb | Kajetan Krykwinski | 22 April 2019, 19:27:06 UTC | fix typo in stubs | 22 April 2019, 19:27:06 UTC |
| c4a3fcc | Kajetan Krykwinski | 22 April 2019, 19:23:29 UTC | update plaform map | 22 April 2019, 19:23:29 UTC |
| 1b3918d | Kajetan Krykwinski | 22 April 2019, 19:19:36 UTC | updated stubs to R 1.2.0 | 22 April 2019, 19:19:36 UTC |
| d55b049 | Kajetan Krykwinski | 22 April 2019, 18:01:10 UTC | rom version updates | 22 April 2019, 18:01:10 UTC |
| 652cdf1 | Kajetan Krykwinski | 22 April 2019, 18:00:01 UTC | updated EOSR to 1.2.0 | 22 April 2019, 18:00:01 UTC |
| b591c14 | Kajetan Krykwinski | 22 April 2019, 19:49:20 UTC | branch created | 22 April 2019, 19:49:20 UTC |
| 1b7baa2 | Daniel Fort | 13 April 2019, 19:51:19 UTC | M50: update to Canon firmware version 1.0.2 | 13 April 2019, 19:51:19 UTC |
| e3a7397 | alex@thinkpad | 27 March 2019, 19:42:59 UTC | 77D: empty gui.h required for compiling | 27 March 2019, 19:42:59 UTC |
| a105b57 | alex@thinkpad | 23 March 2019, 17:41:48 UTC | fio-ml.h: updated fio_file structure for DIGIC 6/7/8 Tested on 5D4, 200D, 77D and M50, all in QEMU. | 23 March 2019, 17:41:48 UTC |
| 007b0ec | alex@thinkpad | 27 March 2019, 09:53:35 UTC | Merged qemu into digic6-dumper (minimal/qemu-fio test) | 27 March 2019, 09:53:35 UTC |
| 30c8823 | alex@thinkpad | 27 March 2019, 09:47:47 UTC | qemu-fio: burn-in test for FindClose (FindFirst/FindClose/FindNext repeated many times) | 27 March 2019, 09:47:47 UTC |
| 1081787 | alex@thinkpad | 25 March 2019, 21:02:50 UTC | qemu-fio: minimal test code for file I/O routines in QEMU Only FindFirst/FindNext test for now; others to be added later. Compile with e.g.: cd minimal/qemu-fio make MODEL=60D clean make MODEL=60D install_qemu CONFIG_QEMU=y FIXME: works on DIGIC 4/5, fails on DIGIC >= 6, not tested on DIGIC 2/3. | 25 March 2019, 21:02:50 UTC |
| 8896e73 | alex@thinkpad | 25 March 2019, 21:06:13 UTC | QEMU tests: minor fix for HPTimer test (slightly faster, no longer times out) | 25 March 2019, 21:06:13 UTC |
| 0f433fb | alex@thinkpad | 25 March 2019, 17:14:43 UTC | 5D4: sync debugmsg.gdb to the one from chris_overseas (a8bdfa9) | 25 March 2019, 17:14:43 UTC |
| 96a2ffe | alex@thinkpad | 23 March 2019, 22:52:32 UTC | DIGIC 6/7/8 Hello World: reworked with 32-bit access in the display buffer | 23 March 2019, 22:52:32 UTC |
| a8c6554 | alex@thinkpad | 23 March 2019, 22:47:44 UTC | DIGIC 6/7/8 Hello World: also set opacity for all pixels (should now work in LiveView for UYVY models, such as 80D and 200D) | 23 March 2019, 22:47:44 UTC |
| 87bd868 | alex@thinkpad | 23 March 2019, 21:47:22 UTC | DIGIC 6/7/8 Hello World: set U and V for all pixels on UYVY models (80D, 200D and others) No more color artifacts at font edges. | 23 March 2019, 21:47:22 UTC |
| 3131140 | alex@thinkpad | 23 March 2019, 22:41:28 UTC | DIGIC 6/7/8 Hello World: use rgb2yuv422 from imgconv.c/h; (@names_are_hard, why did you swap the endianness in your rgb2yuv422?!) | 23 March 2019, 22:41:28 UTC |
| b1cb6b1 | alex@thinkpad | 23 March 2019, 21:33:55 UTC | imgconv.h: updated YUV<->RGB routines for DIGIC 6/7/8 (to be tested) U and V now have an offset of 0x80; previously, on DIGIC 5 and earlier models, achromatic was 0. | 23 March 2019, 21:33:55 UTC |
| a900e0a | alex@thinkpad | 23 March 2019, 19:34:00 UTC | internals-common: assuming all DIGIC 5 and newer models use Rec.709 TODO: need a trained eye to check. | 23 March 2019, 19:34:00 UTC |
| f0a866c | alex@thinkpad | 23 March 2019, 20:55:05 UTC | DIGIC 6/7/8: generic Hello World code, based on names_are_hard's and chris_overseas' work. To be tested. MARV structure: https://www.magiclantern.fm/forum/index.php?topic=17360.msg212411#msg212411 | 23 March 2019, 20:55:05 UTC |
| 6af04b4 | alex@thinkpad | 23 March 2019, 18:58:29 UTC | internals-common: enabled new DryOS task hooks on all new models (DIGIC 6/7/8; to be tested) | 23 March 2019, 18:58:29 UTC |
| 5b61a11 | alex@thinkpad | 23 March 2019, 17:15:29 UTC | internals-common.h: common definitions for CPU types and DIGIC families | 23 March 2019, 17:15:29 UTC |
| f42df4c | alex@thinkpad | 24 March 2019, 23:02:17 UTC | check_stubs.py: fix crash when attempting to compare stubs present in only one file | 24 March 2019, 23:02:17 UTC |
| 2e40e30 | alex@thinkpad | 25 March 2019, 15:51:22 UTC | DIGIC 6/7/8: explicit macros for Thumb code, ARM code and data pointers in stubs.S - THUMB_FN: for Thumb functions - ARM32_FN: for 32-bit ARM functions - DATA_PTR: for stubs not pointing to code (these can't be called as functions) Advantages: - Thumb bit handled automatically (less error-prone) - easier to read (compared to checking address parity manually) - easier to copy stubs from/to IDA or GDB scripts (no more need to edit the Thumb bit manually) Also: - updated maintenance scripts from contrib/stub-format and stub-checker - declared data stubs so they won't be incorrectly tagged as code - removed "Thumb" mentions from comments | 25 March 2019, 15:51:22 UTC |
| 3f416d1 | alex@thinkpad | 25 March 2019, 15:45:31 UTC | DIGIC 6/7/8: aligned comments | 25 March 2019, 15:45:31 UTC |
| a300f3a | alex@thinkpad | 23 March 2019, 15:47:18 UTC | DIGIC 7/8: malloc/free stubs should be private (not yet used in source code) | 23 March 2019, 15:47:18 UTC |
| a27e004 | alex@thinkpad | 25 March 2019, 15:30:30 UTC | DIGIC 6/7/8: reordered stubs | 25 March 2019, 15:30:30 UTC |
| dbe9fb9 | alex@thinkpad | 25 March 2019, 15:25:43 UTC | stub-reorder.py: do not attempt to find missing stubs by default | 25 March 2019, 15:25:43 UTC |
| 35924da | alex@thinkpad | 25 March 2019, 15:22:56 UTC | stub-reorder.py: updated sorting order heuristics: - ignore the underscore from stub names - free and free_dma_memory should be right after malloc/alloc_dma_memory - file stubs should be first - create/delete/open/close/etc should be grouped, usually first - property functions: logical order is very close to reverse alphabetical order | 25 March 2019, 15:22:56 UTC |
| dd42296 | alex@thinkpad | 15 March 2019, 07:56:57 UTC | stub-reorder.py: minor updates for DIGIC 6/7/8 | 15 March 2019, 07:56:57 UTC |
| 3d64ff9 | alex@thinkpad | 15 March 2019, 07:25:55 UTC | 200D, 77D: comments for interrupt and memory allocation stubs | 15 March 2019, 07:25:55 UTC |
| e3c759f | alex@thinkpad | 23 March 2019, 15:23:52 UTC | 77D: some nitpicks | 23 March 2019, 15:23:52 UTC |
| b83de2d | calle2010 | 19 March 2019, 06:48:15 UTC | 77D.102 stubs, firmware signature based on the work from aprofiti in ML forum https://www.magiclantern.fm/forum/index.php?topic=19737.msg206736#msg206736 (f387fc1, b44e17e, e25589c, 1578fb6, 397b9a2, 0264f84, minus the experiments -- a1ex) | 19 March 2019, 06:48:15 UTC |
| 54cac0d | calle2010 | 14 March 2019, 21:57:27 UTC | move platform directory 77D.100 to 77D.102 | 14 March 2019, 21:57:27 UTC |
| 04fed83 | alex@thinkpad | 05 March 2019, 14:22:32 UTC | QEMU: 32-bit DIGIC timer support (DIGIC 6 and newer) | 05 March 2019, 14:22:32 UTC |
| d531c26 | alex@thinkpad | 03 March 2019, 23:59:18 UTC | QEMU: updated emulation for 7D2 1.0.4 (ROM from real hardware; no longer using 80D bootloader). Some workarounds were required to emulate the bootloader. Communication between the two cores is not yet handled. | 03 March 2019, 23:59:18 UTC |
| a9a9fbe | alex@thinkpad | 04 March 2019, 09:37:30 UTC | QEMU: renamed 7D2M to 7D2 (slave core is still 7D2S) | 04 March 2019, 09:37:30 UTC |
| cf601ef | alex@thinkpad | 04 March 2019, 09:34:36 UTC | QEMU: updated tests for 5D 1.1.1 and 400D 1.1.1, both ROMs from real hardware (previously, it was a mix between an incomplete 5D firmware and 1000D bootloader) | 04 March 2019, 09:34:36 UTC |
| e1f335e | alex@thinkpad | 04 March 2019, 09:27:50 UTC | QEMU: imported scnprintf/vscnprintf from Linux kernel and fixed incorrect usage in previous code (adapted commit e8bb011b) | 04 March 2019, 09:27:50 UTC |
| bca7890 | alex@thinkpad | 04 March 2019, 08:44:46 UTC | QEMU: fixed indentation of multiline debug strings (-d debugmsg) | 04 March 2019, 08:44:46 UTC |
| 99b6ab0 | alex@thinkpad | 28 February 2019, 22:08:50 UTC | Memory backend: use const char * for read-only strings | 28 February 2019, 22:08:50 UTC |
| 7d77ecb | alex@thinkpad | 28 February 2019, 21:51:32 UTC | tasks: use const char * for DryOS task names | 28 February 2019, 21:51:32 UTC |
| 867d6d0 | alex@thinkpad | 28 February 2019, 21:18:48 UTC | tasks.h: renamed current_task->name to current_task->task_name; updated old code to use get_current_task_name() instead. A few places still require raw access to the task_name field (e.g. tskmon). | 28 February 2019, 21:18:48 UTC |
| 813b161 | alex@thinkpad | 28 February 2019, 21:11:36 UTC | get_current_task_name: updated interrupt ID for DIGIC 6/7/8 (no need to shift it by 2, unlike DIGIC 5 and earlier) | 28 February 2019, 21:11:36 UTC |
| be15292 | alex@thinkpad | 28 February 2019, 21:11:36 UTC | get_current_task_name: moved into tasks.h to remove duplicate code It was in 5 different places in ML source, not counting current_task->name and QEMU source. | 28 February 2019, 21:11:36 UTC |
| 27ee197 | alex@thinkpad | 28 February 2019, 17:37:14 UTC | log-d678: maximum MPU message size is 0xFF chars (no reason to use a smaller size) | 28 February 2019, 17:37:14 UTC |
| b50f71f | alex@thinkpad | 27 February 2019, 19:33:37 UTC | log-d678: use 512 bytes for MPU messages; use the same buffer for both mpu_send/recv | 27 February 2019, 19:33:37 UTC |
| 22ee541 | alex@thinkpad | 26 February 2019, 22:19:38 UTC | log-d678: only check for MPU messages on the first CPU core (they don't arrive on the second core anyway, but our checks may cause race conditions) | 26 February 2019, 22:19:38 UTC |
| c2588ab | alex@thinkpad | 26 February 2019, 21:35:28 UTC | log-d678: attempt to use Canon's cli/spinlock function on DIGIC 7/8 (200D for now) It appears to be some sort of cli/sei valid for both cores. To be tested. | 26 February 2019, 21:35:28 UTC |
| 51a991f | alex@thinkpad | 26 February 2019, 21:27:16 UTC | arm-mcr.h: read_cpsr | 26 February 2019, 21:27:16 UTC |
| 77049f1 | alex@thinkpad | 26 February 2019, 20:50:28 UTC | spinlock: volatile keyword is required | 26 February 2019, 20:50:28 UTC |
| fa0dedd | alex@thinkpad | 26 February 2019, 13:58:45 UTC | Moved spinlock functions into arm-mcr.h (spin_lock, spin_unlock); refactored log-d678.c | 26 February 2019, 13:58:45 UTC |
| ec48414 | alex@thinkpad | 26 February 2019, 13:41:51 UTC | log-d6: __sync_lock_test_and_set requires an explicit spinning loop https://stackoverflow.com/questions/1383363/is-my-spin-lock-implementation-correct-and-optimal | 26 February 2019, 13:41:51 UTC |
| 4e158ab | alex@thinkpad | 26 February 2019, 08:45:05 UTC | log-d678: attempt to log messages from both CPU cores on DIGIC 7/8 (to be tested on real hardware) http://infocenter.arm.com/help/topic/com.arm.doc.faqs/ka4175.html http://infocenter.arm.com/help/topic/com.arm.doc.ddi0388f/CBBDIIFI.html | 26 February 2019, 08:45:05 UTC |
| 47be065 | alex@thinkpad | 26 February 2019, 07:33:53 UTC | Renamed log-d6.[ch] to log-d678.[ch] and minimal-d6.c to minimal-d678.c These files are starting to get code specific to DIGIC 7/8. They are not directly usable on DIGIC 8 yet, as most of the functions we need to override are in ROM. Only in QEMU for now. | 26 February 2019, 07:33:53 UTC |
| d89e9a1 | alex@thinkpad | 26 February 2019, 07:21:20 UTC | arm-mcr.h, log-d6.h: renamed get_cpuid to get_cpu_id to avoid confusion with CPUID aka CPU model identification MPIDR is not 100% correct; we extract only specific bits from it. These bits are called "CPU ID" in ARM docs. http://infocenter.arm.com/help/topic/com.arm.doc.ddi0388e/CIHEBGFG.html | 26 February 2019, 07:21:20 UTC |
| b882ef8 | alex@thinkpad | 25 February 2019, 22:36:34 UTC | log-d6: refuse to run on CPU cores other than #0 Fixes corrupted logs on DIGIC 7/8 (confirmed on 200D by @names_are_hard ). Cause: race condition between the two processor cores. Even if we load ML on core #0 only, when overriding DebugMsg / ISR hooks / etc, the change is also visible from the second core. Disabling interrupts won't help. TODO: figure out how to do mutual exclusion between the two cores. | 25 February 2019, 22:36:34 UTC |
| 73ea1bb | alex@thinkpad | 25 February 2019, 22:36:34 UTC | arm-mcr.h: get_cpuid() for multi-core processors (DIGIC 7/8) | 25 February 2019, 22:36:34 UTC |
| 041d3be | alex@thinkpad | 21 February 2019, 19:09:43 UTC | 5D4: hardcoded logging buffers, based on chris_overseas' experiment https://www.magiclantern.fm/forum/index.php?topic=17695.msg212320#msg212320 CONFIG_MMIO_TRACE works in QEMU. | 21 February 2019, 19:09:43 UTC |
| b6775ab | alex@thinkpad | 21 February 2019, 17:40:10 UTC | io_trace: allow CONFIG_MMIO_TRACE for minimal targets, too (removed the 80D workaround) | 21 February 2019, 17:40:10 UTC |
| 00c70bd | Chris Miller | 21 February 2019, 19:53:32 UTC | 5D4: updated the codebase to 1.1.2 3bf2df7, 73990b1, 24dbfdb, c0f8a82, 3e04262 from https://bitbucket.org/chris_miller/ml-fork/branch/5d4-112 | 21 February 2019, 19:53:32 UTC |
| ab004de | alex@thinkpad | 21 February 2019, 17:15:19 UTC | check-stubs.py: also check ROM/RAM contents, 8 bytes for each stub (optional) RAM files should be created with the Portable ROM dumper. RAM files, if any, should be created with romcpy.sh (QEMU: -d romcpy). | 21 February 2019, 17:15:19 UTC |
| 7e5ccc0 | alex@thinkpad | 20 February 2019, 09:06:22 UTC | check-stubs.py: updated heuristics for DIGIC 6/7/8 - everything above E0000000 is ROM - check parity differences (Thumb bit) - check "delta" changes (it's expected to drift, but no large jumps) | 20 February 2019, 09:06:22 UTC |
| f06a432 | alex@thinkpad | 15 February 2019, 22:57:31 UTC | EOS R: skip 0x82000000-0x83000000 for CONFIG_MARK_UNUSED_MEMORY_AT_STARTUP (apparently used as shared memory by a secondary core, codenamed Shirahama) | 15 February 2019, 22:57:31 UTC |
| c062b32 | alex@thinkpad | 15 February 2019, 22:13:11 UTC | EOS R: UNCACHEABLE macro is no longer valid; using a workaround for CONFIG_MARK_UNUSED_MEMORY_AT_STARTUP | 15 February 2019, 22:13:11 UTC |
| 55fface | alex@thinkpad | 15 February 2019, 22:01:11 UTC | EOS R, M50: updated CONFIG_MARK_UNUSED_MEMORY_AT_STARTUP (see bee6ec3 for details and usage notes) | 15 February 2019, 22:01:11 UTC |
| d7c9d6b | alex@thinkpad | 14 February 2019, 22:31:58 UTC | M50: uart_printf (not yet used, but... required to compile) | 14 February 2019, 22:31:58 UTC |
| 2a62182 | alex@thinkpad | 14 February 2019, 20:57:23 UTC | EOS R: added uart_printf for easier debugging | 14 February 2019, 20:57:23 UTC |
| 5e6d34c | alex@thinkpad | 14 February 2019, 20:43:05 UTC | minimal-d78: need to call FIO_RemoveFile before FIO_CreateFile | 14 February 2019, 20:43:05 UTC |
| f065f08 | alex@thinkpad | 14 February 2019, 18:34:40 UTC | EOS R: LED test code (not enabled by default) | 14 February 2019, 18:34:40 UTC |
| 9dd709e | alex@thinkpad | 14 February 2019, 18:13:18 UTC | EOS R: updated to 1.1.0 (note to self: check firmware version next time) | 14 February 2019, 18:13:18 UTC |
| 0c1b6be | alex@thinkpad | 14 February 2019, 17:15:19 UTC | EOS R: initial platform directory - firmware 1.0.0 - boot process tested in QEMU - confirmed to boot on real hardware - very simple logging works (with Canon's DebugMsg) - ROM dumping from main firmware also works | 14 February 2019, 17:15:19 UTC |
| 3b26e45 | alex@thinkpad | 14 February 2019, 06:32:53 UTC | reboot.c: debug code for jumping into Canon's main firmware (disabled by default) | 14 February 2019, 06:32:53 UTC |
| e1397a5 | alex@thinkpad | 14 February 2019, 06:29:41 UTC | DIGIC 8: MMIO tricks required to boot (tested on EOS R; maybe also needed on M50/SX70) | 14 February 2019, 06:29:41 UTC |
| e83d43c | alex@thinkpad | 13 February 2019, 09:34:39 UTC | DIGIC 6: moved MMIO boot tricks in reboot.c - for consistency - 7D may use two different boot methods ("classic" and "cache hack"); keeping this in reboot.c reduces code duplication - in the future, we will want to be able to jump to any Canon firmware from the same binary; this will have to be done from reboot.c | 13 February 2019, 09:34:39 UTC |
| b41ef49 | alex@thinkpad | 13 February 2019, 09:30:35 UTC | 7D, 7D2, 5DS, 5DSR: use CONFIG_DUAL_DIGIC (to enable the specific boot tricks) | 13 February 2019, 09:30:35 UTC |
| f5dd789 | alex@thinkpad | 13 February 2019, 09:28:18 UTC | CONFIG_DIGIC_version is now mandatory; defined CONFIG_DIGIC_IV on models using one. | 13 February 2019, 09:28:18 UTC |
| 1a816d9 | alex@thinkpad | 11 February 2019, 13:25:32 UTC | QEMU: fixed Thumb code disassembly with qdisas This used to work in earlier versions, but target_disas changed its syntax in 2.5.0. Useful for debugging io_trace on DIGIC 6 (with CONFIG_QEMU=y). | 11 February 2019, 13:25:32 UTC |
| f8742e6 | alex@thinkpad | 04 March 2019, 09:31:07 UTC | QEMU: fixed TCM size info (broken in df56963); simplified condition for 946_PRBS size info | 04 March 2019, 09:31:07 UTC |
| a4c2f32 | alex@thinkpad | 11 February 2019, 13:25:32 UTC | QEMU: better description for DRSR, useful for emulating io_trace on DIGIC 6: - enable bit (similar to PRBS on DIGIC 5 and earlier) - consistency check for base address and size (base address must be multiple of size - Cortex R4 TRM p.178) - subregion disable bits (if used) Useful for emulating io_trace. Note: QEMU already calls tlb_flush when writing to DRSR, DRBAR or DRACR. No need to apply e4fd44e on DIGIC 6. | 11 February 2019, 13:25:32 UTC |
| 3643ed5 | alex@thinkpad | 11 February 2019, 13:25:32 UTC | QEMU: print PC when taking an exception | 11 February 2019, 13:25:32 UTC |
| dce506b | alex@thinkpad | 03 March 2019, 14:51:40 UTC | QEMU install: option to to keep or replace existing sd.img and cf.img, if any | 03 March 2019, 14:51:40 UTC |
| eed1db3 | alex@thinkpad | 03 March 2019, 14:36:34 UTC | QEMU install: always use qemu-eos as username | 03 March 2019, 14:36:34 UTC |
| 10624aa | alex@thinkpad | 03 March 2019, 14:23:11 UTC | QEMU: updated SD/CF image with the latest portable display test (19f18f0 from recovery branch) | 03 March 2019, 14:23:11 UTC |
| a8558f5 | alex@thinkpad | 03 March 2019, 13:47:25 UTC | QEMU test suite: updated for latest ROM dumper - now working on all EOS models - always update to latest version - allow RESCUE.LOG alongside with the ROM dumps - report extra files on the SD card, if any | 03 March 2019, 13:47:25 UTC |
| a71a983 | alex@thinkpad | 03 March 2019, 12:19:52 UTC | QEMU: make sure all models have correct ROM sizes defined - do not allow ROM files with duplicate data - most models do not have ROM0; only define where it is actually used - ROM0/1, where present, should be defined with the right size (too low - won't boot; too high - will fail the duplication test) - test results: context changed in some models without ROM0 (noise from the ROM dump was sometimes pointing to strings in ROM1) https://www.magiclantern.fm/forum/index.php?topic=5601.msg212692#msg212692 | 03 March 2019, 12:19:52 UTC |
| 7b64623 | alex@thinkpad | 03 March 2019, 11:26:38 UTC | GDB scripts: workaround to prevent GDB from crashing on 5D It appears to be a bug in GDB, e.g. trying to access guest memory when setting a convenience variable. Reprogramming the MPU to allow memory access where GDB expects it appears to do the trick for now. | 03 March 2019, 11:26:38 UTC |
| 493e4ae | alex@thinkpad | 03 March 2019, 10:47:21 UTC | GDB scripts: fixed CURRENT_ISR on A1100 | 03 March 2019, 10:47:21 UTC |
| cc87e4e | alex@thinkpad | 03 March 2019, 10:47:21 UTC | QEMU: defined CURRENT_ISR on VxWorks models (5D, 40D, 400D, 450D, 1000D) The interrupt ID is only stored the stack, but the address appears to be repeatable for the first nesting level. Better than nothing. | 03 March 2019, 10:47:21 UTC |
| 9690f88 | alex@thinkpad | 03 March 2019, 10:47:21 UTC | QEMU: fixed CURRENT_TASK for 5D (both GDB script and model_list.c) | 03 March 2019, 10:47:21 UTC |
| bf93ccf | alex@thinkpad | 03 March 2019, 08:07:42 UTC | QEMU: updated CURRENT_ISR for EOS M5; workaround for current_task_addr | 03 March 2019, 08:07:42 UTC |
| e7516d7 | alex@thinkpad | 03 March 2019, 07:47:01 UTC | GDB scripts: updated formatting of CURRENT_ISR on 200D, 800D, 77D, 6D2, 750D (non-functional) | 03 March 2019, 07:47:01 UTC |
| 543e4b4 | alex@thinkpad | 03 March 2019, 07:46:14 UTC | GDB scripts: updated CURRENT_ISR for 100D and 1300D to use the latest hypothesis (right before the interrupt ID, there is a counter telling whether we are running from interrupt or not, on all models so far) | 03 March 2019, 07:46:14 UTC |
| 443606c | alex@thinkpad | 03 March 2019, 07:20:58 UTC | MPU spells: fix possible buffer overflow when interpreting messages | 03 March 2019, 07:20:58 UTC |
