Skip to content

Conversation

@prashanthswami
Copy link
Contributor

We should ideally have at least one RISC-V board in our test group to limit future regression. Further work will have to be done to actually enable a toolchain that can build this test. The Starfive VisionFive V2 board was chosen here as an open-source board that has been referenced in the public issues.

Confirmed success of this mocked device test on a RISC-V QEMU instance.

@prashanthswami
Copy link
Contributor Author

For review: @malfet
CC: @GlassOfWhiskey - the riscv_hwprobe mock stuff should merge cleanly with your current PR, but the hwcap mock may conflict slightly. Need to also see if I should guard it with Linux 6.4 based on the discussion thread there.

We should ideally have at least one RISC-V board in our test group to
limit future regression. Further work will have to be done to actually
enable a toolchain that can build this test. The Starfive VisionFive V2
board was chosen here as an open-source board that has been referenced
in the public issues.

Confirmed success of this mocked device test on a RISC-V QEMU instance.
@prashanthswami prashanthswami force-pushed the add-starfive-visionfive branch from 0bb2786 to 2105209 Compare November 29, 2023 02:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants