dgilmore changed the topic of #fedora-riscv to: Fedora on RISC-V https://fedoraproject.org/wiki/Architectures/RISC-V || Logs: https://libera.irclog.whitequark.org/fedora-riscv || Alt Arch discussions are welcome in #fedora-alt-arches
cyberpear has joined #fedora-riscv
zsun has joined #fedora-riscv
esv has joined #fedora-riscv
cyberpear has quit [Quit: Connection closed for inactivity]
zsun has quit [Quit: Leaving.]
davidlt has joined #fedora-riscv
<davidlt[m]> I haven't touched Scala for years, but I loved it compared to Java. Yet it runs (or used to run?) on the same JVM.
<dtometzki> good morning does anyone knows how i can run opensbi & u-boot from visonfive in Qemu
<dtometzki> * in Qemu ?
<davidlt[m]> There is no machine that would emulate VF2 in QEMU.
<dtometzki> yes that is what i found out
<dtometzki> * found out. I thought maybe there is another way
jcajka has joined #fedora-riscv
<davidlt[m]> I missed something interesting.
<davidlt[m]> SiFive FU800 :)
<davidlt[m]> That showed up in the some kernel crash reports on kernel mailing list.
zsun has joined #fedora-riscv
rwmjones has quit [Ping timeout: 252 seconds]
rwmjones has joined #fedora-riscv
zsun has quit [Quit: Leaving.]
davidlt has quit [Ping timeout: 260 seconds]
zsun has joined #fedora-riscv
<dtometzki> davidlt: do have a setup with qemu and machine sifive_u where it run?
davidlt has joined #fedora-riscv
<davidlt[m]> I never use sifive_u machine. Technically it should be able too boo the same binaries as Unmatched IIRC.
<davidlt[m]> It represents Unleashed or Unmatched board, don't recall exactly.
<cwt[m]> Is there any way to check extensions usage in a compiled binary file?
<davidlt[m]> There might be some bits in ELF header, but otherwise capstone and analyse instructions.
<davidlt[m]> Ah, no only C is marked in the header.
<davidlt[m]> There is also Tag_RISCV_arch
<davidlt[m]> Tag_RISCV_arch, 5, NTBS=subarch
<davidlt[m]> Tag_RISCV_arch should be recorded in lowercase, and all extensions should be separated by underline(_).
<davidlt[m]> Tag_RISCV_arch contains a string for the target architecture taken from the option -march. Different architectures will be integrated into a superset when object files are merged.
<cwt[m]> hmm, it will be recorded in the header of any binary file?
<davidlt[m]> Should be if the toolchain follows psABI.
masami has joined #fedora-riscv
zsun has quit [Quit: Leaving.]
<cwt[m]> Just test it with a simple C file that do nothing. the Tag_RISCV_arch is what we pust on -march, not the instructions in the binary.
<davidlt[m]> Yeah, so the toolchain is OK to generate any of those instructions. Yet it might not do that for multiple reasons.
<davidlt[m]> If you want to be exact you will need to do binary analysis.
<cwt[m]> ah ok, will try to do it tomorrow.
masami has quit [Quit: Leaving]
jcajka has quit [Quit: Leaving]
davidlt has quit [Ping timeout: 248 seconds]
tg has quit [Ping timeout: 260 seconds]
tg has joined #fedora-riscv
tg has quit [Ping timeout: 260 seconds]
tg has joined #fedora-riscv
<somlo> davidlt[m]: `CONFIG_COMPAT_32BIT_TIME=y` is the second option that when enabled, causes the kernel to crash on Litex/Rocket