From: Stafford Horne <shorne@gmail.com>
To: Yann Sionneau <ysionneau@kalray.eu>
Cc: 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 21:45:00 +0900 [thread overview]
Message-ID: <20210225124500.GA365039@lianli.shorne-pla.net> (raw)
In-Reply-To: <7c538f1d-9cc4-c25c-0ccd-44831597c80e@kalray.eu>
Hello,
On Thu, Feb 25, 2021 at 08:17:41AM +0100, Yann Sionneau wrote:
> Hello,
>
> I am adding Stafford Horne in CC, as I think he might want to help about
> openrisc port :)
>
> Cheers
>
> Yann
>
> On 23/02/2021 10:59, Sascha Hauer wrote:
> > Hi Franck, Antony
> >
> > Are you still interested in barebox support for NIOS2 and openrisc? If
> > not I would consider removing it. Background is that we are planning to
> > introduce green threads and implement pollers with them which makes
> > green threads rather mandatory. Green threads need a setjmp/longjmp
> > implementation that would have to be added for these architectures.
> >
> > Keeping the architectures is no big deal normally, but I don't want to
> > add untested new functionality, also I don't want to implement things
> > that nobody uses, so if you are still interested it would be great if
> > you volunteer to implement setjmp/longjmp.
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.
-Stafford
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2021-02-25 12:46 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 [this message]
2021-02-25 13:02 ` Jules Maselbas
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=20210225124500.GA365039@lianli.shorne-pla.net \
--to=shorne@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=sha@pengutronix.de \
--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