From: Antony Pavlov <antonynpavlov@gmail.com>
To: Franck Jullien <franck.jullien@gmail.com>,
Sascha Hauer <sha@pengutronix.de>,
Barebox List <barebox@lists.infradead.org>
Subject: Re: nios2 and openrisc in barebox
Date: Wed, 24 Feb 2021 10:06:46 +0300 [thread overview]
Message-ID: <20210224100646.41d718b1801959a0b47e3f75@gmail.com> (raw)
In-Reply-To: <CAJfOKBx9dhJ2usck1NBv=VViTFHjSLzGjqiQoaSptp1oTPAW9g@mail.gmail.com>
On Tue, 23 Feb 2021 14:13:44 +0100
Franck Jullien <franck.jullien@gmail.com> wrote:
> Le mar. 23 févr. 2021 à 10:59, Sascha Hauer <sha@pengutronix.de> a écrit :
> >
> > 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.
> >
> > Thanks
> > Sascha
> >
>
> Hi,
>
> Thanks for asking.
>
> I don't think anyone is using (has ever used ?) Barebox on these architectures.
>
> I do have a product which uses Barebox and a NIOS2 in the field.
> It's working for 10+ years already but will never be updated.
>
> I think you can drop support for them. I won't work on this myself.
> Let's wait for Antony's view on this.
Hi!
I experimented with openrisc before widespread use of RISC-V.
I have never used nios2.
IMHO we can drop openrisc and nios2.
--
Best regards,
Antony Pavlov
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2021-02-24 7:08 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 [this message]
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
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=20210224100646.41d718b1801959a0b47e3f75@gmail.com \
--to=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=franck.jullien@gmail.com \
--cc=sha@pengutronix.de \
/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