mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Jules Maselbas <jmaselbas@kalray.eu>, 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: Mon, 1 Mar 2021 12:05:35 +0100	[thread overview]
Message-ID: <36fa4f92-6f5d-d24c-988c-e85c207864bb@pengutronix.de> (raw)
In-Reply-To: <ba82e9ef-9d9a-179c-1688-a9aeb12413d3@pengutronix.de>

Hello,

On 25.02.21 16:33, Ahmad Fatoum wrote:

> On 25.02.21 14:02, Jules Maselbas wrote:
>> 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 
> 
> Great. Thanks. I'm preparing an updated version that will clean it up
> a bit, but the heart part of architectures providing setjmp/longjmp/initjmp
> will stay the same.
> 
> Small request:
>   If you implement initjmp, could you have it save into jmp_buf a frame
>   pointer value of NULL if applicable? That way, should backtrace be
>   implemented (or done via JTAG), they have a defined end.

Dismiss this last request. C code will just zero-initialize jmp_buf,
so initjmp needs only fill out return address and stack pointer. I just
sent out a series, which can be used to develop this one.

@Jules, any chance you could take over the kvx port? :-)

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox


  parent reply	other threads:[~2021-03-01 11:06 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
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 [this message]
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=36fa4f92-6f5d-d24c-988c-e85c207864bb@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=jmaselbas@kalray.eu \
    --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