On 5/3/22 15:17, Mark Cave-Ayland wrote:
On 24/02/2022 14:04, Philippe Mathieu-Daudé wrote:
On 24/2/22 12:59, Mark Cave-Ayland wrote:
This helps to follow how the guest is programming the mos6522 when
debugging.
Signed-off-by: Mark Cave-Ayland
Reviewed-by: Peter Maydell
---
On 24/02/2022 14:04, Philippe Mathieu-Daudé wrote:
On 24/2/22 12:59, Mark Cave-Ayland wrote:
This helps to follow how the guest is programming the mos6522 when debugging.
Signed-off-by: Mark Cave-Ayland
Reviewed-by: Peter Maydell
---
hw/misc/mos6522.c | 10 --
Le 24/02/2022 à 12:59, Mark Cave-Ayland a écrit :
This helps to follow how the guest is programming the mos6522 when debugging.
Signed-off-by: Mark Cave-Ayland
Reviewed-by: Peter Maydell
---
hw/misc/mos6522.c| 10 --
hw/misc/trace-events | 4 ++--
2 files changed, 10
On 24/2/22 12:59, Mark Cave-Ayland wrote:
This helps to follow how the guest is programming the mos6522 when debugging.
Signed-off-by: Mark Cave-Ayland
Reviewed-by: Peter Maydell
---
hw/misc/mos6522.c| 10 --
hw/misc/trace-events | 4 ++--
2 files changed, 10 insertions(+), 4
This helps to follow how the guest is programming the mos6522 when debugging.
Signed-off-by: Mark Cave-Ayland
Reviewed-by: Peter Maydell
---
hw/misc/mos6522.c| 10 --
hw/misc/trace-events | 4 ++--
2 files changed, 10 insertions(+), 4 deletions(-)
diff --git a/hw/misc/mos6522.c
