On Fri, Nov 29, 2013 at 11:53:19AM +0000, Matt Fleming wrote:
> On Thu, 28 Nov, at 04:41:20PM, Leif Lindholm wrote:
> > In systems based on [U]EFI-conformant firmware, runtime services provide
> > a standardised way for the kernel to update firmware environment
> > variables. This is used for example by efibootmgr to update which image
> > should be loaded on next boot.
> >
> > This patchset implements basic support for UEFI runtime services on ARM
> > platforms, as well as the basic underlying EFI support. It also defines
> > a mechanism by which the required information is passed from the
> > bootloader (the EFI stub submitted separately) to the kernel via FDT
> > entries.
>
> This all looks pretty good to me. Is this series going through the ARM
> trees?
Thanks.
That's the plan.
/
Leif
The patches support SMBIOS/DMI on arm system, it tested by dmidecode
and lshw tools.
The first patch is wrapping remap/unmap methond for general archs,
and has been posted for review to x86 and ia64, waiting the ack.
The last two patches depend on booting from UEFI and SMBIOS data
reported as Runtime Services Data type.
Ard Biesheuvel (1):
firmware/dmi_scan: generalize for use by other archs
Yi Li (2):
ARM64:DMI: Add smbios/dmi support on arm64
ARM32:DMI: Add smbios/dmi support on arm32
arch/arm/Kconfig | 13 +++++++++++++
arch/arm/include/asm/dmi.h | 28 ++++++++++++++++++++++++++++
arch/arm/kernel/setup.c | 2 ++
arch/arm64/Kconfig | 10 ++++++++++
arch/arm64/include/asm/dmi.h | 28 ++++++++++++++++++++++++++++
arch/arm64/kernel/setup.c | 2 ++
arch/ia64/include/asm/dmi.h | 10 +++++++---
arch/x86/include/asm/dmi.h | 8 ++++++--
drivers/firmware/dmi_scan.c | 20 +++++++++++---------
9 files changed, 107 insertions(+), 14 deletions(-)
create mode 100644 arch/arm/include/asm/dmi.h
create mode 100644 arch/arm64/include/asm/dmi.h
--
1.7.9.5
resending to right list address...
On Wed, Nov 20, 2013 at 12:35 PM, Roy Franz <roy.franz(a)linaro.org> wrote:
> Hi Steven,
>
> I'm getting the following failure when building for V7 VExpress
> RTSM. This failure starts in rev
> e0cec187231a1bf8fc12caa0c4f734771cf6fe42, which is the merge of the
> ACPI topic branch.
>
> Do I need to change something in my build environment in order to support ACPI?
>
> Thanks,
> Roy
>
>
>
> "arm-linux-gnueabihf-ld" -o
> /home/rfranz/cavium/linaro/trees/uefi-next/Build/ArmVExpress-RTSM-A15/RELEASE_ARMLINUXGCC/ARM/ArmPkg/Drivers/AcpiTables/rtsm_ve-v7/AcpiTables/OUTPUT/./Oem0.dll
> -nostdlib --pie --entry _ReferenceAcpiTable
> /home/rfranz/cavium/linaro/trees/uefi-next/Build/ArmVExpress-RTSM-A15/RELEASE_ARMLINUXGCC/ARM/ArmPkg/Drivers/AcpiTables/rtsm_ve-v7/AcpiTables/OUTPUT/./Oem0.obj
> arm-linux-gnueabihf-ld: warning: cannot find entry symbol
> _ReferenceAcpiTable; defaulting to 00000228
> "GenFw" -o /home/rfranz/cavium/linaro/trees/uefi-next/Build/ArmVExpress-RTSM-A15/RELEASE_ARMLINUXGCC/ARM/ArmPkg/Drivers/AcpiTables/rtsm_ve-v7/AcpiTables/OUTPUT/./Oem0.acpi
> -c /home/rfranz/cavium/linaro/trees/uefi-next/Build/ArmVExpress-RTSM-A15/RELEASE_ARMLINUXGCC/ARM/ArmPkg/Drivers/AcpiTables/rtsm_ve-v7/AcpiTables/OUTPUT/./Oem0.dll
> GenFw: ERROR 3000: Invalid
> /home/rfranz/cavium/linaro/trees/uefi-next/Build/ArmVExpress-RTSM-A15/RELEASE_ARMLINUXGCC/ARM/ArmPkg/Drivers/AcpiTables/rtsm_ve-v7/AcpiTables/OUTPUT/./Oem0.dll
> bad ARM dynamic relocations, unkown type 23.
> make: *** [/home/rfranz/cavium/linaro/trees/uefi-next/Build/ArmVExpress-RTSM-A15/RELEASE_ARMLINUXGCC/ARM/ArmPkg/Drivers/AcpiTables/rtsm_ve-v7/AcpiTables/OUTPUT/Oem0.acpi]
> Error 2
>
>
> build.py...
> : error 7000: Failed to execute command
> make --no-print-directory tbuild
> [/home/rfranz/cavium/linaro/trees/uefi-next/Build/ArmVExpress-RTSM-A15/RELEASE_ARMLINUXGCC/ARM/ArmPkg/Drivers/AcpiTables/rtsm_ve-v7/AcpiTables]
This single UEFI binary now supports multiple versions of the FVP Base
Models.
As they all use a different DTB file, load "fdt.dtb" and ask the user to
make sure it is linked to the correct file in the user instructions.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Ryan Harkin <ryan.harkin(a)linaro.org>
---
.../ArmVExpressPkg/ArmVExpress-FVP-AArch64.dsc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/ArmPlatformPkg/ArmVExpressPkg/ArmVExpress-FVP-AArch64.dsc b/ArmPlatformPkg/ArmVExpressPkg/ArmVExpress-FVP-AArch64.dsc
index c325721..194be40 100755
--- a/ArmPlatformPkg/ArmVExpressPkg/ArmVExpress-FVP-AArch64.dsc
+++ b/ArmPlatformPkg/ArmVExpressPkg/ArmVExpress-FVP-AArch64.dsc
@@ -168,7 +168,7 @@
gArmPlatformTokenSpaceGuid.PcdDefaultBootDevicePath|L"VenHw(C5B9C74A-6D72-4719-99AB-C59F199091EB)/Image"
gArmPlatformTokenSpaceGuid.PcdDefaultBootArgument|"console=ttyAMA0 earlyprintk=pl011,0x1c090000 debug user_debug=31 loglevel=9 root=/dev/vda2"
!endif
- gArmPlatformTokenSpaceGuid.PcdDefaultFdtLocalDevicePath|L"VenHw(C5B9C74A-6D72-4719-99AB-C59F199091EB)/fvp-base-gicv2-psci.dtb"
+ gArmPlatformTokenSpaceGuid.PcdDefaultFdtLocalDevicePath|L"VenHw(C5B9C74A-6D72-4719-99AB-C59F199091EB)/fdt.dtb"
gArmPlatformTokenSpaceGuid.PcdDefaultBootType|3
gArmPlatformTokenSpaceGuid.PcdFdtDevicePath|L"VenHw(C5B9C74A-6D72-4719-99AB-C59F199091EB)/fdt.dtb"
--
1.7.9.5
The patch that follows would be good to add to our tree.
It isn't critical, but it fixes an issue that Roy was seeing with single core models.
The patch is taken directly from upstream and I tested it here locally, although only on the newer FVP models.
It applied cleanly to our tree, so I don't see any problems taking it and adding it to linaro-topic-misc or somewhere suitable like that. You could even create a new topic for upstream fixes that will be removed next cycle if you wanted to be ultra-organised.