Friday, 2019-04-26

*** tpb has joined #litex00:00
futarisIRCcloudmithro: I did port the changes from qemu-litex to the main qemu tree (on my github). v3.1.0-litex branch. Input doesn't work (in LiteX bios) on lm32. It was fine in qemu-litex. Haven't tested linux on openrisc.02:03
futarisIRCcloud - is the same as the HEAD of timvideos/qemu-litex, and behaves the same.09:19
tpbTitle: GitHub - futaris/qemu at v3.0.50-litex (at
futarisIRCcloudI probably should rebase all the commits from qemu-litex repo onto qemu, but I'm lazy and just trying to get qemu vexriscv working.09:25
futarisIRCcloudmithro: What are the plans for patch-up at latch-up ( in the next 12-18 hours? )09:25
futarisIRCcloudSo the qemu-system built from that tree works fine with qemu-riscv32-virt:10:49
futarisIRCcloud./build/arty_net_vexriscv/qemu/riscv32-softmmu/qemu-system-riscv32 -M virt -nographic -kernel buildroot/buildroot/output/images/fw_jump.elf -device loader,file=buildroot/buildroot/output/images/Image,addr=0x80400000 -append "root=/dev/vda ro" -drive file=~/github/buildroot/buildroot/output/images/rootfs.ext2,format=raw,id=hd0 -device virtio-blk-device,drive=hd0 -netdev user,id=net0 -device virtio-net-device,netdev=net010:50
futarisIRCcloudJust need to create the litex machine, and do the SBI stuff.10:50
tpbTitle: GitHub - futaris/litex-buildenv at build-qemu-riscv (at
_florent_futarisIRCcloud: just for info, i'm working on getting linux working with vexriscv here:
tpbTitle: GitHub - enjoy-digital/litex-linux-vexriscv: Linux test with LiteX/VexRiscv (at
_florent_futarisIRCcloud: for now, i'm just reproducing the results from VexRiscv linux simulation in with litex_sim11:08
_florent_then i'll do the adaptations11:09
futarisIRCcloudOk. Thanks for the update. IIRC, they are using a FDT compiled into the kernel, much like openrisc does.11:31
_florent_futarisIRCcloud: not sure since i'm providing the .dtb ;à11:34
futarisIRCcloudQEMU has a bunch of functions that are supposed to be used to create the FDT, depending on the arguments to qemu. It means I should be able to replace the virt / sifive peripherals with litex peripherals one by one, and still have the kernel boot up, as long as it has the necessary drivers for each of them. :)11:59
*** _florent_ has quit IRC12:09
*** _florent_ has joined #litex12:11
mithrofutarisIRCcloud: patchup @ LatchUp is still a week away - I'm at KiCon today13:09
mithrofutarisIRCcloud: my plan around LiteX stuff in qemu was to allow you to specify the memory base address for the csrs + irqs13:10
mithrofutarisIRCcloud: if I recall correctly I have a qemu version with everything split out into individual branches13:12
*** _florent_ has quit IRC13:22
*** _florent__ has joined #litex13:22
mithrofutarisIRCcloud: forwarded you some emails I sent Joel13:35
tpbTitle: GitHub - mithro/litex-devicetree: Tool for generating Linux compatible DeviceTree from a LiteX csr.csv definition. (at
*** futarisIRCcloud has quit IRC14:09
*** futarisIRCcloud has joined #litex22:45

Generated by 2.13.1 by Marius Gedminas - find it at!