You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nuttx.apache.org by "g2gps (via GitHub)" <gi...@apache.org> on 2023/03/17 06:18:36 UTC
[GitHub] [nuttx] g2gps commented on pull request #8762: Support for Kernel build with vexriscv-smp.
g2gps commented on PR #8762:
URL: https://github.com/apache/nuttx/pull/8762#issuecomment-1473214005
@pussuw Thanks for the feedback and your port on nuttSBI. Admittedly, I had underestimated exactly what was required to get things working correctly.
I ended up finding and using the [Litex port of openSBI](https://github.com/litex-hub/opensbi/tree/0.8-linux-on-litex-vexriscv), which is the same used in the [Linux on Litex Vexriscv](https://github.com/litex-hub/linux-on-litex-vexriscv) project.
Currently, the port works, however I still need to integrate openSBI into the build system. There's a few ways I could do this:
1. Add it into the current `Make.defs` under `arch/risc-v/src/opensbi`. Keeping in mind that it would be pointing to a different repository.
2. Add something similar as (1) in `arch/risc-v/src/litex`.
3. Add instructions on where it it, and how to build it. Let the end-user go through this process.
The openSBI binary is currently loaded to gateware separately from the kernel, so I'm in favour of (3). However, I've can understand the desire to manage the build process as part of Nuttx. In that case, should the built openSBI binary just be placed in the root `nuttx` directory, along with the kernel?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org