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
warren_ is now known as warren
alexfanqi has quit [Quit: leaving]
alexfanqi has joined #fedora-riscv
alexfanqi has quit [Quit: leaving]
alexfanqi has joined #fedora-riscv
alexfanqi has quit [Client Quit]
alexfanqi has joined #fedora-riscv
davidlt has joined #fedora-riscv
davidlt has quit [Remote host closed the connection]
jcajka has joined #fedora-riscv
jcajka has quit [Quit: Leaving]
zsun has joined #fedora-riscv
zsun has quit [Quit: Leaving.]
Guest12 has joined #fedora-riscv
Guest12 is now known as codedude
cyberpear has joined #fedora-riscv
codedude is now known as bryanz
<somlo> davidlt[m]: here's the final list of kernel config options that triggers a crash/panic on boot on LiteX/Rocket:
<somlo> CONFIG_PRINTK_INDEX=y
<somlo> CONFIG_FB_EFI=y
<somlo> CONFIG_DTPM_CPU=y
<somlo> CONFIG_IMA_KEXEC=y
<somlo> CONFIG_COMPAT_32BIT_TIME=y
<somlo> CONFIG_CRYPTO_ECDH=y
<somlo> CONFIG_FPROBE=y
<somlo> let me know which ones we're going to want to turn off (I've got CONFIG_COMPAT_32BIT_TIME so far, anything else we might want to disable)?
<somlo> my plan right now is to try these again with the latest linus upstream tree, then perhaps ask in #riscv if anyone knows why 1. the options might lead rocket to crash, and 2. if there are any pending patches in progress related to any of the options
<somlo> that is, before I start digging into any of them myself, which is a high-effort, high-learning-curve endeavor I'd rather avoid if I can :D
<somlo> what do you think?
cyberpear has quit [Quit: Connection closed for inactivity]