boot-architecture

boot-architecture@lists.linaro.org

7 participants
651 discussions

[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

[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, 6 months

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, 6 months

[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, 6 months

[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, 6 months

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

[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

[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

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

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

← Newer
1
...
53
54
55
56
57
58
59
...
66
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

boot-architecture