# Environment (DragonFly QEMU/KVM guest used for DF-5106 verification)

DragonFly dfbsd 6.5-DEVELOPMENT DragonFly 6.5-DEVELOPMENT #0: Thu Jul  2 06:02:54 UTC 2026     root@dfbsd:/usr/obj/usr/src/sys/X86_64_GENERIC  x86_64
kern.osrevision: 600519
hw.machine: x86_64
kernel config: X86_64_GENERIC

# source identity: guest /usr/src snapshot == audit target tree
sys/dev/sound/midi/midi.c   md5 d193653695588df8a8a24cf2ceeb1d31
sys/dev/sound/midi/mpu401.c md5 2df6971aa3d6d55cda2e157ddae13674

# hardware relevance
pciconf -l | grep -i emu   -> (empty)  NO emu10kx hardware in the QEMU guest
X86_64_GENERIC contains no 'device snd_emu10kx'
/boot/kernel contains snd_emu10kx.ko (module only; cannot attach without HW)
=> the real emu10kx-midi.c path cannot attach on this guest; verification was
   done at the framework level (mpu401/midi/newbus), which is hardware-
   independent, by a simulation module replicating the exact
   emu_midi_attach / emu_midi_detach call sequence (see simid.c header).

# build environment
cc (DragonFly base gcc/clang), in-tree kld build via bsd.kmod.mk
sound.ko + midi framework pulled in via MODULE_DEPEND(simid, sound, 5, 5, 5)