Linaro-uefi

linaro-uefi@lists.linaro.org

811 discussions

linaro-edk2 2014.05

by Leif Lindholm

Hi all, I have set a new baseline at upstream commit 7447345a364e6aa5f5bd5219d25d28a2d6147bce. Due to upstream changes, linaro-platform-tc2 and linaro-platform-a9 failed to rebase cleanly - Ryan is looking into that. Since we now have all of the required support in the upstream Bds to boot properly, we are leaving out the linaro-topic-bds patched for this round. This will have an impact on validation. Also, linaro-topic-pxeboot is being put out to pasture since Olivier pushed the Ethernet driver last week. We may need to carry side patches for model platforms that use a different driver. I have pushed linaro-edk2-2014.05-a1, but we will be waiting for at least another alpha including the two mentioned platform topics. / Leif

11 years, 10 months

The GRUB multiboot support patch for aarch64(V3)

by Fu Wei

Hi Leif, I have make a multiboot support patch V3 following all your suggestion The main change are : (1)separate all the xen specific code to multiboot_xen.c and multiboot_xen.h (2)support for ramdisk and xsm (3)fully support http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/Multiboot and xen/docs/misc/arm/device-tree/booting.txt in Xen source code. (4)there is not limit in the module's number For the test log, please check : https://staging.validation.linaro.org/scheduler/job/46542/log_file I have tested it locally, it works fine for me. Please check the patch, and provide some suggestions. Thank you very much! -- Best regards, Fu Wei Enterprise Server Engineer From Red Hat LEG Team Linaro.org | Open source software for ARM SoCs Ph: +86 186 2020 4684 (mobile) IRC: fuwei Skype: tekkamanninja Room 1512, Regus One Corporate Avenue,Level 15, One Corporate Avenue,222 Hubin Road,Huangpu District, Shanghai,China 200021

11 years, 10 months

Re: [Linaro-uefi] PCI driver support on ARM64 platforms.

by Ganapatrao Kulkarni

Hi Olivier, thanks for the inputs. Yes agreed, it is specific to chipset/SoC not Architecture specific. thanks Ganapat On Thu, May 1, 2014 at 3:25 PM, Olivier Martin <olivier.martin(a)arm.com>wrote: > Hi Ganapat, > > > > You will need to implement the UEFI protocols: > > - EFI_PCI_HOST_BRIDGE_RESOURCE_ALLOCATION_PROTOCOL > > - EFI_PCI_ROOT_BRIDGE_IO_PROTOCOL > > > > Your driver will be more tied to your PCI Root Complex than the Aarch64 > architecture itself. > > > > PcAtChipsetPkg/PciHostBridgeDxe might be a good candidate to start with. > But again, your driver will be chipset specific, not architecture specific. > > > > Olivier > > > > *From:* Ganapatrao Kulkarni [mailto:gpkulkarni@gmail.com] > *Sent:* 01 May 2014 10:28 > *To:* linaro-uefi(a)lists.linaro.org; Olivier Martin > *Subject:* PCI driver support on ARM64 platforms. > > > > Hi All, > > We want to understand how to enable/add PCI support for ARM64 based > platforms in UEFI. > > Any suggestion on where to start from? which driver needs to be referred? > > Can we use PcAtChipsetPkg/PciHostBridgeDxe to start with? > > what are the changes required to port PcAtChipsetPkg/PciHostBridgeDxe to > support ARM64 platforms? > > I appreciate your advise on this! > > thanks in advance > > Ganapat > > >

11 years, 10 months

PCI driver support on ARM64 platforms.

by Ganapatrao Kulkarni

Hi All, We want to understand how to enable/add PCI support for ARM64 based platforms in UEFI. Any suggestion on where to start from? which driver needs to be referred? Can we use PcAtChipsetPkg/PciHostBridgeDxe to start with? what are the changes required to port PcAtChipsetPkg/PciHostBridgeDxe to support ARM64 platforms? I appreciate your advise on this! thanks in advance Ganapat

11 years, 10 months

The problem in Booting Kernel

by Xieguotao

Hi all, I have a problem,can you please help me out? We want boot zImage(zImage is comprised of EFI stub and Linux kernel) by Tftp in Bootmanager,but we found an error: D01 >exit unload symbols_only c:\uefi_linaro_workspace\binary_give\uefi-next-d95896d\Build \D01\DEBUG_RVCT\ARM\HisiPkg\D01BoardPkg\Application\Ebl\Ebl\DEBUG\Ebl.dll [1] Ramdisk - VenMsg(06ED4DD0-FF78-11D3-BDC4-00A0C94053D1,0000000000000000)/uImage - Initrd: VenMsg(06ED4DD0-FF78-11D3-BDC4-00A0C94053D1,0000000000000000)/ initrd - Arguments: mem=256M console=ttyAMA0,9600 - LoaderType: Linux kernel with ATAG data ----------------------- Global FDT Config - not configured ----------------------- [a] Boot Manager [b] EBL [c] GO Start: a [1] Add Boot Device Entry [2] Update Boot Device Entry [3] Remove Boot Device Entry [4] Update FDT path [5] Return to main menu Choice: 1 [1] (29 MB) - VenMsg(06ED4DD0-FF78-11D3-BDC4-00A0C94053D1,0000000000000000) [2] (978 MB) - Pci(0x0,0x0)/Sata(0x0,0x0,0x0)/HD(1,MBR,0x00000000,0x3F,0x1EA3FE) [3] (978 MB) - Pci(0x0,0x0)/Sata(0x0,0x0,0x0)/HD(2,MBR,0x00000000,0x1EA43D,0x1EA43D) [4] (978 MB) - Pci(0x0,0x0)/Sata(0x0,0x0,0x0)/HD(3,MBR,0x00000000,0x3D487A,0x1EA43D) [5] VenMsg(06ED4DD0-FF78-11D3-BDC4-00A0C94053D1,0000000000000000) - VenMsg(06ED4DD0-FF78-11D3-BDC4-00A0C94053D1,0000000000000000) [6] PXE on MAC Address: 0E:00:FF:0C:FF:FE - MAC(0E00FF0CFFFE,0x1) [7] TFTP on MAC Address: 0E:00:FF:0C:FF:FE - MAC(0E00FF0CFFFE,0x1) Select the Boot Device: 7 Get the IP address from DHCP: [y/n] y Get the TFTP server IP address: 192.168.10.100 File path of the EFI Application or the kernel : zImage Is an EFI Application? [y/n] y Is your application is an OS loader? [y/n] n Description for this new Entry: OS [1] Add Boot Device Entry [2] Update Boot Device Entry [3] Remove Boot Device Entry [4] Update FDT path [5] Return to main menu Choice: 5 [1] Ramdisk - VenMsg(06ED4DD0-FF78-11D3-BDC4-00A0C94053D1,0000000000000000)/uImage - Initrd: VenMsg(06ED4DD0-FF78-11D3-BDC4-00A0C94053D1,0000000000000000)/ initrd - Arguments: mem=256M console=ttyAMA0,9600 - LoaderType: Linux kernel with ATAG data [2] OS - MAC(0E00FF0CFFFE,0x1)/IPv4(192.168.10.100) - LoaderType: EFI Application ----------------------- Global FDT Config - not configured ----------------------- [a] Boot Manager [b] EBL [c] GO Start: 2 AllocatePoolPages: failed to allocate 322561 pages AllocatePool: failed to allocate 1321205792 bytes AllocatePoolPages: failed to allocate 322561 pages AllocatePool: failed to allocate 1321205792 bytes The error happened in BdsLoadImage-> BdsConnectDevicePath.Actually, Handle is no use in BdsTftpLoadImage,so I modify BdsLoadImage for test,then we can download zImage,but we still cannot boot it; (We can boot linux by Grub) Can you give me some advice?

11 years, 11 months

Re: [Linaro-uefi] how to compile a AARCH32 UEFI bin?

by TigerLiu＠via-alliance.com

Hi, Leif&&Olivier: Got it! Thanks for your reply! Best wishes,

11 years, 11 months

how to compile a AARCH32 UEFI bin?

by TigerLiu＠via-alliance.com

Hi, experts: I want to test booting an AARCH32 UEFI bin. I have downloaded a free licenced FVP model. I used ATF(Arm Trusted Firmware) to boot UEFI.bin . So, how to compile a AARCH32 UEFI bin? Could current UEFI code be compiled as a 32bit bin? Best wishes,

11 years, 11 months

grub-install and linaro-edk2 test report

by Fu Wei

Hi Leif, I have tested the linaro-edk2 and grub-install in latest leg image, report is below: For linaro-edk2(http://snapshots.linaro.org/components/kernel/linaro-edk2/12) Because this version of uefi need to work with Turstzone Firmware0.3, so we need to wrap it, can not test directly in LAVA. I wrap it locally, and upload to linaro for testing: http://people.linaro.org/~fu.wei/LAVA/test/UEFI/Bug-1281123/ Test: https://staging.validation.linaro.org/scheduler/job/46616 But in local test, I found some problems: (1)I can not execute the grub stored in /EFI/grub/grubaa64, but once I copy it to / or /EFI/BOOT/, that can be executed either by FS1:/EFI/grub/grubaa64.efi and EFI\BOOT\grubaa64.efi , the log is below: ------------------ Shell> FS1:/EFI/grub/grubaa64.efi 'FS1:/EFI/grub/grubaa64.efi' is not recognized as an internal or external command, operable program, or script file. Shell> FS1: FS1:\> ls EFI/grub/* 04/17/2014 14:43 <DIR> 2,048 . 04/17/2014 14:43 <DIR> 2,048 .. 04/17/2014 14:50 124,416 grubaa64.efi 1 File(s) 124,416 bytes grub 2 Dir(s)) 0 bytes FS1:\> EFI/grub/grubaa64.efi 'EFI/grub/grubaa64.efi' is not recognized as an internal or external command, operable program, or script file. FS1:\> cp EFI/grub/grubaa64.efi EFI/BOOT/ Copying FS1:\EFI\grub\grubaa64.efi -> FS1:\EFI\BOOT\grubaa64.efi - [ok] FS1:\> EFI\BOOT\grubaa64.efi Welcome to GRUB! GNU GRUB version 2.02~beta2 Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions. grub> exit FS1:\> FS1:\EFI\grub\grubaa64.efi Welcome to GRUB! GNU GRUB version 2.02~beta2 Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions. grub> exit FS1:\> EFI/grub/grubaa64.efi 'EFI/grub/grubaa64.efi' is not recognized as an internal or external command, operable program, or script file. FS1:\> rm EFI/BOOT/grubaa64.efi Deleting 'FS1:\EFI\BOOT\grubaa64.efi' Delete successful FS1:\> FS1:\EFI\grub\grubaa64.efi Welcome to GRUB! GNU GRUB version 2.02~beta2 Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions. grub> exit FS1:\> grubaa64.efi 'grubaa64.efi' is not recognized as an internal or external command, operable program, or script file. FS1:\> grubaa64 'grubaa64' is not recognized as an internal or external command, operable program, or script file. FS1:\> FS1:\EFI\grub\grubaa64.efi Welcome to GRUB! GNU GRUB version 2.02~beta2 Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions. grub> exit FS1:\> cp EFI/grub/grubaa64.efi . Copying FS1:\EFI\grub\grubaa64.efi -> FS1:\grubaa64.efi - [ok] FS1:\> grubaa64.efi Welcome to GRUB! GNU GRUB version 2.02~beta2 Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions. grub> ------------------ *Is that the normal behavior???* (2)Got "Synchronous Exception:", once I exit from uefi shell and reenter the shell, the log is below: ------------------ FS1:\> exit [1] Linaro disk image on virtio - VenHw(C5B9C74A-6D72-4719-99AB-C59F199091EB)/Image - Arguments: console=ttyAMA0 earlyprintk=pl011,0x1c090000 debug user_debug=31 loglevel=9 root=/dev/vda2 - FDT: VenHw(C5B9C74A-6D72-4719-99AB-C59F199091EB)/fvp-base-gicv2-psci.dtb - LoaderType: Linux kernel with Local FDT [2] pxe - MAC(201201041000,0x1) - LoaderType: EFI Application ----------------------- Global FDT Config - VenHw(C5B9C74A-6D72-4719-99AB-C59F199091EB)/fdt.dtb ----------------------- [a] Boot Manager [b] Shell [c] Reboot [d] Shutdown Start: b Synchronous Exception: Synchronous Exception: ...... ------------------ (3)grub did not get the config file in /grub/grub.cfg Test log: https://staging.validation.linaro.org/scheduler/job/46613/log_file#L_131_0 https://staging.validation.linaro.org/scheduler/job/46613/log_file#L_155_2 Could you help me, Thanks! -- Best regards, Fu Wei Enterprise Server Engineer From Red Hat LEG Team Linaro.org | Open source software for ARM SoCs Ph: +86 186 2020 4684 (mobile) IRC: fuwei Skype: tekkamanninja Room 1512, Regus One Corporate Avenue,Level 15, One Corporate Avenue,222 Hubin Road,Huangpu District, Shanghai,China 200021

11 years, 11 months

[inputs required]: build system improvement

by Sam Protsenko

Hi guys, There was some complaints about shortcomings of EDK2 build system, like "make clean" doesn't work correct, dependency checking is lame, etc. It would be really great to collect here all inputs with explanations (or steps how to reproduce). So if you happened to notice that something is wrong with EDK2 build system -- please provide this information here. I also don't really understand what is wrong with clean scripts and dependency checking (just heard complaints without explanations), so if you know any details -- please provide it here as well. Once I have enough inputs I will solicit feedback from the community and will try to upstream fixes. Thanks!

11 years, 11 months

[HOWTO] Implement / Validate / Debug / Tune UEFI Runtime drivers

by Olivier Martin

I have just finished to write a wikipage to help people to implement and debug UEFI Runtime drivers based on the Tianocore project (Open Source implementation of the UEFI spec). To validate the UEFI Runtime drivers, I have been using the Linux kernel with EFI Stub support (https://wiki.linaro.org/LEG/Engineering/Kernel/UEFI/EFIstub): Linux kernel available here: https://git.linaro.org/people/leif.lindholm/linux.git/shortlog/refs/heads/ue fi-for-next The wikipage: https://sourceforge.net/apps/mediawiki/tianocore/index.php?title=ArmPkg/Runt ime

11 years, 11 months

← Newer
1
...
71
72
73
74
75
76
77
...
82
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Linaro-uefi