Re: [Qemu-devel] boot arm fedora via u-boot in qemu

[Gerd Hoffmann <kraxel@redhat.com>]

  Hi,

> Retrieving file: /dtb-3.16.0-0.rc7.git1.1.fc22.armv7hl/sun7i-a20-bananapi.dtb
> 22335 bytes read in 2312 ms (8.8 KiB/s)
> Kernel image @ 0x42000000 [ 0x000000 - 0x5a8640 ]
> ## Flattened Device Tree blob at 43000000
>    Booting using the fdt blob at 0x43000000
>    Loading Ramdisk to 4e3d8000, end 4ffff039 ... OK
>    Loading Device Tree to 4e3cf000, end 4e3d773e ... OK
> 
> Starting kernel ...
> 
> [    0.000000] Booting Linux on physical CPU 0x0
> [    0.000000] Initializing cgroup subsys cpuset
> [    0.000000] Initializing cgroup subsys cpu
> [    0.000000] Initializing cgroup subsys cpuacct
> [    0.000000] Linux version 3.16.0-0.rc7.git1.1.fc22.armv7hl (mockbuild@arm02-builder06.arm.fedoraproject.org) (gcc version 4.9.1 20140717 (Red Hat 4.9.1-2) (GCC) ) #1 SMP Tue Jul 29 17:20:28 UTC 2014
> 
> Note how it is also actually reading the dtb from disk, where as in your case
> it is not, so that seems to be the culprit.

If I don't pass the dtb to qemu u-boot will actually load it from disk,
looks like this:

U-Boot 2014.10-rc3-00276-g30fa548 (Oct 21 2014 - 18:56:38)

DRAM:  1 GiB
WARNING: Caches not enabled
Flash: 128 MiB
MMC:   MMC: 0
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
QEMU: will try to load vexpress-v2p-ca9.dtb from disk.
Net:   smc911x-0
Warning: smc911x-0 using MAC address from net device

Warning: Your board does not use generic board. Please read
doc/README.generic-board and take action. Boards not
upgraded by the late 2014 may break or be removed.
Hit any key to stop autoboot:  0 
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
528 bytes read in 34 ms (14.6 KiB/s)
Ignoring unknown command: ui
Ignoring malformed menu command:  autoboot
Ignoring malformed menu command:  hidden
Ignoring unknown command: totaltimeout
Fedora-Minimal-armhfp-21-20140905 Boot Options.
1:      Fedora-Minimal-armhfp-21-20140905 (3.16.1-301.fc21.armv7hl)
Enter choice: 1
1:      Fedora-Minimal-armhfp-21-20140905 (3.16.1-301.fc21.armv7hl)
Retrieving file: /initramfs-3.16.1-301.fc21.armv7hl.img
29202689 bytes read in 3854 ms (7.2 MiB/s)
Retrieving file: /vmlinuz-3.16.1-301.fc21.armv7hl
5460688 bytes read in 793 ms (6.6 MiB/s)
append: ro root=UUID=55c3c475-37c8-41f8-ac34-3c153cde02a2
console=ttyAMA0,115200n8 earlyprintk
Retrieving file: /dtb-3.16.1-301.fc21.armv7hl/vexpress-v2p-ca9.dtb
12941 bytes read in 771 ms (15.6 KiB/s)
Kernel image @ 0x80008000 [ 0x000000 - 0x5352d0 ]
## Flattened Device Tree blob at 87f00000
   Booting using the fdt blob at 0x87f00000
   Loading Ramdisk to 7e307000, end 7fee0901 ... OK
   Loading Device Tree to 7e300000, end 7e30628c ... OK

Starting kernel ...

Still not working.

I think when loading it from disk the dtb lacks the virtio-mmio nodes
which qemu will add to the dtb, so virtio devices will not work.
Shouldn't make much of a difference though when booting from sdcard.

cheers,
  Gerd