06:45 <maquefel> Hi all, does any have USB gadget working on Lichee RV Allwinner D1 USB-C OTG or it just me ?

06:52 <davidlt[m]> maquefel: I don't, I don't even have D1 based board yet.

06:52 <maquefel> David Abdurachmanov is that you ?

06:53 <davidlt[m]> yes

06:53 <maquefel> Hi - it's Nikita Shubin

06:54 <davidlt[m]> Nice to see you here :)

06:54 <maquefel> same :)

06:54 <davidlt[m]> Btw, I pinged Anup on Unmatched WDT reset patchset last night, he will look into it soonish.

06:57 <maquefel> he already merged them onto master

06:58 <davidlt[m]> ah, cool, didn't check yet

06:59 <maquefel> but it looks like WD should be avoided - see similiar post on da9363 forum https://www.dialog-semiconductor.com/products/pmics?post_id=10052#tab-support_tab_content

07:00 <maquefel> any way it's EoL - so that's something unpleasant but really not fatal

07:06 <davidlt[m]> Yeah, I get impression that the drivers depend on OTP having AUTOBOOT set to ON.

07:06 <davidlt[m]> Sadly there is no way to change that.

07:11 <maquefel> Thats really not obvious from there datasheets...

22:12 <iooi> Happy and healthy new year to everyone!

22:13 <iooi> About a month ago I asked a question about using QEMU's virtio-vga for a graphical boot process, which never got answered, but accidentally killed all conversations in this channel.

22:13 <iooi> I am sorry for that!

22:14 <iooi> So maybe let me introduce myself first: I am a member of the GNUstep development team and want to help the GNUstep community to get GNUstep ported to RISC-V.

22:15 <iooi> A part of GNUstep, GNUstep-GUI has graphical user interface parts, which need a graphical representation on the screen. Hence I am asking on how to use QEMU's virtio-vga for that purpose.

22:15 <iooi> Using "real hardware" like SiFive's HiFive Unmatched is not an real option here, given the relativelly high price and short supply of this board.

22:16 <iooi> So the only viable option I see here would be to use QEMU and its virtio-vga for that purpose.

22:16 <iooi> I wonder if this already can be done.

22:17 <iooi> https://www.phoronix.com/scan.php?page=news_item&px=QEMU-6.1-Released says that support for QEMUs virtio-vga should be in place for RISC-V.

22:17 <iooi> So I tried using:

22:17 <iooi> MBP15:~ lars$ qemu-system-riscv64 -vga virtio -machine virt -smp 4 -m 2G -kernel /Volumes/Data/Projects/RISC-V/Fedora-Developer-Rawhide-20200108.n.0-fw_payload-uboot-qemu-virt-smode.elf -bios none -object rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-device,rng=rng0 -device virtio-blk-device,drive=hd0 -drive file=/Volumes/Data/Projects/RISC-V/Fedora-Developer-Rawhide-20200108.n.0-sda.raw,format=raw,id=hd0 -device

22:17 <iooi> virtio-net-device,netdev=usernet -netdev user,id=usernet,hostfwd=tcp::10000-:22

22:19 <iooi> to boot. Which worked in so far that I've got a successful boot. QEMU opened a console-like window for which I selected "View" > "serial0". This "console" showed all the messages of the boot process but nothing related to virtio-vga drivers or such. But then again Fedora-Developer-Rawhide-20200108 might already be to old for that.

22:19 <iooi> How would I proceed from here?

22:21 <iooi> One more thing: https://dl.fedoraproject.org/pub/alt/risc-v/repo/virt-builder-images/images/ seems to me to be a bit outdated. The instructions here https://fedoraproject.org/wiki/Architectures/RISC-V/Installing might be fine but require a redhat host to be executed. I am on a Mac, there is no "guestfish" for instance.

22:22 <iooi> Thanks again to everybody here for your great work on RISC-V support for Linux! You're doing a great job!