The addition of ACPI to the image pushed the size of debug builds over
the 0xD2000 limit. Resizing to 0xD5000 fixes this problem.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Ryan Harkin <ryan.harkin(a)linaro.org>
---
.../ArmVExpressPkg/ArmVExpress-CTA15-A7.fdf | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/ArmPlatformPkg/ArmVExpressPkg/ArmVExpress-CTA15-A7.fdf b/ArmPlatformPkg/ArmVExpressPkg/ArmVExpress-CTA15-A7.fdf
index ffd72cd..f225448 100644
--- a/ArmPlatformPkg/ArmVExpressPkg/ArmVExpress-CTA15-A7.fdf
+++ b/ArmPlatformPkg/ArmVExpressPkg/ArmVExpress-CTA15-A7.fdf
@@ -26,12 +26,12 @@
[FD.ARM_VEXPRESS_CTA15A7_EFI]
BaseAddress = 0x81000000|gArmTokenSpaceGuid.PcdFdBaseAddress # The base address of the Firmware in remapped DRAM.
-Size = 0x000D2000|gArmTokenSpaceGuid.PcdFdSize # The size in bytes of the FLASH Device
+Size = 0x000D5000|gArmTokenSpaceGuid.PcdFdSize # The size in bytes of the FLASH Device
ErasePolarity = 1
BlockSize = 0x00001000
-NumBlocks = 0xD2
+NumBlocks = 0xD5
-0x00000000|0x000D2000
+0x00000000|0x000D5000
gArmTokenSpaceGuid.PcdFvBaseAddress|gArmTokenSpaceGuid.PcdFvSize
FV = FVMAIN_COMPACT
--
1.7.9.5
Forwarding to the public list.
---------- Forwarded message ----------
From: Steven Kinney <steven.kinney(a)linaro.org>
Date: 3 December 2013 13:59
Subject: Re: [linaro-uefi-internal] Re: Topic branches for 2013.12-rc-1
To: Anmar Oueja <anmar.oueja(a)linaro.org>
Cc: linaro-uefi-internal <linaro-uefi-internal(a)linaro.org>
Hi All,
2013.12-rc1 will be pushed today; note that the Tianocore
has changes that disrupt patches, for example, in DSC files because of
a GIC DXE name change (from PL390DXE to GICDXE). I have had to
manually apply patches or "hack" patches to have them cleanly apply.
So if you have patches, regarding current work, based off a previous
revision of the Tianocore master, simply be aware that some patches
might need alteration to apply cleanly or simply manually apply the
patch if the diff is small.
Thanks,
Steve
On 2 December 2013 19:03, Anmar Oueja <anmar.oueja(a)linaro.org> wrote:
>
> Hello all,
>
> Please note the following dates:
>
> * December 12th is freeze date (no new patches will be accepted past that date)
> * December 19th is public release date
>
> anmar
>
> On 2 December 2013 10:47, Steven Kinney <steven.kinney(a)linaro.org> wrote:
> > Hi UEFI folks,
> >
> > I am working on the RC1 for 2013.12 and need all of you to
> > create topic branches, based off the latest Tianocore master, and I will
> > track these topic branches when creating 2013.12-rc1. I will look at
> > patches, sent via the linaro-uefi-internal, but will not apply any patches
> > outside of individual topic branches; the mailing list patches will be
> > considered review only.
> >
> > Thanks,
> >
> > Steve
Hello list,
Please cc me, as I'm not subscribed.
It seems that imgbuild.sh destroys the GPT, resulting in kernel not
found.
I followed the instruction on
https://wiki.linaro.org/LEG/Engineering/Kernel/UEFI/build
and do as follows:
# create GPT on 16GB SD:
gdisk -l /dev/sdb
GPT fdisk (gdisk) version 0.8.7
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/sdb: 31116288 sectors, 14.8 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 58356604-961A-4F20-9D71-B4F19ED27A35
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 31116254
Partitions will be aligned on 2048-sector boundaries
Total free space is 30067645 sectors (14.3 GiB)
Number Start (sector) End (sector) Size Code Name
1 10240 1058815 512.0 MiB EF00 EFI System
# create filesystem, copy kernel and dtb:
mkfs.vfat -F32 /dev/sdb1
mount /dev/sdb1 /mnt/
cp arch/arm/boot/uImage /mnt/
cp arch/arm/boot/dts/exynos5250-arndale.dtb /mnt/board.dtb
umount /mnt/
# fetch trees and build:
git clone git://git.linaro.org/arm/uefi/uefi-next.git
git clone git://git.linaro.org/arm/uefi/uefi-tools.git
export PATH=$PATH:/usr/src/uefi-tools
cd uefi-next/
git checkout linaro-tracking
uefi-build.sh arndale
cd SamsungPlatformPkg/Apps/Tools/mkbl2/
# 'burn; image to SD:
./imgburn.sh --disk /dev/sdb --image ../../../../Build/Arndale-Exynos/RELEASE_ARMLINUXGCC/FV/ARNDALE_EFI.fd
Config:
IMAGE ../../../../Build/Arndale-Exynos/RELEASE_ARMLINUXGCC/FV/ARNDALE_EFI.fd
SoC 5250
DISK /dev/sdb
source file(../../../../Build/Arndale-Exynos/RELEASE_ARMLINUXGCC/FV/ARNDALE_EFI.fd) size = 2703360 bytes
target file(./fwbl2.bin) size = 16384 bytes
16+0 records in
16+0 records out
8192 bytes (8.2 kB) copied, 0.00652876 s, 1.3 MB/s
32+0 records in
32+0 records out
16384 bytes (16 kB) copied, 0.0048919 s, 3.3 MB/s
5280+0 records in
5280+0 records out
2703360 bytes (2.7 MB) copied, 0.729687 s, 3.7 MB/s
# list SD:
# gdisk -l /dev/sdb
GPT fdisk (gdisk) version 0.8.7
Caution: invalid main GPT header, but valid backup; regenerating main header
from backup!
Caution! After loading partitions, the CRC doesn't check out!
Warning! Main partition table CRC mismatch! Loaded backup partition table
instead of main partition table!
Warning! One or more CRCs don't match. You should repair the disk!
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: damaged
****************************************************************************
Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk
verification and recovery are STRONGLY recommended.
****************************************************************************
Disk /dev/sdb: 31116288 sectors, 14.8 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 58356604-961A-4F20-9D71-B4F19ED27A35
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 31116254
Partitions will be aligned on 2048-sector boundaries
Total free space is 30067645 sectors (14.3 GiB)
Number Start (sector) End (sector) Size Code Name
1 10240 1058815 512.0 MiB EF00 EFI System
# Boot arndale:
(screen /dev/ttyUSB0 115200)
Boot firmware (version 0.90 built at 20:04:00 on Nov 29 2013)
PROGRESS CODE: V3020003 I0
PROGRESS CODE: V3020002 I0
PROGRESS CODE: V3020003 I0
PROGRESS CODE: V3020002 I0
The default boot selection will start in 1 seconds
ERROR: Did not find Linux kernel.
[1] Linaro image on SD card
- VenHw(3A02E7FE-0649-4FB4-BE4F-A862CA1872A9)/HD(2,MBR,0x00000000,0x2000,0x1A000)/uImage
- Initrd: VenHw(3A02E7FE-0649-4FB4-BE4F-A862CA1872A9)/HD(2,MBR,0x00000000,0x2000,0x1A000)/uInitrd
- Arguments: root=/dev/mmcblk1p3 rw rootwait console=ttySAC2,115200n8 init --no-log
- FDT: VenHw(3A02E7FE-0649-4FB4-BE4F-A862CA1872A9)/HD(2,MBR,0x00000000,0x2000,0x1A000)/board.dtb
- LoaderType: Linux kernel with Local FDT
-----------------------
Global FDT Config
- VenHw(3A02E7FE-0649-4FB4-BE4F-A862CA1872A9)/HD(2,MBR,0x00000000,0x2000,0x1A000)/board.dtb
-----------------------
[a] Boot Manager
[b] Shell
[c] Reboot
[d] Shutdown
Start:
There is no response on keypresses here. There should be?
If I fix the GPT with gdisk, I get no output on boot.
This EFI boot is new for me, so please let me know if I do something
wrong. Also, please let me know if this is the wrong list for this kind
of questions.
Sander
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.
