From: "Umar, Sayyad Mahammad" <contact@sayyadumar.com>
To: Richard Henderson <richard.henderson@linaro.org>, qemu-devel@nongnu.org
Cc: Yoshinori Sato <yoshinori.sato@nifty.com>,
Alistair Francis <alistair@alistair23.me>,
Peter Maydell <peter.maydell@linaro.org>,
Jason Wang <jasowangio@gmail.com>,
qemu-arm@nongnu.org
Subject: Re: [PATCH 0/2] target/rx: add RXv2/RXv3 CPU support
Date: Mon, 14 Sep 2026 00:27:26 +0200 [thread overview]
Message-ID: <7dcfa12f-50e5-4f98-a8b2-972ce2331499@sayyadumar.com> (raw)
In-Reply-To: <7e3a07b7-9ebe-42a2-8561-650ddcfe9026@linaro.org>
On 9/13/26 23:39, Richard Henderson wrote:
> On 9/13/26 08:21, Sayyad Mahammad Umar wrote:
>> This series extends the RX target with RXv2 and RXv3 CPU support,
>> forming the foundation for the RX65N, RX651, and RX72M machine models.
>>
>> The first patch adds the CPU definitions, instruction support, and
>> translator changes required by the newer RX cores.
>>
>> The second patch adds the initial RX machine and peripheral support.
>>
>> Signed-off-by: Sayyad Mahammad Umar <contact@sayyadumar.com>
>> ---
>> Sayyad Mahammad Umar (2):
>> target/rx: add RXv2 and RXv3 CPU support
>> hw/rx: add common RX peripherals
>>
>> MAINTAINERS | 20 +
>> hw/adc/renesas_s12ad.c | 324 +++++++++
>> hw/dma/renesas_rx_dmac.c | 317 +++++++++
>> hw/dma/renesas_rx_dtc.c | 169 +++++
>> hw/gpio/renesas_rx_gpio.c | 256 +++++++
>> hw/misc/renesas_rx_crc.c | 219 ++++++
>> hw/misc/renesas_rx_fcu.c | 985
>> ++++++++++++++++++++++++++
>> hw/misc/renesas_rx_romcache.c | 139 ++++
>> hw/misc/rx65n_sysclk.c | 190 +++++
>> hw/net/renesas_etherc.c | 955 +++++++++++++++++++++++++
>> hw/rtc/renesas_rx_rtc.c | 330 +++++++++
>> hw/ssi/renesas_rspi.c | 319 +++++++++
>> hw/timer/renesas_mtu3.c | 509 ++++++++++++++
>> hw/watchdog/renesas_rx_wdt.c | 193 ++++++
>> include/hw/adc/renesas_s12ad.h | 61 ++
>> include/hw/dma/renesas_rx_dmac.h | 57 ++
>> include/hw/dma/renesas_rx_dtc.h | 42 ++
>> include/hw/gpio/renesas_rx_gpio.h | 64 ++
>> include/hw/misc/renesas_rx_crc.h | 30 +
>> include/hw/misc/renesas_rx_fcu.h | 191 +++++
>> include/hw/misc/renesas_rx_romcache.h | 30 +
>> include/hw/misc/rx65n_sysclk.h | 37 +
>> include/hw/net/renesas_etherc.h | 109 +++
>> include/hw/rtc/renesas_rx_rtc.h | 52 ++
>> include/hw/ssi/renesas_rspi.h | 61 ++
>> include/hw/timer/renesas_mtu3.h | 73 ++
>> include/hw/watchdog/renesas_rx_wdt.h | 48 ++
>> target/rx/cpu-param.h | 3 +
>> target/rx/cpu-qom.h | 2 +
>> target/rx/cpu.c | 57 +-
>> target/rx/cpu.h | 124 ++++
>> target/rx/disas.c | 383 ++++++++++-
>> target/rx/gdbstub.c | 44 +-
>> target/rx/helper.c | 56 +-
>> target/rx/helper.h | 22 +
>> target/rx/insns.decode | 125 +++-
>> target/rx/meson.build | 6 +-
>> target/rx/op_helper.c | 357 ++++++++++
>> target/rx/translate.c | 1225
>> ++++++++++++++++++++++++++-------
>> 39 files changed, 7873 insertions(+), 311 deletions(-)
> With 7500+ new lines in two patches, no one is going to look at this.
> This patch set must be split into many many more patches. For example,
> one per new instruction, one per new device, one per logical change to
> existing code.
>
>
> r~
Hello Mr Henderson,
Thanks for the comment. You are right this patch is rather large. I will
split this into smaller patches and have another go at it.
Regards,
Umar
next prev parent reply other threads:[~2026-09-13 22:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-13 18:21 [PATCH 0/2] target/rx: add RXv2/RXv3 CPU support Sayyad Mahammad Umar
2026-09-13 18:21 ` [PATCH 1/2] target/rx: add RXv2 and RXv3 " Sayyad Mahammad Umar
2026-09-13 18:21 ` [PATCH 2/2] hw/rx: add common RX peripherals Sayyad Mahammad Umar
2026-09-13 21:39 ` [PATCH 0/2] target/rx: add RXv2/RXv3 CPU support Richard Henderson
2026-09-13 22:27 ` Umar, Sayyad Mahammad [this message]
2026-09-14 11:23 ` yoshinori.sato
2026-10-04 21:16 ` Umar, Sayyad Mahammad
2026-10-05 12:09 ` yoshinori.sato
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7dcfa12f-50e5-4f98-a8b2-972ce2331499@sayyadumar.com \
--to=contact@sayyadumar.com \
--cc=alistair@alistair23.me \
--cc=jasowangio@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=yoshinori.sato@nifty.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.