are there any plans for a RISC-V reference board?

are there any plans for a RISC-V reference board?

[Robert P. J. Day]

  at some point, will there be a poky (meta-yocto-bsp) RISC-V
reference board? i'm thinking the Nezha Allwinner D1 (which is
already supported in meta-riscv) would be a safe choice. or maybe the
more powerful VisionFive 2?

  thoughts?

rday

Re: [yocto] are there any plans for a RISC-V reference board?

[Josef Holzmayr]

[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]

Hi Robert,

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

On Tue, Oct 10, 2023 at 8:32 AM Robert P. J. Day <rpjday@crashcourse.ca>
wrote:

>
>   at some point, will there be a poky (meta-yocto-bsp) RISC-V
> reference board? i'm thinking the Nezha Allwinner D1 (which is
> already supported in meta-riscv) would be a safe choice. or maybe the
> more powerful VisionFive 2?
>
>   thoughts?
>
> rday
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> You automatically follow any topics you start or reply to.
> View/Reply Online (#61297):
> https://lists.yoctoproject.org/g/yocto/message/61297
> Mute This Topic: https://lists.yoctoproject.org/mt/101869785/4689568
> Group Owner: yocto+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [
> jester@theyoctojester.info]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>

[-- Attachment #2: Type: text/html, Size: 1957 bytes --]

Re: [yocto] VOLATILE_LOG_DIR ?= "no" gives build error

[Dave Hitchman]

[-- Attachment #1: Type: text/plain, Size: 1083 bytes --]



Hi all,
I was trying to get /var/lib and some files set up in my yocto build.
I read that setting VOLATILE_LOG_DIR ?= "no" would mean the directory I created during the bitbake would get copied over
However when I tried it I got...
| apt-pkg/tagfile-keys.cc:1:10: fatal error: /include/apt-pkg/tagfile-keys.h: No such file or directory
|     1 | #include "/include/apt-pkg/tagfile-keys.h"
|       |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| compilation terminated.
| ninja: build stopped: subcommand failed.
| WARNING: exit code 1 from a shell command.
| ERROR: Execution of '/home/dave/Documents/Kymati/yocto/build/tmp/work/cortexa53-crypto-phytec-linux/apt/2.2.2-r0/temp/run.do_install.277311' failed with exit code 1
ERROR: Task (/home/dave/Documents/Kymati/yocto/sources/poky/../poky/meta/recipes-devtools/apt/apt_2.2.2.bb:do_install) failed with exit code '1'

I didnt change anything else. I wonder if someone could confirm why this happens, and the best route to achieve the actual aim (the var lib directory created)

BR
and thanks for the help
Dave

[-- Attachment #2: Type: text/html, Size: 3390 bytes --]

Re: [yocto] are there any plans for a RISC-V reference board?

[Robert P. J. Day]

[-- Attachment #1: Type: text/plain, Size: 1185 bytes --]

On Tue, 10 Oct 2023, Josef Holzmayr wrote:

> Hi Robert,

> 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?

rday

Re: [yocto] are there any plans for a RISC-V reference board?

[Alexander Kanavin]

[-- Attachment #1: Type: text/plain, Size: 1823 bytes --]

Can you clarify please what LTS means here?

Alex

On Fri 13. Oct 2023 at 9.09, Robert P. J. Day <rpjday@crashcourse.ca> wrote:

> On Tue, 10 Oct 2023, Josef Holzmayr wrote:
>
> > Hi Robert,
>
> > 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?
>
> rday
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#61327):
> https://lists.yoctoproject.org/g/yocto/message/61327
> Mute This Topic: https://lists.yoctoproject.org/mt/101869785/1686489
> Group Owner: yocto+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [
> alex.kanavin@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>

[-- Attachment #2: Type: text/html, Size: 2821 bytes --]

Re: [yocto] are there any plans for a RISC-V reference board?

[Robert P. J. Day]

[-- Attachment #1: Type: text/plain, Size: 1693 bytes --]

On Fri, 13 Oct 2023, Alexander Kanavin wrote:

> Can you clarify please what LTS means here?
>
> Alex
>
> On Fri 13. Oct 2023 at 9.09, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
>       On Tue, 10 Oct 2023, Josef Holzmayr wrote:
>
>       > Hi Robert,
>
>       > 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.

  I don't know, this is just the email I got from someone at StarFive
who considered me the right contact person because I asked the
question in the first place.

rday

Re: [yocto] are there any plans for a RISC-V reference board?

[Richard Purdie]

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