From: Stafford Horne <shorne@gmail.com>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: Barebox <barebox@lists.infradead.org>,
Openrisc <openrisc@lists.librecores.org>
Subject: Re: [PATCH 0/4] OpenRISC fixes and setjmp/longjmp work
Date: Wed, 3 Mar 2021 23:12:14 +0900 [thread overview]
Message-ID: <20210303141214.GG365039@lianli.shorne-pla.net> (raw)
In-Reply-To: <57222afc-9d92-e52d-34d4-0737eff1ec82@pengutronix.de>
On Wed, Mar 03, 2021 at 03:03:11PM +0100, Ahmad Fatoum wrote:
> Hello Stafford,
>
> On 03.03.21 14:50, Stafford Horne wrote:
> > Hello,
> >
> > These are the patches I came up with to get the setjmp/longjmp routines to work
> > on OpenRISC. It seems to be working well.
> >
> > The patches are on github here:
> > https://github.com/stffrdhrn/barebox/tree/openrisc-bthread
> >
> > I had to revert a commit to remove openrisc to do this work, I hope that can be
> > reverted.
>
> Great. Thanks for taking the time!
> Could this be tested on qemu-system-or1k? If so, it would be great to have this
> documented in-tree, so future changes could be tested.
Sure, I will try to get it working. For some reason qemu was getting hung.
Give me a few days.
-Stafford
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2021-03-03 15:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 13:50 Stafford Horne
2021-03-03 13:50 ` [PATCH 1/4] openrisc: Use movhi to zero registers Stafford Horne
2021-03-03 13:50 ` [PATCH 2/4] openrisc: Add gitignore for dtb files Stafford Horne
2021-03-03 13:50 ` [PATCH 3/4] openrisc: Add linkage.h Stafford Horne
2021-03-03 13:50 ` [PATCH 4/4] openrisc: Implement setjmp/longjmp/initjmp Stafford Horne
2021-03-03 14:03 ` [PATCH 0/4] OpenRISC fixes and setjmp/longjmp work Ahmad Fatoum
2021-03-03 14:12 ` Stafford Horne [this message]
2021-03-03 20:25 ` Stafford Horne
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=20210303141214.GG365039@lianli.shorne-pla.net \
--to=shorne@gmail.com \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=openrisc@lists.librecores.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