From: Richard Henderson <richard.henderson@linaro.org>
To: Keith Packard <keithp@keithp.com>, qemu-devel@nongnu.org
Cc: Laurent Vivier <laurent@vivier.eu>
Subject: Re: [PATCH 0/3] target/m68k: Fix a few semihosting bugs
Date: Tue, 3 Oct 2023 15:39:54 -0700 [thread overview]
Message-ID: <ec38df5b-9533-4ba2-a9d9-05514456b8bf@linaro.org> (raw)
In-Reply-To: <20230802161914.395443-1-keithp@keithp.com>
On 8/2/23 09:19, Keith Packard via wrote:
> The first two patches mirror similar patches I recently sent for nios2.
>
> 1. Use correct parameter for EXIT (d1 instead of d0)
> 2. Fix use of deposit64 in LSEEK (argument order was incorrect)
>
> The second patch has also been submitted by Peter Maydell, it's
> included here because it was required to get things working.
>
> The final patch adds semihosting support for non-ColdFire processors
> (which don't support the HALT instruction) by using BKPT #0 instead
> (as per the m68k semihosting docs).
>
> All of these have been tested using picolibc (patches for m68k support
> there are moving upstream as well).
Queued patch 1 to m68k-next. Patch 2 has already been committed, and I've just sent a
replacement for patch 3.
r~
PS: I hadn't noticed the picolibc note here at the time; I'll give that a try later today.
prev parent reply other threads:[~2023-10-03 22:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 16:19 [PATCH 0/3] target/m68k: Fix a few semihosting bugs Keith Packard via
2023-08-02 16:19 ` [PATCH 1/3] target/m68k: Pass semihosting arg to exit Keith Packard via
2023-08-03 10:07 ` Peter Maydell
2023-08-02 16:19 ` [PATCH 2/3] target/m68k: Fix semihost lseek offset computation Keith Packard via
2023-08-02 16:19 ` [PATCH 3/3] target/m68k: Support semihosting on non-ColdFire targets Keith Packard via
2023-08-03 10:45 ` Peter Maydell
2023-08-03 10:06 ` [PATCH 0/3] target/m68k: Fix a few semihosting bugs Peter Maydell
2023-10-03 22:39 ` Richard Henderson [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=ec38df5b-9533-4ba2-a9d9-05514456b8bf@linaro.org \
--to=richard.henderson@linaro.org \
--cc=keithp@keithp.com \
--cc=laurent@vivier.eu \
--cc=qemu-devel@nongnu.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 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).