93c640f005
Keep arm_nuri on 3.10.x for the usual reasons. Keep mips & mipsel (32 bits) on 4.3.x because 4.4.x fails to boot properly (kernel stuck after the CPU cache info). Results table: Defconfig Kernel Qemu Network Status -------------------------------------------------------------- aarch64_virt 4.4.1 2.3.0 YES OK arm_nuri 3.10.96 2.3.0 YES(1) OK most times(2) arm_versatile 4.4.1 2.3.0 YES OK arm_vexpress 4.4.1 2.3.0 YES OK microblazebe 4.4.1 2.3.0 YES OK microblazeel 4.4.1 2.3.0 YES OK mips64el_malta 4.4.1 2.3.0 YES OK mips64_malta 4.4.1 2.3.0 YES OK mipsel_malta 4.3.5 2.3.0 YES OK (4) mips_malta 4.3.5 2.3.0 YES OK (4) ppc_g3beige 4.4.1 2.3.0 YES OK ppc_mpc8544ds 4.4.1 2.3.0 YES OK ppc_virtex_ml507 4.4.1 2.3.0 NO OK ppc64_pseries 4.4.1 2.3.0 YES OK sh4 4.4.1 2.3.0 YES OK sh4eb 4.4.1 2.3.0 NO(3) OK sparc_ss10 4.4.1 2.3.0 YES OK sparc64_sun4u 4.4.1 2.3.0 YES OK sparc_sun4u 4.4.1 2.3.0 YES OK x86 4.4.1 2.3.0 YES OK x86_64 4.4.1 2.3.0 YES OK xtensa_lx60 4.4.1 2.3.0 YES OK (1) - Supposed to work but broken, probably Qemu emulation issue (2) - In like 1/3 starts it fails to work properly (3) - Probably an endian issue with 8139 emulation/driver (4) - Kernel stuck at cpu cache details from 4.4 - 4.4.1 Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> |
||
---|---|---|
.. | ||
linux-4.4.config | ||
readme.txt |
Run the emulation with: qemu-system-ppc -M virtex-ml507 -kernel output/images/vmlinux -m 256 -nographic -append "console=ttyS0" -dtb output/images/virtex440-ml507.dtb The login prompt will appear in the terminal that started Qemu. Tested with QEMU 2.3.0