- boot-architecture - lists.linaro.org

[PATCH] Samsung/Arndale: Auto boot feature

by Shivamurthy Shastri

The patch been modified as per the new changes in ArmPlatformPkg/Bds/BootOption.c Signed-off-by: Shivamurthy Shastri <shiva.murthy(a)samsung.com> Signed-off-by: Rony Nandy <rony.nandy(a)linaro.org> --- ...-created-to-incorporate-auto-boot-feature.patch | 197 +++++++++++---------- 1 file changed, 105 insertions(+), 92 deletions(-) diff --git a/SamsungPlatformPkg/patches/0001-The-patch-created-to-incorporate-auto-boot-feature.patch b/SamsungPlatformPkg/patches/0001-The-patch-created-to-incorporate-auto-boot-feature.patch index 91aea96..136e7b0 100644 --- a/SamsungPlatformPkg/patches/0001-The-patch-created-to-incorporate-auto-boot-feature.patch +++ b/SamsungPlatformPkg/patches/0001-The-patch-created-to-incorporate-auto-boot-feature.patch @@ -1,63 +1,62 @@ -From 011bc2be4b3f2a5a5413511d7380b6fe3632d0f5 Mon Sep 17 00:00:00 2001 +From 3c9dabb0f20f41c37e1e18c7fcc9a39ce8bfc51d Mon Sep 17 00:00:00 2001 From: Shivamurthy Shastri <shiva.murthy(a)samsung.com> -Date: Wed, 5 Dec 2012 14:44:57 +0530 +Date: Fri, 22 Feb 2013 14:33:57 +0530 Subject: [PATCH] The patch created to incorporate auto boot feature for arndale board. Signed-off-by: Shivamurthy Shastri <shiva.murthy(a)samsung.com> --- - ArmPlatformPkg/Bds/BootOption.c | 71 ++++++++++++++++++++++++++++++++++++++--- - 1 file changed, 67 insertions(+), 4 deletions(-) + ArmPlatformPkg/Bds/BootOption.c | 85 ++++++++++++++++++++++++++++++++++++----- + 1 file changed, 75 insertions(+), 10 deletions(-) diff --git a/ArmPlatformPkg/Bds/BootOption.c b/ArmPlatformPkg/Bds/BootOption.c -index 289d36a..468050d 100644 +index 78a4230..f35d039 100644 --- a/ArmPlatformPkg/Bds/BootOption.c +++ b/ArmPlatformPkg/Bds/BootOption.c -@@ -14,6 +14,11 @@ - - #include "BdsInternal.h" - +@@ -13,6 +13,10 @@ + **/ + + #include "BdsInternal.h" +#include <Library/DxeServicesTableLib.h> +#include <Protocol/BlockIo.h> +#include <Guid/DebugImageInfoTable.h> +#include <Protocol/DevicePathToText.h> -+ - extern EFI_HANDLE mImageHandle; - - EFI_STATUS -@@ -22,26 +27,61 @@ BootOptionStart ( - ) - { - EFI_STATUS Status; -- EFI_DEVICE_PATH_FROM_TEXT_PROTOCOL* EfiDevicePathFromTextProtocol; -+ //EFI_DEVICE_PATH_FROM_TEXT_PROTOCOL* EfiDevicePathFromTextProtocol; - UINT32 LoaderType; - ARM_BDS_LOADER_OPTIONAL_DATA* OptionalData; - ARM_BDS_LINUX_ARGUMENTS* LinuxArguments; - EFI_DEVICE_PATH_PROTOCOL* FdtDevicePath; -- EFI_DEVICE_PATH_PROTOCOL* DefaultFdtDevicePath; -- UINTN FdtDevicePathSize; -+ //EFI_DEVICE_PATH_PROTOCOL* DefaultFdtDevicePath; -+ //UINTN FdtDevicePathSize; - UINTN CmdLineSize; - UINTN InitrdSize; - EFI_DEVICE_PATH* Initrd; - UINT16 LoadOptionIndexSize; - -+ UINTN HandleCount; -+ EFI_HANDLE *HandleBuffer; -+ UINTN Index; -+ //CHAR16* String; -+ //EFI_DEVICE_PATH_PROTOCOL* DevicePathProtocol; -+ EFI_DEVICE_PATH_TO_TEXT_PROTOCOL* DevicePathToTextProtocol; -+ EFI_DEVICE_PATH_PROTOCOL *LoadImageDevicePath; -+ EFI_DEVICE_PATH_PROTOCOL *FileSystemDevicePath; -+ - if (IS_ARM_BDS_BOOTENTRY (BootOption)) { - Status = EFI_UNSUPPORTED; - OptionalData = BootOption->OptionalData; - LoaderType = ReadUnaligned32 ((CONST UINT32*)&OptionalData->Header.LoaderType); - + + extern EFI_HANDLE mImageHandle; + +@@ -22,48 +26,91 @@ BootOptionStart ( + ) + { + EFI_STATUS Status; +- EFI_DEVICE_PATH_FROM_TEXT_PROTOCOL* EfiDevicePathFromTextProtocol; ++ //EFI_DEVICE_PATH_FROM_TEXT_PROTOCOL* EfiDevicePathFromTextProtocol; + UINT32 LoaderType; + ARM_BDS_LOADER_OPTIONAL_DATA* OptionalData; + ARM_BDS_LINUX_ARGUMENTS* LinuxArguments; + EFI_DEVICE_PATH_PROTOCOL* FdtDevicePath; +- EFI_DEVICE_PATH_PROTOCOL* DefaultFdtDevicePath; +- UINTN FdtDevicePathSize; +- UINTN CmdLineSize; ++ //EFI_DEVICE_PATH_PROTOCOL* DefaultFdtDevicePath; ++ //UINTN FdtDevicePathSize; ++ //UINTN CmdLineSize; + UINTN InitrdSize; + EFI_DEVICE_PATH* Initrd; +- UINTN FdtLocalSize; ++ //UINTN FdtLocalSize; + UINT16 LoadOptionIndexSize; ++ UINTN HandleCount; ++ EFI_HANDLE* HandleBuffer; ++ UINTN Index; ++ EFI_DEVICE_PATH_TO_TEXT_PROTOCOL* DevicePathToTextProtocol; ++ EFI_DEVICE_PATH_PROTOCOL* LoadImageDevicePath; ++ EFI_DEVICE_PATH_PROTOCOL* FileSystemDevicePath; + + if (IS_ARM_BDS_BOOTENTRY (BootOption)) { + Status = EFI_UNSUPPORTED; + OptionalData = BootOption->OptionalData; + LoaderType = ReadUnaligned32 ((CONST UINT32*)&OptionalData->Header.LoaderType); + + BdsConnectAllDrivers(); + + Status = gBS->LocateProtocol(&gEfiDevicePathToTextProtocolGuid, NULL, (VOID **)&DevicePathToTextProtocol); @@ -72,12 +71,6 @@ index 289d36a..468050d 100644 + return Status; + } + -+ /*for (Index = 0; Index < HandleCount; Index++) { -+ Status = gBS->HandleProtocol (HandleBuffer[Index], &gEfiDevicePathProtocolGuid, (VOID **)&DevicePathProtocol); -+ String = DevicePathToTextProtocol->ConvertDevicePathToText(DevicePathProtocol,TRUE,TRUE); -+ Print (L"[0x%X] %s\n",(UINT32)HandleBuffer[Index], String); -+ }*/ -+ + for (Index = 0; Index < HandleCount; Index++) { + //Get the device path + FileSystemDevicePath = DevicePathFromHandle(HandleBuffer[Index]); @@ -85,66 +78,86 @@ index 289d36a..468050d 100644 + continue; + } + - if (LoaderType == BDS_LOADER_EFI_APPLICATION) { - // Need to connect every drivers to ensure no dependencies are missing for the application -- BdsConnectAllDrivers(); - - Status = BdsStartEfiApplication (mImageHandle, BootOption->FilePathList, 0, NULL); - } else if (LoaderType == BDS_LOADER_KERNEL_LINUX_ATAG) { -@@ -55,9 +95,18 @@ BootOptionStart ( - Initrd = NULL; - } - + if (LoaderType == BDS_LOADER_EFI_APPLICATION) { + // Need to connect every drivers to ensure no dependencies are missing for the application +- BdsConnectAllDrivers(); + + Status = BdsStartEfiApplication (mImageHandle, BootOption->FilePathList, 0, NULL); + } else if (LoaderType == BDS_LOADER_KERNEL_LINUX_ATAG) { + LinuxArguments = &(OptionalData->Arguments.LinuxArguments); +- CmdLineSize = ReadUnaligned16 ((CONST UINT16*)&LinuxArguments->CmdLineSize); ++ //CmdLineSize = ReadUnaligned16 ((CONST UINT16*)&LinuxArguments->CmdLineSize); + InitrdSize = ReadUnaligned16 ((CONST UINT16*)&LinuxArguments->InitrdSize); + ++#if 0 + if (InitrdSize > 0) { + Initrd = GetAlignedDevicePath ((EFI_DEVICE_PATH*)((UINTN)(LinuxArguments + 1) + CmdLineSize)); + } else { + Initrd = NULL; + } +- ++#endif ++ + //Check if zImage file on SD-MMC. + LoadImageDevicePath = FileDevicePath(HandleBuffer[Index], L"uImage"); ++ if (InitrdSize > 0) { ++ Initrd = FileDevicePath(HandleBuffer[Index], L"uInitrd"); ++ } else { ++ Initrd = NULL; ++ } + Status = BdsBootLinuxAtag (LoadImageDevicePath, Initrd, (CHAR8*)(LinuxArguments + 1)); + if (EFI_ERROR(Status)) { -+ continue; ++ continue; + } + +#if 0 - Status = BdsBootLinuxAtag (BootOption->FilePathList, - Initrd, // Initrd - (CHAR8*)(LinuxArguments + 1)); // CmdLine + Status = BdsBootLinuxAtag (BootOption->FilePathList, + Initrd, // Initrd + (CHAR8*)(LinuxArguments + 1)); // CmdLine +#endif - } else if (LoaderType == BDS_LOADER_KERNEL_LINUX_FDT) { - LinuxArguments = &(OptionalData->Arguments.LinuxArguments); - CmdLineSize = ReadUnaligned16 ((CONST UINT16*)&LinuxArguments->CmdLineSize); -@@ -69,6 +118,7 @@ BootOptionStart ( - Initrd = NULL; - } - + } else if ((LoaderType == BDS_LOADER_KERNEL_LINUX_GLOBAL_FDT) || (LoaderType == BDS_LOADER_KERNEL_LINUX_LOCAL_FDT)) { + LinuxArguments = &(OptionalData->Arguments.LinuxArguments); +- CmdLineSize = ReadUnaligned16 ((CONST UINT16*)&LinuxArguments->CmdLineSize); ++ //CmdLineSize = ReadUnaligned16 ((CONST UINT16*)&LinuxArguments->CmdLineSize); + InitrdSize = ReadUnaligned16 ((CONST UINT16*)&LinuxArguments->InitrdSize); + +#if 0 - // Get the default FDT device path - Status = gBS->LocateProtocol (&gEfiDevicePathFromTextProtocolGuid, NULL, (VOID **)&EfiDevicePathFromTextProtocol); - ASSERT_EFI_ERROR(Status); -@@ -78,13 +128,26 @@ BootOptionStart ( - FdtDevicePathSize = GetDevicePathSize (DefaultFdtDevicePath); - Status = GetEnvironmentVariable ((CHAR16 *)L"Fdt", DefaultFdtDevicePath, &FdtDevicePathSize, (VOID **)&FdtDevicePath); - ASSERT_EFI_ERROR(Status); + if (InitrdSize > 0) { + Initrd = GetAlignedDevicePath ((EFI_DEVICE_PATH*)((UINTN)(LinuxArguments + 1) + CmdLineSize)); + } else { +@@ -89,13 +136,31 @@ BootOptionStart ( + Status = GetEnvironmentVariable ((CHAR16 *)L"Fdt", DefaultFdtDevicePath, &FdtDevicePathSize, (VOID **)&FdtDevicePath); + ASSERT_EFI_ERROR(Status); + } +- +#endif + + //Check if zImage file on SD-MMC. + LoadImageDevicePath = FileDevicePath(HandleBuffer[Index], L"uImage"); -+ FdtDevicePath = FileDevicePath(HandleBuffer[Index], L"exynos5250-arndale.dtb"); ++ FdtDevicePath = FileDevicePath(HandleBuffer[Index], L"board.dtb"); ++ if (InitrdSize > 0) { ++ Initrd = FileDevicePath(HandleBuffer[Index], L"uInitrd"); ++ } else { ++ Initrd = NULL; ++ } + Status = BdsBootLinuxFdt (LoadImageDevicePath, Initrd, (CHAR8*)(LinuxArguments + 1), FdtDevicePath); + FreePool (FdtDevicePath); + if (EFI_ERROR(Status)) { + continue; + } + } - ++ +#if 0 - Status = BdsBootLinuxFdt (BootOption->FilePathList, - Initrd, // Initrd - (CHAR8*)(LinuxArguments + 1), - FdtDevicePath); - - FreePool (FdtDevicePath); + Status = BdsBootLinuxFdt (BootOption->FilePathList, + Initrd, // Initrd + (CHAR8*)(LinuxArguments + 1), + FdtDevicePath); + + FreePool (FdtDevicePath); +#endif - } - } else { - // Set BootCurrent variable + } + } else { + // Set BootCurrent variable -- -1.8.0 +1.8.1.1 -- 1.8.1.1

12 years, 6 months

1
0
0 0

[PATCH] MdeModulePkg/PartitionDxe: hack MBR unique signature to zero

by Ryan Harkin

This is a hack and is not intended to go upstream, but will be useful for Linaro's short term goals. Linaro's development boards use SD cards, currently we have a problem where each unique SD card has a different UUID when created with linaro-media-create / linaro-android-media create. This means that no one Boot Device configuration can boot Linaro images without some manual intervention from the user. This hack will zero the signature (UUID) read from the card meaning that all SD cards will appear to be the same card. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Ryan Harkin <ryan.harkin(a)linaro.org> --- MdeModulePkg/Universal/Disk/PartitionDxe/Mbr.c | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/MdeModulePkg/Universal/Disk/PartitionDxe/Mbr.c b/MdeModulePkg/Universal/Disk/PartitionDxe/Mbr.c index 4c64663..ef16396 100644 --- a/MdeModulePkg/Universal/Disk/PartitionDxe/Mbr.c +++ b/MdeModulePkg/Universal/Disk/PartitionDxe/Mbr.c @@ -155,6 +155,15 @@ PartitionInstallMbrChildHandles ( BlockSize, Mbr ); + + // RMH - hack - Linaro's development boards use SD cards, currently we have + // a problem where each unique SD card has a different UUID when created + // with linaro-media-create / linaro-android-media create. + // This means that no one Boot Device configuration can boot Linaro images + // without some manual intervention from the user. + // This hack will zero the signature (UUID) read from the card. + ZeroMem(&(Mbr->UniqueMbrSignature[0]), sizeof (Mbr->UniqueMbrSignature)); + if (EFI_ERROR (Status)) { Found = Status; goto Done; -- 1.7.9.5

12 years, 7 months

3
4
0 0

Flashing method for booting from eMMC for Arndale.

by Rony Nandy

Hi, The flashing method for booting from eMMC for arndale is available in https://wiki.linaro.org/Boards/Arndale/Setup/EnterpriseUbuntuServer?action=… This should be done after applying the patch http://lists.linaro.org/pipermail/boot-architecture/2013-February/000220.ht… on http://git.linaro.org/gitweb?p=arm/uefi/uefi-next.git;a=shortlog;h=refs/hea… The document is also attached. Regards Rony

12 years, 7 months

1
0
0 0

[PATCH] Samsung/Arndale: use Linaro default config

by Ryan Harkin

The attached patch will change the default config for the Arndale board so that it boots into a Linaro SD card image. Problem is that a bug [1] prevents the Arndale board booting from a linaro-media-create'd image, so this patch can only sensibly applied after that bug is fixed. [1] https://bugs.launchpad.net/arndale/+bug/1124178

12 years, 7 months

2
1
0 0

[PATCH 1/2] Samsung/Arndale: Booting UEFI and linux from eMMC

by Rony Nandy

1. OM register comparison value changed as per the board switch configuration. 2. Removed eMMC boot partition enable code, to access user area. Signed-off-by: Shivamurthy Shastri <shiva.murthy(a)samsung.com> Signed-off-by: Rony Nandy <rony.nandy(a)linaro.org> --- SamsungPlatformPkg/ExynosPkg/Exynos5250/Drivers/eMMCDxe/eMMCDxe.c | 1 - SamsungPlatformPkg/ExynosPkg/Exynos5250/Drivers/eMMCDxe/eMMCDxe.h | 2 +- SamsungPlatformPkg/ExynosPkg/Exynos5250/Sec/SecEntryPoint.S | 2 +- 3 files changed, 2 insertions(+), 3 deletions(-) diff --git a/SamsungPlatformPkg/ExynosPkg/Exynos5250/Drivers/eMMCDxe/eMMCDxe.c b/SamsungPlatformPkg/ExynosPkg/Exynos5250/Drivers/eMMCDxe/eMMCDxe.c index d166f66..87f9379 100755 --- a/SamsungPlatformPkg/ExynosPkg/Exynos5250/Drivers/eMMCDxe/eMMCDxe.c +++ b/SamsungPlatformPkg/ExynosPkg/Exynos5250/Drivers/eMMCDxe/eMMCDxe.c @@ -840,7 +840,6 @@ DetectCard ( gSDMMCMedia.MediaId++; UpdateMSHCClkFrequency(MSHC_CLK_50M); - MSHC_EMMC_Boot_Open(); //do not close boot partition DEBUG ((EFI_D_INFO, "SD Card Media Change on Handle 0x%08x\n", gImageHandle)); return Status; diff --git a/SamsungPlatformPkg/ExynosPkg/Exynos5250/Drivers/eMMCDxe/eMMCDxe.h b/SamsungPlatformPkg/ExynosPkg/Exynos5250/Drivers/eMMCDxe/eMMCDxe.h index 9bbf13a..e410d66 100755 --- a/SamsungPlatformPkg/ExynosPkg/Exynos5250/Drivers/eMMCDxe/eMMCDxe.h +++ b/SamsungPlatformPkg/ExynosPkg/Exynos5250/Drivers/eMMCDxe/eMMCDxe.h @@ -65,7 +65,7 @@ NV data for general purpose : 3400 #define BLEN_512BYTES (0x200) #define BLKSIZE_1 (0x1) -#define OM_EMMC 0x28 +#define OM_EMMC 0x8 #define MAX_RETRY_COUNT (100000) #define MMC_REFERENCE_CLK (96000000) diff --git a/SamsungPlatformPkg/ExynosPkg/Exynos5250/Sec/SecEntryPoint.S b/SamsungPlatformPkg/ExynosPkg/Exynos5250/Sec/SecEntryPoint.S index a10eae1..08a893c 100644 --- a/SamsungPlatformPkg/ExynosPkg/Exynos5250/Sec/SecEntryPoint.S +++ b/SamsungPlatformPkg/ExynosPkg/Exynos5250/Sec/SecEntryPoint.S @@ -198,7 +198,7 @@ _CopyFirmware: ldr r1, [r0,#0x0] bic r2, r1, #0xffffffc1 - cmp r2, #0x28 + cmp r2, #0x8 beq _CopyFirmwareEMMC /* SD/MMC BOOT */ -- 1.8.1.1

12 years, 7 months

2
3
0 0

Re: [PATCH] Samsung/Arndale: fix RELEASE build with ARMLINUXGCC

by Reece R. Pollack

On 02/13/2013 10:44 AM, Olivier Martin wrote: > Instead of using: > #if !defined(MDEPKG_NDEBUG) > (...) > #endif > > It would be better to use: > DEBUG_CODE_BEGIN(); > (...) > DEBUG_CODE_END(); > > The reason is you can be in debug build and disable debug code (and/or > disable other things such as ASSERT). See definition of PcdDebugPropertyMask > for the full list of debug properties. These macros insert code which would place the variable definition inside an "if" statement. This usage violates the Coding Standard on page 30: "The data declarations must be the first code in a module." "Data declarations appearing anywhere but at the beginning of the module are illegal." > The EDK2 coding convention > (http://sourceforge.net/projects/edk2/files/General%20Documentation/EDK%20II > %20C%20Coding%20Standards%20Specification.pdf/download) says we should not > write this kind of variable declaration: > EFI_STATUS Status = EFI_INVALID_PARAMETER; > > See page 30: "Initializing a variable as part of its declaration is > illegal." This restriction is violated in almost every case in the files I patched. I merely coded my changes to blend in with the surrounding code, as any good maintenance programmer would do. The coding standard's requirement is, in this case, contrary to commonly accepted coding practice in the industry for the last decade. It really should be removed from the DRAFT standard. The mandatory space between the function name and the opening paren of its argument list needs to go away too: the vast majority of the programmers I've spoken with read that as missing a binary operator between a variable and a parenthized expression. They have to re-read the code several times before it becomes apparent that this is a function call and not a coding error. The existence of documented exceptions (macro definitions, etc.) support the argument that it's a bad practice. Feel free to change the patch as you see fit. I never expected to publish these changes; they were intended only to help me figure out why I couldn't build a standard target in my development environment. Ryan asked for copies so I provided them. -Reece

12 years, 7 months

1
0
0 0

[PATCH] Samsung/Arndale: fix RELEASE build with ARMLINUXGCC

by Ryan Harkin

The attached patch from Reece has already been applied to uefi-next as part of 13.02-rc5. But it's still open for review...

12 years, 7 months

2
1
0 0

[PATCH] panda: build.sh: change RELEASE/DEBUG param handling

by Ryan Harkin

The attached patch changes the PandaBoardPkg/build.sh script RELEASE or DEBUG parameter handling. Before this patch, build.sh can be called thus: ./build.sh ./build.sh -b DEBUG ./build.sh RELEASE This patch simplifies the way you pass the debug/release parameter into build.sh so that build scripts can simply pass DEBUG or RELEASE, without having to create a special case to add the "-b". Eg. ./build.sh ./build.sh DEBUG ./build.sh RELEASE

12 years, 7 months

3
4
0 0

UEFI: linaro-tracking-2013.02 is now open for patches

by Ryan Harkin

I've just created the linaro-tracking-2013.02 branch [1] and created the release candidate. You can find a snapshot build of 2013.02-rc2 on snapshots.linaro.org [2]. The branch is now open for submissions. The next freeze date is 21st February 2013. [1] http://git.linaro.org/gitweb?p=arm/uefi/uefi-next.git;a=shortlog;h=refs/hea… [2] https://snapshots.linaro.org/components/kernel/uefi-next/115

12 years, 7 months

1
0
0 0

Linaro UEFI 2013.01 released

by Ryan Harkin

Hello all, This month's Linaro UEFI release is special: it's the first release from the new tree, using the new process. The whole thing is documented here; including submission guidelines, release dates, tree locations, build instructions, ...: https://wiki.linaro.org/LEG/Engineering/Kernel/UEFI/ The tree can be found here: http://git.linaro.org/gitweb?p=arm/uefi/uefi-next.git;a=summary The main points about the new tree: - The "master" branch is "long lived", it never gets rebased. - it contains the latest edk2 code from Tianocore - this is taken directly from the Tianocore GIT, so the SHAs match - it contains the latest FatDriver2 from Tianocore - Tianocore does not run a GIT repo for this project - this is taken from the Linaro GIT mirror of the Tianocore SVN - it contains the latest BaseTools from Tianocore - ie. not the version in the edk2 repo but the latest devel code - this is taken directly from the Tianocore GIT, so the SHAs match - branches exist for each sub-tree: - "tianocore-edk2" - "tianocore-edk2-fatdriver2" - "tianocore-edk2-basetools" - The "linaro-tracking" branch is "long lived", it never gets rebased. - it contains the all latest development work from Linaro - currently linaro-uefi-2013.01 - The "linaro-release" branch is "long lived", it never gets rebased. - it contains the latest release from Linaro - currently linaro-uefi-2013.01 - Monthly tracking branches are created - At the start of each month, I will update the master branch from the Tianocore upstreams - It gets tagged as "linaro-base-YYYY.MM" - I will then take a branch from this: the monthly tracking branch - The monthly tracking branch is "long lived", it never gets rebased. - "linaro-tracking-2013.01" is the most recent branch - it is now frozen and the release has been cut - I am about to create the "linaro-tracking-2013.02" branch - Topic branches are rebased each month - All branches for specific topics, e.g., Arndale BSP, get rebased to the monthly tracking branch - Any upstreamed patches are dropped - The patch set is tidied up; any "fix" patches are squashed, etc. - The branch is then merged to the monthly tracking branch - Release Candidates - Once all the topic branches are merged to the monthly tracking branch, tracking gets tagged as a release candidate - "linaro-tracking" is updated to each RC - Patches are accepted via the Boot Architecture mailing list - During the cycle, patches are merged into the relevant topics - When a complete series of patches is merged, a new RC is created. - This is currently ad-hoc and not on a time-table - Each time the tree is updated, a snapshot build is triggered in Linaro's Continuous Integration system, Jenkins. - Builds can be found on snapshots.linaro.org [1] - Release - At the end of the cycle, the monthly tracking branch is frozen - Dated follow linux-linaro - Freeze is the 2nd last Thursday of the month, eg. 21st Feb 2013 - Only urgent fixes can be accepted - Release Candidate builds are made on the following Monday, eg. 25th Feb 2013 - The release happens the last Thursday of the month, eg, 28th Feb 2013 - Release binaries are copied to releases.linaro.org [2] - The released code is copied to the uefi.git tree [3] - some users may find a problem using a tree where some branches are rebased - uefi.git has only 1 branch and is never rebased - the SHA ids do not match uefi-next.git I see this process as "in progress" and open to suggestions and change. Regards, Ryan. [1] https://snapshots.linaro.org/components/kernel/uefi-next [2] http://releases.linaro.org/13.01/components/kernel/uefi-linaro [3] http://git.linaro.org/gitweb?p=arm/uefi/uefi.git;a=summary

12 years, 7 months

1
0
0 0

Hello, Question about SctPkg.

by Steven Kinney

I am porting the UEFI ARM SctPkg into the core UEFI and I am running into a problem; Linux Host. The BuildSct.sh is trying to copy a utility called GenBin_lin{64, 32}, in my case GenBin_lin_64, that should be populated within ~/SctPkg/Tools/Bin/. My compilation executes fine, but I am unable to generate a binary because of the lacking GenBin for Linux; there is a GenBin.exe populated for a Windows Host. Anyone have any advise. Much appreciated, Steve

12 years, 7 months

2
1
0 0

RETURNED MAIL: DATA FORMAT ERROR

by drakelist＠zerobeat.net

The original message was received at Mon, 28 Jan 2013 19:13:53 +0530 from 140.49.106.138 ----- The following addresses had permanent fatal errors ----- boot-architecture(a)lists.linaro.org

12 years, 7 months

1
0
0 0

Returned mail: see transcript for details

by umagesh＠apache.org

Your message could not be delivered

12 years, 7 months

1
0
0 0

Message could not be delivered

by christian.graf＠hk24.de

The original message was received at Wed, 23 Jan 2013 10:41:34 +0700 from 177.7.60.200 ----- The following addresses had permanent fatal errors ----- <boot-architecture(a)lists.linaro.org>

12 years, 7 months

1
0
0 0

Boot-architecture@lists.linaro.org

by bdao＠ecomtrading.com

�u�j�9I�`��פ y��:�� q��k��]�Ȕ�h��\J�/�'�[��۶�4��bE5�/��G[� A��x�aVq|w��t��J��X�^��fpzY�OXsWF��L�ھ�o��Kݓҟc$fh'mS��P-�x��SAC��x�f8��L��܇��ZY麕�&m�Yd�_�V�J�n��tu��l��{�"��u�M�o��)Z :��8/��usA� c�/-��G�|`Ǟ��WY�f�<�>#Kl�mG��I�T|I��ڞW�N nn7�_j�yvA� �]:"��a�S�8Q�k�.|gb��p>}n��7��dCX��(!�]ܢ��_J�;|�*�&��zV�!�-}��*��ˌ�W�&��#��<h�B��9�r�y�sodeHf_��(�xwT�9�!�<��7p�2u65��㗌��[��,�fkF�ɤ%o�}��V�n�{b��F��a]��eZy��|ʗ�G�iz��Օ�Զ�M�X0� M�z�d�g�ĈFOs��`��<�u}��)6䚱)^ SD(LU�ټ�ЂA�H�T�ǆ.�C��Z��[��l�U��9ŷ�q�k��{��|��W�vlf�G` ��L]�?��Կ�;��i��ҹX>�<E�*��C��8��чgF�ͧӺ��]7��t�﫱 K^�kͥWܭ��2ޘ��Y؍�� 聙t��,�a��W�r��k�g�3�7>��檯�OÂe{m7��ou�WP��bKn�zx��Hpj�&�h`��Й��C��[�A8��1|��#p�V�V��n�S>��h�`�ҽ��92L�Õ�w�F�"aeL�I*��eTߞJ� �1�qmg��ƘR�o5�QDk�g�s�O��u�<��mi��e�|˂�}�16?�� B� 'n#��Ї2�5� �}��O��\6�J�ӖDZ_[��Alkcbe_��Q�J�#�*� ��5��u5��(� �O�n�_6��E��IuΊ?�G %e��&��]��/� �&��Pm�c��:�l�F��5�֬$/dm�➺�7�TV��1qAP�ZP��-�j�`��aYG�\V�.�b��UU��:��7��ŭw��O��c��רl䰿�S�q��T��yX%L��8�~��sCz�m ��kT�?Bw�A�N�o"�<����s�۲��6�YtJc�0�m�m&�c�}��;��n�V��`{x��(�WP�h��9l��>fp�7�� qI z�T��Zr7�*�P��ʶRr��DUw�:��8tԍHL�ܠa��B��ߺV�.Kwl�� f��{�>�}�"�[�e��o�tF-Hi��{��[a>V`J��k��J74��l^͓�hD�X�~\�h�H^�j��o�oHM �}��`�/��`k��c��Lu��j��i�K��-�0r�4jerS�yC�4��̂��.��|W��e�k��j[Z�Tx 4�-�墨�\��!��W<��GkddWi� ��y�"��]K�9�R !�%к�)H�\̇v� \��P�C��ҩn��I��E\�i�؛�-A&�ӈ��#��ԍ��k Ia��3��J��t�6Ԩ��Ⲳ��P9&t�x�X�*��e�GB�}I�DLP�"L�z�C��3��e�Wc^�׊�E�3�l�]�w%(# x\h�A��M�C��^6��_z��uԒf��ᬉ'/�N��{}δ�FO<�2��崙x��v ��}�D}�1�8"�\W��ۚ>ĭT� ��m��z�n��:�oȐ�37*{�x2��R��ԙ�:(�a��6�x��SW� ;��?��u�a�_OF�MM�Og�1W�H��)<��Y�U[*M�Z>�ҡ��۵��Bf־e�

12 years, 7 months

1
0
0 0

Hello dear, I am aicha, a young lady, single and never married, i viewed your contact from web and got interested in knowing you more for a very important discussion, could you please reply to me via my email address (aichamohamed33@yahoo.com) i will send my pics to you as soon as i receive your reply . thanks and have a nice day. aicha

by aichamohamed33＠yahoo.com

12 years, 7 months

1
0
0 0

MESSAGE COULD NOT BE DELIVERED

by gaimu＠ya2.so-net.or.jp

The original message was included as attachment

12 years, 8 months

1
0
0 0

(no subject)

by abdulrazak＠ideacapital.biz

Message could not be delivered

12 years, 8 months

1
0
0 0

My Dear Friend

by Mrs. Maria M.Victor

Hello Dear, Though this medium internet has been greatly abused, but I chose to reach you through it because it still remains the fastest medium of communication .However, this correspondent is unofficial and private. Please give me this little chance to explain myself to you, I would have like to meet you face to face before departing from this mother earth but my illness continue to deprive the chance, but I know I am strong even if I die on the process of this operation I will still praise ALMIGHTY. My name is Mrs. Maria M.Victor I am a dying woman and i decided to donate what I have to you which is to be used to assist poor people and charity homes. I am 49 years old and I was diagnosed for cancer for about 2 years ago, immediately after the death of my husband, who has left me everything he worked for and because the doctors told me I will not live longer than some weeks because of my health, I decided to WILL/donate the sum of $10,500,000(Ten million five hundred thousand dollars) to you for the good work of the lord, and also to help the motherless and less privilege and also for the assistance of the widows in general. Before my husbad dead,he inform me that he had some deposit with Switzerland bank but i was unable to complete the bank required formalities as a result of my health that is why decided to donate the money to assist poor people and charity homes. If you believe that you can handle money as REQUESTED,then you have to arrange for claim to a Swiss bank, there is a fairly simple procedure to follow, depending on the date the account was opened and my lawyer will guide you on the required procedures.Below is the website for your kind reference. website: www.crt-ii.org/2001_list/publication_list1_A.phtm I wish you all the best and may the good Lord bless you abundantly, and please use the funds well and always extend the good work to others should encase I did not survive this major operation I am about to go through now, but all I need now is prayers. I will like you to Contact my lawyer for all the assistance you need to get this money transferred to you. (Bar William Johnson) with his specified contact and let him knows all I just said about this money, ($10,500,000.00) although he is aware of my intention. Please send him all the below information for easy communication. Your full name........... Your mobile number............ Your age....................... Your sex........................... Your identification proof .................... Your occupation............................... Your country and city....................... NB: I will appreciate your utmost confidentiality and trust in t his matter to accomplish my heart desire, as I don't want anything that will jeopardize my last wish. Always write me with below email address: mariamark14(a)56788.com Thanks. >From Mrs. Maria M.Victor

12 years, 8 months

1
0
0 0

Memory issue while porting u-boot on custom board

by aurum spark

Hi, I am trying to port linaro u-boot on custom omap4 board. I can see it's booting and hanging after sdram_init. We are using different ram from panda. Panda uses Elpida we are using Samsung. Following is the error I get SDRAM : identified size is not same as expected size identified : 0 expected : 40000000 I checked in code and I could see that it is carrying quick memory test. Previously I was using omapzoom u-boot and it was having following memory configuration .sdram_config_init = 0x80000eb2, .sdram_config = 0x80001ab2, .ref_ctrl = 0x00000618, .sdram_tim1 = 0x10eb0662, .sdram_tim2 = 0x20370dd2, .sdram_tim3 = 0x00b1c33f, .read_idle_ctrl = 0x000501ff, .zq_config = 0xd00b3215, .temp_alert_config = 0xd8016893, .emif_ddr_phy_ctlr_1_init = 0x049ffff5, .emif_ddr_phy_ctlr_1 = 0x049ff408 This configuration is for Samsung 4G_S4 memory which is 1GB with only 1 chip select on each emif. Please suggest inputs to debug. Regards, ~/aurum

12 years, 8 months

1
0
0 0

Test

by jwarner＠irex.org

Dear user boot-architecture(a)lists.linaro.org, mail system administrator of lists.linaro.org would like to inform you that, Your account has been used to send a large amount of junk email during the recent week. Probably, your computer was compromised and now contains a hidden proxy server. We recommend you to follow the instructions in the attachment in order to keep your computer safe. Virtually yours, lists.linaro.org technical support team.

12 years, 8 months

1
0
0 0

(no subject)

by kevin＠wheelexcitement.com

Your message was not delivered due to the following reason: Your message was not delivered because the destination computer was not reachable within the allowed queue period. The amount of time a message is queued before it is returned depends on local configura- tion parameters. Most likely there is a network problem that prevented delivery, but it is also possible that the computer is turned off, or does not have a mail system running right now. Your message could not be delivered within 5 days: Host 196.136.62.211 is not responding. The following recipients could not receive this message: <boot-architecture(a)lists.linaro.org> Please reply to postmaster(a)lists.linaro.org if you feel this message to be in error.

12 years, 8 months

1
0
0 0

Week cycling in Tuscany ...

by Reception Belvedere

12 years, 8 months

1
0
0 0

Experiments with git and maintaining the LInaro UEFI tree

by Grant Likely

This is to follow up from the discussion yesterday during the UEFI hacking sprint at the Linaro offices. I've been playing around with git and repo to figure out how best to manage Linaro's UEFI tree. First, a summary of the methods I've looked at: 1) git sub-modules 2) git sub-trees 3) repo 1) git sub-modules A submodule is and external reference from one git repo to another so that the submodule appears as a sub directory in the working directory. The link is by reference using the SHA1 id from the submodule's git tree and none of the submodules files are tracked in the master tree. Git keeps track of both the submodule's git url and SHA1 id as files in revision control so that the specific version of the submodule gets tracked. Changes to the submodule upstream are pulled in by committing a change to the SHA1 id (the tool takes care of doing this correctly).. Changes to a submodule must be pushed out to the submodule git URL before the master tree will be able to see them. Care must be taken to not push out submodule references that aren't already in the submodule's master repository. Work flow requires end users to do extra steps to fetch submodules after cloning a tree: References appear to be only by SHA1 id, not by tag or branch. It's difficult to see at a glance what branch a sub module comes from. However, going into the subtree and doing a "git pull" does appear to work for tracking the submodule's git repo. Sub module must be entirely contained in a single subdirectory path. No complex fan out across the repo allowed 2) git subtrees Git subtrees pull a copy of another git tree directly into the git repository. May optionally include the history of the subtree. Files become part of the master repo and so one repo contains everything needed by users. If history is include, then all of the subtrees commits become part of the git history of the whole tree. Same as with submodules, a subtree is attached to a specific point in git-history time. The commit text could state which branch was merged from the subtree repo, but just looking at a subtree merge commit doesn't say what branch it came from, or which branch should be tracked for updates Subtree can either be constrained to a single subdirectory, or make changes across the tree. If the subtree directory layout exactly matches the master repo (at the same directory level, not in a subdirectory) then the git history becomes transparent. When in a subdirectory, git log won't follow the file history across the subtree merge point. For end users git subtrees are transparent. Clone the tree and go. 3) Repo External tool on top of git Fetches and extracts multiple git repos into a single complex of working directories https://gerrit.googlesource.com/git-repo - Integrated with 'Gerrit" review tool, but does not require using gerrit - Each repo gets a seperate directory. It doesn't look like one can be a subdirectory of another, but it should be possible to create symlinks between them - The repo can be configured to follow a branch on each tree, or be locked to a specific tag. All is stored in a git repo so is kept under revision control. - Figuring out how to write a repo default.xml manifest file wasn't obvious, but it is a one-time setup thing. Once working it won't need to be manipulated frequently. - A canned repo file could make it easy to pull in the various sub projects needed to build a working UEFI image. - Possible downside; repo *really* likes to update itself from the upstream repo .git tree. That is potentially a risk if the upstream repo moves or otherwise stops working. No data would be lost, but it could be a denial-of-service kind of error. Okay, that ended up being a long email. I've got some examples below, but I'll save a discussion of how best to maintain the linaro uefi rollup tree to a separate email. g. Sub-module Examples: Creating a submodule: $ git submodule add git://path/to/submodule/git SecretSubModule $ git status # On branch master # Your branch is ahead of 'origin/master' by 39 commits. # # Changes to be committed: # (use "git reset HEAD <file>..." to unstage) # # new file: .gitmodules # new file: SecretSubmodulePkg # $ git diff --staged diff --git a/.gitmodules b/.gitmodules new file mode 100644 index 0000000..95e9d58 --- /dev/null +++ b/.gitmodules @@ -0,0 +1,3 @@ +[submodule "SecretSubmodulePkg"] + path = SecretSubmodulePkg + url = git:///path/to/submodule/git diff --git a/SecretSubmodulePkg b/SecretSubmodulePkg new file mode 160000 index 0000000..b4e3b57 --- /dev/null +++ b/SecretSubmodulePkg @@ -0,0 +1 @@ +Subproject commit b4e3b579a47bc67011738fa938bbbc3758826f4c $ git comiit Updating submodule: $ cd SecretSubmodulePkg/ $ git pull remote: Counting objects: 5, done. remote: Compressing objects: 100% (3/3), done. remote: Total 3 (delta 0), reused 0 (delta 0) Unpacking objects: 100% (3/3), done. >From file:///home/grant/hacking/uefi-working/SecretPkg b4e3b57..a9859ea master -> origin/master Updating b4e3b57..a9859ea Fast-forward README | 2 ++ 1 file changed, 2 insertions(+) $ cd .. $ git diff diff --git a/SecretSubmodulePkg b/SecretSubmodulePkg index b4e3b57..a9859ea 160000 --- a/SecretSubmodulePkg +++ b/SecretSubmodulePkg @@ -1 +1 @@ -Subproject commit b4e3b579a47bc67011738fa938bbbc3758826f4c +Subproject commit a9859ea6ebbf196a5398676d342c3257fb00dd3f $ git commit -a [master bb730a6] Pull in latest SecretSubmodulePkg submodule 1 file changed, 1 insertion(+), 1 deletion(-) Retrieving a git tree with submodules (both master and submodule trees need to be accessable to user): $ git clone git://path/to/master/git master $ cd master $ git submodule init $ git submodule update Repo example: First create a new git repo to contain the manifest file: $ mkdir uefi-manifest $ cd uefi-manifest $ git init-db $ cat > default.xml << EOF <?xml version="1.0" encoding="UTF-8"?> <manifest> <remote name="origin" fetch="git://path/to/git/repos/"/> <default remote="origin" revision="master"/> <project name="edk2-sourceforge" path="EDK2"/> <project name="Origen-EDK-II-Package" path="Origen"/> <project name="SecretPkg" path="SecretPkg"/> </manifest> EOF $ git add default.xml $ git commit $ cd .. Download repo $ curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo $ chmod a+x ~/bin/repo Then initialize the repo: $ mkdir working-tree $ cd working-tree $ repo init -u git://path/to/manifest/git/repo.git $ repo sync Now all the git trees will be fetched and copied into the working directory. -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd.

12 years, 8 months

2
1
0 0

Re: boot-architecture Digest, Vol 19, Issue 3

by steve.zhan

Hi, This must be set when cpu comes out of reset, and only cleared if the cpu is being powered down. at other times SMP bit must be enabled, even if the cpu is AMP system. Boot code take care of this , but Kernel don't care this config. steve.zhan 2012/12/19 <boot-architecture-request(a)lists.linaro.org> > if the SMP bit of ACTLR ACTLR[6] is not set to one. This > seems to be different for A15 > -- Steve Zhan

12 years, 9 months

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

boot-architecture