On Tue, May 21, 2024 at 1:20 AM Jiaxun Yang <jiaxun.y...@flygoat.com> wrote: > 在2024年5月21日五月 上午8:35，Max Filippov写道： > >> +++ b/board/emulation/qemu-xtensa/MAINTAINERS > >> @@ -0,0 +1,7 @@ > >> +QEMU XTENSA 'VIRT' BOARD > >> +M: Jiaxun Yang <jiaxun.y...@flygoat.com> > >> +S: Maintained > >> +F: board/emulation/qemu-xtensa/ > >> +F: board/emulation/common/ > >> +F: include/configs/qemu-riscv.h > > > > This must be qemu-xtensa.h, right? > > Ah yes :-) > > Do you mind me to give you a M: entry?
Sure you can add me as a co-maintainer for this board. > > I'm not sure what CFG_SYS_IO_BASE means for the virt machine, but > > it looks like in the noMMU case SDRAM is going to overlap the > > IO range with the above base addresses and sizes. And from QEMU > > monitor I see the following address space distribution in the virt > > machine with a noMMU core: > > So CFG_SYS_IO_BASE means physical address left for I/O with 1:1 mapping > from virtual address. for PTP MMU I handled it in: > > [PATCH 03/10] xtensa: Implement phys virt conversion for PTP_MMU > > Can you confirm if noMMU core is doing the same on VA-PA mapping? So far all xtensa cores except those that have MMUv2 (like dc232b) come out of reset with identity mapping between virtual and physical addresses. -- Thanks. -- Max
