1 files changed, 59 insertions, 0 deletions
diff --git a/results/classifier/118/none/1404610 b/results/classifier/118/none/1404610
new file mode 100644
index 000000000..28d47b645
--- /dev/null
+++ b/results/classifier/118/none/1404610
@@ -0,0 +1,59 @@
+architecture: 0.690
+device: 0.625
+semantic: 0.618
+boot: 0.599
+mistranslation: 0.589
+network: 0.523
+permissions: 0.516
+performance: 0.457
+vnc: 0.419
+risc-v: 0.409
+peripherals: 0.403
+files: 0.395
+ppc: 0.370
+VMM: 0.366
+socket: 0.359
+graphic: 0.319
+user-level: 0.312
+hypervisor: 0.310
+arm: 0.303
+TCG: 0.295
+PID: 0.289
+kernel: 0.277
+x86: 0.265
+virtual: 0.265
+i386: 0.261
+debug: 0.229
+register: 0.221
+KVM: 0.135
+assembly: 0.022
+
+[feature request] HP300 m68k system?
+
+QEMU seems to support nothing (specific) that 4.4BSD was targeted to...would be useful to have a complete emulator for a full HP300 to run the binary dist from McKusick's CD set.
+
+Devices that'd be needed: 
+* 68020, 68030, or 68040 (How much of these are already present? Not sure if there was a non-standard MMU/FPU...but there was definitely a slightly-uncommon bus used for some peripherals)
+* Networking was lance I am pretty sure...at least the onboard one.
+* SCSI (Probably a standard chip as used EVERYWHERE ELSE..not sure off hand)
+* Framebuffers optional, serial is sufficient for basic booting of 4.4.
+
+Tape/disk can also be done via HP-IB...but SCSI would probably be easier unless extra peripherals were required (some serial stuff.)
+
+I'm not aware of anybody from the QEMU community working on emulating such 68k system ... so if you want support for that, you likely have to write the patches on your own... Anyway, you might want to have a look at Laurent Vivier's 68k tree - it features full 680x0 emulation (i.e. not only ColdFire) already: https://github.com/vivier/qemu-m68k
+
+I have Quadra 800 system emulation in the branch q800-v2.4.0.
+
+You can create a bootable disk image following this wiki:
+
+https://github.com/vivier/qemu-m68k/wiki
+
+But this is not fully functional: fork() doesn't work well...
+
+You can also find a working image from:
+
+http://landley.net/aboriginal/
+
+This image works better as it is based on busybox and uClibc
+(the fork() bug is triggered by the lazy symbol resolution mode of glibc)
+