V4.2 - Githubissues

openhwgroup / cva6-sdk

CVA6 SDK containing RISC-V tools and Buildroot

60 stars 65 forks source link

V4.2 #13

Closed zarubaf closed 5 years ago

zarubaf commented 5 years ago

Disable building newlib toolchain. We can compile everything using the glibc toolchain.
Enable FPU
Enable Xilinx SPI driver

zarubaf commented 5 years ago

I was wondering whether you can just take this image. If possible I'd prefer not to duplicate efforts here. What was the specific problem again?

msfschaffner commented 5 years ago

I think it was the lowRISC ethernet driver that broke the boot process...

It would be great if we had only one image though...

zarubaf commented 5 years ago

Can we check again with the new image and maybe kindly ask @jrrk for his help?

jrrk commented 5 years ago

Hi Florian, I prefer not to work with patch lists if it can be helped. You will recall open source according to the FSF means 'source in the most convenient form for modification' which of course a patch is not because it incorporates machine formatting which breaks if you change more than one line

zarubaf commented 5 years ago

I very much agree. What kind of options do we have to circumvent having to keep around patchsets?

jrrk commented 5 years ago

Buildroot supports the use of an external kernel. We can fork from https://github.com/torvalds/linux.git, v5.1-rc7 is the latest tag, we can apply our patches at this point (but with out any intention of upstreaming, because our hardware is constantly changing)

jrrk commented 5 years ago

I also think we should split LowRISC specific stuff and OpenPiton specific stuff from the ariane repository, and put it in an ariane-soc repository. Although it is convenient to have ariane-ethernet in the default build, it also means having to strip it out if it does not suit other uses.

zarubaf commented 5 years ago

We do have the device tree for deciding which module to load, right? If possible I'd prefer to not duplicate too much of the efforts between the two (and maybe in the future more) platforms.

jrrk commented 5 years ago

One Linux image is certainly possible, one BBL/opensbi sounds doable, one boot prom sounds compilcated, especially when you consider multiple boards.

zarubaf commented 5 years ago

Forking the linux kernel sounds good to me.

zarubaf commented 5 years ago

Yeah bootrom definetely needs to be system specifc.

jrrk commented 5 years ago

Latest kernel + lowrisc patches available here (not tested yet):

https://github.com/lowRISC/linux/tree/ariane-lowrisc-v0.7

zarubaf commented 5 years ago

I will integrate the lowrisc Linux in a separate PR. Thanks