From: Andreas Schwab <schwab@suse.de>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-devel@nongnu.org, "Laurent Vivier" <laurent@vivier.eu>
Subject: Re: [RFC PATCH] target/m68k: Use i128 for 128-bit load/store in m68k_copy_line()
Date: Mon, 30 Oct 2023 14:51:14 +0100 [thread overview]
Message-ID: <mvmbkcg6wx9.fsf@suse.de> (raw)
In-Reply-To: <8c85fc54-3933-4330-a378-c1b444b0771f@linaro.org> (Richard Henderson's message of "Tue, 17 Oct 2023 06:52:50 -0700")
On Okt 17 2023, Richard Henderson wrote:
> The manual says "burst reads and writes" without defining those terms.
Burst transfers are explained in the M68040UM (7.4.2 Line Read Transfer
and 7.4.4 Line Write Transfers).
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
prev parent reply other threads:[~2023-10-30 13:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 12:27 [RFC PATCH] target/m68k: Use i128 for 128-bit load/store in m68k_copy_line() Philippe Mathieu-Daudé
2023-10-17 13:44 ` Richard Henderson
2023-10-17 13:52 ` Richard Henderson
2023-10-30 13:51 ` Andreas Schwab [this message]
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=mvmbkcg6wx9.fsf@suse.de \
--to=schwab@suse.de \
--cc=laurent@vivier.eu \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
/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.