From: Jules Maselbas <jmaselbas@kalray.eu>
To: Stafford Horne <shorne@gmail.com>
Cc: Yann Sionneau <ysionneau@kalray.eu>,
Barebox List <barebox@lists.infradead.org>,
Sascha Hauer <sha@pengutronix.de>,
shorne@opencores.org
Subject: Re: nios2 and openrisc in barebox
Date: Thu, 25 Feb 2021 14:02:40 +0100 [thread overview]
Message-ID: <20210225130240.GA5081@tellis.lin.mbt.kalray.eu> (raw)
In-Reply-To: <20210225124500.GA365039@lianli.shorne-pla.net>
On Thu, Feb 25, 2021 at 09:45:00PM +0900, Stafford Horne wrote:
> Hello,
>
> I am the maintainer of most OpenRISC things right now. I would be happy to
> help, but I don't really use barebox right now. Most of my deployments I use
> with litex FPGA SoC's that has its own bootloader.
>
> That said, we have a setjmp/longjmp implementation in our glibc port which I
> have been testing for upstreaming lately.
>
> https://github.com/stffrdhrn/or1k-glibc/blob/or1k-port-2/sysdeps/or1k/setjmp.S
> https://github.com/stffrdhrn/or1k-glibc/blob/or1k-port-2/sysdeps/or1k/__longjmp.S
>
> I had a look at the barebox docs and openrisc port, it seems like there is
> support for our standard platform, or1ksim, which is the same as my de0-nano
> fpga board/soc and qemu. I should be able to make use of this.
>
> Is there a branch where you are doing the green thread work? I could add and
> test the OpenRISC implementation.
Hi,
I've done this yesterday, I've push a branch[1] that has the green
thread paches applied (except patches on usb mass storage gadget).
https://github.com/jmaselbas/barebox/tree/test_setjmp
To test greenthread your can run the `poller -c` command in barebox's
prompt. To do you you'll need to enable CONFIG_POLLER_YIELD and define
CONFIG_HAS_ARCH_SJLJ
Best,
Jules
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2021-02-25 13:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 9:59 Sascha Hauer
2021-02-23 13:13 ` Franck Jullien
2021-02-24 7:06 ` Antony Pavlov
2021-02-24 8:44 ` Sascha Hauer
2021-02-25 7:17 ` Yann Sionneau
2021-02-25 12:45 ` Stafford Horne
2021-02-25 13:02 ` Jules Maselbas [this message]
2021-02-25 15:33 ` Ahmad Fatoum
2021-02-25 17:39 ` Antony Pavlov
2021-02-25 21:12 ` Stafford Horne
2021-03-01 11:05 ` Ahmad Fatoum
2021-03-01 11:17 ` Jules Maselbas
2021-03-01 12:18 ` 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=20210225130240.GA5081@tellis.lin.mbt.kalray.eu \
--to=jmaselbas@kalray.eu \
--cc=barebox@lists.infradead.org \
--cc=sha@pengutronix.de \
--cc=shorne@gmail.com \
--cc=shorne@opencores.org \
--cc=ysionneau@kalray.eu \
/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