Saturday, 2022-05-21

*** tpb <[email protected]> has joined #litex00:00
*** Emantor <[email protected]> has quit IRC (Quit: ZNC - http://znc.in)01:20
*** Emantor <[email protected]> has joined #litex01:20
swetlandso I notice that you need to issue a dcache flush to vexriscv to avoid getting stale data from the liteeth packet sram sometimes03:19
swetlandisn't this sram in the IO memory area?  shouldn't it just *never* be cached?  vexriscv issue? litex issue? something else?03:20
*** Degi_ <[email protected]> has joined #litex03:44
*** Degi <[email protected]> has quit IRC (Ping timeout: 260 seconds)03:44
*** Degi_ is now known as Degi03:44
swetlandshenki: so, I think I have your liteeth peripheral bolted into my local qemu build but can't quite get it going...05:04
swetland$ /work/qemu/build/qemu-system-riscv32 -machine micro -bios out/boot.elf  -device liteeth,id=network0 -netdev tap,id=network0,ifname=qemu0,script=no,downscript=no05:04
swetlandqemu-system-riscv32: -device liteeth,id=network0: Parameter 'driver' expects a pluggable device type05:04
swetlandif I drop the -device portion I get:05:05
swetlandqemu-system-riscv32: warning: netdev network0 has no peer05:05
swetlandqemu-system-riscv32: warning: nic liteeth.0 has no peer05:05
*** Degi <[email protected]> has quit IRC (Quit: ZNC 1.7.5+deb4 - https://znc.in)05:14
*** Degi <[email protected]> has joined #litex05:17
swetlandokay  -nic tap,ifname=qemu0,script=no,downscript=no,mac=72:72:aa:bb:cc:dd  gets me closer.  multicast makes it through. pings do not (maybe a qemu limitation? but I thought tap mode was better for that?)06:51
swetlandah, correction, all inbound traffic looks good. outbound (qemu vm -> tun/tap) is not happy06:56
cr1901_florent_: Understood, thanks. Deleted those repos then :P. AFAICT, opentitan uses the ibex core06:58
swetlandah, the qemu model does not accept packets if reader events are disabled06:58
swetland$ ping6 fe80::7072:aaff:febb:ccdd%qemu007:00
swetlandPING fe80::7072:aaff:febb:ccdd%qemu0(fe80::7072:aaff:febb:ccdd%qemu0) 56 data bytes07:00
swetland64 bytes from fe80::7072:aaff:febb:ccdd%qemu0: icmp_seq=1 ttl=255 time=0.973 ms07:00
swetland64 bytes from fe80::7072:aaff:febb:ccdd%qemu0: icmp_seq=2 ttl=255 time=0.972 ms07:00
swetland64 bytes from fe80::7072:aaff:febb:ccdd%qemu0: icmp_seq=3 ttl=255 time=0.904 ms07:00
jevinskie[m]Congrats! Nice work!16:44
*** lexano <[email protected]> has quit IRC (Remote host closed the connection)17:26
swetlandwell, shenki did the hard work. I just had to figure out which of the five different sets of options for configuring network stuff in qemu to use ^^21:01
jevinskie[m]I tweeted back in January “Qemu args are a CTF from hell by themselves” ;-)21:20
swetlandahaha21:21
swetlandqemu reminds me of working on the linux kernel. there are N different APIs for everything and it's an adventure figuring out which ones are the correct/modern/bestsupported for whatever you're trying to do.  and THEN there are half a dozen ways to configure anything21:22
jevinskie[m]Hmm I wonder how difficult verilator cosimulation of a UTMI usb core would be. You’d have usb-ip speaking Linux USB request blocks and have to pack/unpack them into UTMI protocol. Would be super spiffy to have virtual usb devices with simulation!22:35
swetlandI bet setup/bulk/interrupt LS/FS wouldn't be too bad.  HS likely challenging, isoch maybe not practical23:23

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!