1 files changed, 66 insertions, 0 deletions
diff --git a/results/classifier/118/graphic/1343 b/results/classifier/118/graphic/1343
new file mode 100644
index 00000000..4bcf8cb3
--- /dev/null
+++ b/results/classifier/118/graphic/1343
@@ -0,0 +1,66 @@
+architecture: 0.945
+graphic: 0.926
+device: 0.869
+kernel: 0.729
+files: 0.674
+peripherals: 0.662
+PID: 0.627
+permissions: 0.608
+ppc: 0.563
+debug: 0.531
+arm: 0.525
+performance: 0.516
+mistranslation: 0.508
+semantic: 0.505
+vnc: 0.489
+socket: 0.489
+risc-v: 0.457
+boot: 0.438
+register: 0.429
+VMM: 0.399
+user-level: 0.377
+TCG: 0.344
+network: 0.337
+hypervisor: 0.300
+assembly: 0.238
+virtual: 0.202
+x86: 0.157
+i386: 0.145
+KVM: 0.120
+
+qemu-system-riscv64: It cannot initialize ramfb video adapter
+Description of problem:
+It looks like ramfb video adapter doesn't work in riscv64 architecture. But it works fine in aarch64 architecture.
+Steps to reproduce:
+1. Launch the [attached kernel](/uploads/43282fa1bd6959472af4f99646b447b9/kernel) with command:
+```
+qemu-system-riscv64 -machine virt -kernel kernel -device ramfb -bios none -serial stdio
+```
+2. You will get the messages in console:
+```
+guest fw_cfg dma-interface enabled 
+setup ramfb successfull
+```
+3. Video adapter will not initialize. QEMU window will continue display this message:
+```
+Guest has not initialized the display (yet).
+```
+Additional information:
+There is a useful project for aarch64 architecture - https://github.com/luickk/qemu-ramfb-aarch64-driver. This is a Bare metal driver for ramfb adapter. It works fine. I adapted it for riscv64 architecture - https://github.com/CityAceE/qemu-ramfb-riscv64-driver. I've successfully went through all problems. Driver compiles now and launches. But unfortunately ramfb doesn't initialize. I parallel traced aarch64 and riscv64. They works equal until initialization. Aarch64 changes revolution just after qemu_cfg_write_entry call, but nothing happened after qemu_cfg_write_entry call in riscv64 emulation. I spent a lot of time trying to resolve this problem, but it looks like a problem in qemu-system-riscv64.
+
+**UPDATE**
+
+Tested with Windows builds of QEMU:
+
+v 6.1 - The same situation as Ubuntu build 6.2.
+
+v 7.1.92 - Stopped with message:
+```
+c:\Program Files\qemu\qemu-system-riscv64.exe: -device ramfb: ramfb device requires fw_cfg with DMA
+```
+
+P.S. v 7.1.92 - qemu-system-aarch64.exe with [aarch64 kernel build](/uploads/0df1d440163913c25a1505032672e1c5/kernel) works fine.
+
+**UPDATE2**
+
+[QEMU emulator version 7.0.0 (v7.0.0-11902-g1d935f4a02-dirty)](https://qemu.weilnetz.de/w64/2022/qemu-w64-setup-20220419.exe) is the last Windows build which opens my riscv64 kernel without message about requirement of fw_cfg with DMA. Next build "QEMU emulator version 7.0.90 (v7.1.0-rc0-11915-g5f9b281b8a-dirty)" already has this issue.