qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
* [PATCH v1 0/2] Re: Drop ignore_memory_transaction_failures for xilink_zynq
@ 2024-09-26 17:04 Chao Liu
  2024-09-26 19:15 ` Peter Maydell
  0 siblings, 1 reply; 2+ messages in thread
From: Chao Liu @ 2024-09-26 17:04 UTC (permalink / raw)
  To: qemu-devel; +Cc: peter.maydell, bin.meng, edgar.iglesias, alistair

> The ignore_memory_transaction_failures is used for compatibility
> with legacy board models. 
> 
> I attempted to remove this property from the
> xilink_zynq board and replace it with unimplemented devices to 
> handle devices that are not implemented on the board.
> 
> Chao Liu (2):
>   xilink_zynq: Add various missing unimplemented devices
>   xilink-zynq-devcfg: Fix up for memory address range size not set
>     correctly
> 
>  hw/arm/xilinx_zynq.c      | 44 ++++++++++++++++++++++++++++++++++++++-
>  hw/dma/xlnx-zynq-devcfg.c |  2 +-
>  2 files changed, 44 insertions(+), 2 deletions(-)
> 
> -- 
> 2.46.1

Hello, maintainers,

Could you please provide any suggestions or feedback on the set of patches?
This is my first contribution to the QEMU community,
and it makes me feel very honored.

Additionally, I have used creat_unimplemented_device() to
add all the unimplemented devices on the Xilinx Zynq board,
primarily referencing the Zynq DTS, located at

roms/u-boot/arch/arm/dts/zynq-7000.dtsi.

You can verify whether all the board devices have been added correctly by
following these commands:

Step1:
./qemu/build/qemu-system-arm -M xilinx-zynq-a9 -display none -monitor stdio

Step2:
(qemu) info mtree

I am looking forward to your reply.

Regards,
Chao Liu



^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2024-09-26 19:16 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-09-26 17:04 [PATCH v1 0/2] Re: Drop ignore_memory_transaction_failures for xilink_zynq Chao Liu
2024-09-26 19:15 ` Peter Maydell

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).