![](https://seccdn.libravatar.org/avatar/d08c8785b44c2e795ebed85a2afc7cc4.jpg?s=120&d=mm&r=g)
2018-01-24 19:43 GMT+03:00 Matwey V. Kornilov <matwey.kornilov@gmail.com>:
2018-01-24 16:38 GMT+03:00 Alexander Graf <agraf@suse.de>:
On 24.01.18 13:15, Matwey V. Kornilov wrote:
Hi,
There is one more thing that is unclear to me now. As far as I understand there is no other way except FDT to provide hardware layout for armv7l kernel. Then, who is responsible for FDT loading? As far as I understand it is grub2 task to load FDT from the table at b1b621d5-f19c-41a5-.... And FDT is completely provided by UEFI firmware. In case of u-boot, dtb file is loaded from the disk by means of u-boot and placed into memory. What should happen here when OVMF is used? In theory, it has to be configured to generate FDT from QEMU config somehow, right? Or pass-through entire FDT from Qemu hypervisor?
It basically passes through the device tree that's generated by QEMU, yes. However, OVMF defaults changed a while back and it only exposes ACPI tables instead of DT in newer versions on AArch64 IIRC.
Maybe something went wrong and they changed them for armv7 as well by accident?
I use latest version of aarch32 OVMF firmware from openSUSE:Factory:ARM. Well, then, I suppose, I have to see appropriate EFI driver (FdtClientDxe ? ) in the driver list.
Shell> drivers T D D Y C I R P F A V VERSION E G G #D #C DRIVER NAME IMAGE NAME == ======== = = = == == =================================== ========== 6B 0000000A D - - 1 - Platform Console Management Driver ConPlatformDxe 6C 0000000A D - - 1 - Platform Console Management Driver ConPlatformDxe 6D 0000000A B - - 1 1 Console Splitter Driver ConSplitterDxe 6E 0000000A ? - - - - Console Splitter Driver ConSplitterDxe 6F 0000000A ? - - - - Console Splitter Driver ConSplitterDxe 70 0000000A B - - 1 1 Console Splitter Driver ConSplitterDxe 71 0000000A B - - 1 1 Console Splitter Driver ConSplitterDxe 75 0000000A ? - - - - Graphics Console Driver GraphicsConsoleDxe 76 0000000A B - - 1 1 Serial Terminal Driver TerminalDxe 77 0000000A D - - 1 - Generic Disk I/O Driver DiskIoDxe 78 0000000B ? - - - - Partition Driver(MBR/GPT/El Torito) PartitionDxe 79 0000000A ? - - - - FAT File System Driver Fat 7C 00000010 ? - - - - UDF File System Driver UdfDxe 7D 00000010 ? - - - - Virtio Block Driver VirtioBlkDxe 7E 00000010 B - - 1 1 Virtio Network Driver VirtioNetDxe 7F 00000010 ? - - - - Virtio SCSI Host Driver VirtioScsiDxe 80 00000010 ? - - - - Virtio Random Number Generator Driv VirtioRngDxe 81 0000000A B - - 1 1 ARP Network Service Driver ArpDxe 82 0000000A B - - 1 1 DHCP Protocol Driver Dhcp4Dxe 83 0000000A B - - 2 10 IP4 Network Service Driver Ip4Dxe 84 0000000A B - - 1 2 MNP Network Service Driver MnpDxe 85 0000000A B - - 1 1 VLAN Configuration Driver VlanConfigDxe 86 0000000A B - - 2 2 MTFTP4 Network Service Mtftp4Dxe 87 0000000A B - - 2 2 Tcp Network Service Driver Tcp4Dxe 88 0000000A B - - 6 10 UDP Network Service Driver Udp4Dxe 89 0000000A D - - 6 - UEFI PXE Base Code Driver UefiPxe4BcDxe 8A 0000000A D - - 1 - iSCSI Driver IScsi4Dxe 8C 0000000A ? - - - - SCSI Bus Driver ScsiBus 8D 0000000A ? - - - - Scsi Disk Driver ScsiDisk 8E 0000000A B - - 1 2 PCI Bus Driver PciBusDxe 90 00000010 D - - 1 - Virtio PCI Driver VirtioPciDeviceDxe 91 00000010 ? - - - - Virtio 1.0 PCI Driver Virtio10 92 00000010 ? - - - - Virtio GPU Driver VirtioGpuDxe 93 00000020 ? - - - - Usb Uhci Driver UhciDxe 94 00000030 ? - - - - Usb Ehci Driver EhciDxe 95 00000030 ? - - - - Usb Xhci Driver XhciDxe 96 0000000A ? - - - - Usb Bus Driver UsbBusDxe 97 0000000A ? - - - - Usb Keyboard Driver UsbKbDxe 98 00000011 ? - - - - Usb Mass Storage Driver UsbMassStorageDxe
Linaro's image has the same behavior. -- With best regards, Matwey V. Kornilov -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org