Yocto Project Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>,
	Josef Holzmayr <jester@theyoctojester.info>
Cc: Yocto discussion list <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] are there any plans for a RISC-V reference board?
Date: Fri, 13 Oct 2023 13:33:33 +0100	[thread overview]
Message-ID: <2d442abb79e2d6311534a0f13855f05ef69a7e42.camel@linuxfoundation.org> (raw)
In-Reply-To: <943d42b1-8628-e247-77b1-692f5ada7d5f@crashcourse.ca>

On Fri, 2023-10-13 at 03:09 -0400, Robert P. J. Day wrote:
> On Tue, 10 Oct 2023, Josef Holzmayr wrote:
> > It has been discussed at numerous occasions. The main blocker is: we
> > need a commitment for the maintenance. So if a high-ranking member
> > decides to push forwards with this and allocate resources, or a new
> > member from the RISC-V ecosystem steps up to make it happen, then
> > the project is all ears.
> > 
> > Greetz,
> > Josef
> 
>    Ask and ye shall receive. I just got the following private note
> from jiaqi.dong@starfivetech.com, who obviously saw my earlier post
> (and agreed to let me reproduce his response to me to the list):
> 
> > I think VisionFive 2 is an appropriate reference board. We offer
> > Long Term Support for JH7110 and VisionFive 2. After being upgraded,
> > VisionFive 2 with big improvements in the processor work frequency,
> > multimedia processing capabilities, and scalability. Since August of
> > last year, we have continued to promote the ecosystem of VF2, it has
> > successively adapted to Deepin OS, Ubuntu OS, UEFI EDK2, OpenWrt,
> > PPSSPP…you can check out the RVspace forum. So we would like to work
> > with the developers and provide LTS if there are specific project
> > requirements.
> 
>   Sound promising?

The project has been talking to the RISC-V Foundation for a while about
this. The tricky part is that adding official support for a new
architecture isn't a cheap or easy undertaking for the project.

The autobuilder for example has hardware to pay for as well as
bandwidth and power costs. If we add a new architecture, the test
matrix is larger and the costs rise. There is also the increased human
load of more tests, more failures and more work to do.

Intel, AMD and ARM are platinum members and this partly allows for the
architecture support. MIPS and PowerPC are on the list for legacy
reasons and their testing scope is being scaled back.

We've discussed and agreed that adding a new architecture with all the
work it entails is at least around a platinum membership level of
impact for us. Therefore, to have official support of a new
architecture, we've asked that there be support either from existing
membership or new members of around that level.

When you look at the details of what you get, that price tag is
actually quite reasonable for the level of automated testing performed.

We've been clear about our position on this for a while. There are
actually discussions in progress about it with both the foundation and
RISE and I have some reasons to be optimistic but some of this has been
going back and forth for a number of years. FWIW, personally I would
love to see the support officially there and it in our test matrix.

Cheers,

Richard



      parent reply	other threads:[~2023-10-13 12:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-10  6:32 are there any plans for a RISC-V reference board? Robert P. J. Day
2023-10-10  6:49 ` [yocto] " Josef Holzmayr
2023-10-10  8:18   ` [yocto] VOLATILE_LOG_DIR ?= "no" gives build error Dave Hitchman
2023-10-13  7:09   ` [yocto] are there any plans for a RISC-V reference board? Robert P. J. Day
2023-10-13  9:35     ` Alexander Kanavin
2023-10-13  9:40       ` Robert P. J. Day
2023-10-13 12:33     ` Richard Purdie [this message]

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=2d442abb79e2d6311534a0f13855f05ef69a7e42.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=jester@theyoctojester.info \
    --cc=rpjday@crashcourse.ca \
    --cc=yocto@lists.yoctoproject.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