- 13 5月, 2019 16 次提交
-
-
由 Heinrich Schuchardt 提交于
UEFI SCT uses this call sequence to determine the current TPL level inside notification functions: OldTpl = BS->RaiseTPL(TPL_HIGH_LEVEL); BS->RestoreTPL(OldTpl); In RestoreTPL() we trigger the notification function of queued events. If we do not mark the event as non-queued before calling the notification function, this results in an infinite recursive call sequence. Mark the event as non-queued before entering the notification function. Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Heinrich Schuchardt 提交于
Replace unnecessary control structures by using return statements. Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Heinrich Schuchardt 提交于
If AllocatePages() is called with AllocateAddress, the UEFI spec requires to return EFI_NOT_FOUND in case the memory page does not exist. The UEFI SCT II 2017 spec additionally requires to return EFI_NOT_FOUND if the page is already allocated. Check that *Memory refers to an unallocated page. UEFI SCT II (2017): AllocatePages(), 5.1.2.1.9 - 5.1.2.1.10 Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Heinrich Schuchardt 提交于
According to the UEFI AllocatePages() has to return EFI_OUT_OF_RESOURCES if sufficient memory is not available. Change the return value. UEFI SCT II (2017): 3.2.1 AllocatePages(), 5.1.2.1.8 Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Heinrich Schuchardt 提交于
When we call FreePages() we essentially add memory to our memory map. We shouldn't do this for memory that does not exit. Check if the memory that is to be freed via FreePages() or FreePool() is in our memory map and is not EFI_CONVENTIONAL_MEMORY. This check is mandated by the UEFI specification. Cf. UEFI SCT II (2017), 3.2.2 FreePages(), 5.1.2.1 - 5.1.2.2 Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Heinrich Schuchardt 提交于
According to the UEFI specification UninstallProtocolInteface() has to return EFI_NOT_FOUND if the interface is not found. Correct the return value. Cf. UEFI SCT II spec (2017), 3.3.2 UninstallProtocolInterface(), 5.1.3.2.4 Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Heinrich Schuchardt 提交于
efi_search_protocol() already checks that the GUID matches. Don't check a second time. Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Heinrich Schuchardt 提交于
A parameter check in LocateDevicePath() does not match the requirements of the UEFI spec. If device is NULL, only return EFI_INVALID_PARAMETER if a matching handle is found. Cf. UEFI SCT II specification (2017)3.3.7 LocateDevicePath(), 5.1.3.7.3 Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Heinrich Schuchardt 提交于
%s/not buffer/no buffer/ Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Heinrich Schuchardt 提交于
The device path to text protocol is not needed for EBBR compliance. So let's make it a customizable option. Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Heinrich Schuchardt 提交于
The Unicode collation protocol is not needed for EBBR compliance. So let's make it a customizable option. The Unicode capitalization table is only needed by this protocol. So let it depend on the Unicode collation protocol. Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Heinrich Schuchardt 提交于
No need to mention U-Boot in brief description. Fix several typos, mention iPXE. Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Heinrich Schuchardt 提交于
Use if/endif for dependencies to give structure to the configuration menu. Sort important settings to the top. Abbreviate the short description of EFI_LOADER_HII. Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Heinrich Schuchardt 提交于
If EFI_LOADER_HII is not set, do not unnecessarily compile files for HII protocols. Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Heinrich Schuchardt 提交于
Assign include/charset.h to EFI PAYLOAD. The functions defined in this include are used by the UEFI sub-system. Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Heinrich Schuchardt 提交于
Correct the description of utf8_utf16_strnlen() and utf8_utf16_strlen() to reflect that they return u16 count and not byte count. For these functions and utf16_utf8_strnlen() describe the handling of invalid code sequences. Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
- 10 5月, 2019 24 次提交
-
-
由 Tom Rini 提交于
- Correct CONFIG_CRC32 related options in Kconfig - CONFIG_GPIO select's DM_GPIO, drop CONFIG_GPIO from whitelist.txt
-
由 Chris Packham 提交于
There are no longer any references to this in the code so this can be removed. Signed-off-by: NChris Packham <judge.packham@gmail.com> Reviewed-by: NHeiko Schocher <hs@denx.de>
-
由 Chris Packham 提交于
There is no check for CONFIG_CRC32 so the #define in image.h does nothing. Remove it. Reported-by: NRobert P. J. Day <rpjday@crashcourse.ca> Signed-off-by: NChris Packham <judge.packham@gmail.com> Reviewed-by: NStefano Babic <sbabic@denx.de> Reviewed-by: NHeiko Schocher <hs@denx.de>
-
由 Chris Packham 提交于
There is no 'config CRC32' remove the select that was attempting to use it. Reported-by: NRobert P. J. Day <rpjday@crashcourse.ca> Signed-off-by: NChris Packham <judge.packham@gmail.com> Reviewed-by: NHeiko Schocher <hs@denx.de>
-
由 Chris Packham 提交于
There is no 'config CRC32', remove the select that was attempting to use it. Reported-by: NRobert P. J. Day <rpjday@crashcourse.ca> Signed-off-by: NChris Packham <judge.packham@gmail.com> Reviewed-by: NHeiko Schocher <hs@denx.de>
-
由 Chris Packham 提交于
CONFIG_GPIO does not exist. There is one hit for it in tegra_gpio.c but it is a variable name. Signed-off-by: NChris Packham <judge.packham@gmail.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Chris Packham 提交于
CONFIG_GPIO does not exist. sysreset_gpio.c uses the DM gpio APIs so the correct option to select is DM_GPIO. Reported-by: NRobert P. J. Day <rpjday@crashcourse.ca> Signed-off-by: NChris Packham <judge.packham@gmail.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Tom Rini 提交于
- Minor fixes (ata memory leak, implement feedback on ohci-da8xx changes, avb test fix, mmc test fix, spelling fixes, make FIT really optional, fit-dtb blob cleanups, TI K3 workflow improvements, bootz can boot barebox on 32bit ARM).
-
由 Lokesh Vutla 提交于
There is one case where 400ms is not sufficient for loading the system firmware: - System firmware is not signed with rsa degenerate key. - ROM loading the sysfw directly from SPI flash which is in memory mapped mode. The above scenario is definitely not desired in production use cases as it effects boot time. But still keeping this support as this is a valid boot scenario. Signed-off-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Lokesh Vutla 提交于
Instead of overlading makefile, use the k3_gen_x509_cert.sh script to generate boot images. Signed-off-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Lokesh Vutla 提交于
TI's K3 boot architecture mandates a x509 certificate for every boot image. While signing the image K3 ROM allows for two types of keys based on which the boot image gets loaded in different ways: - Degenerate RSA keys: This generates a signature which is equal to the digest. When ROM sees this, it does a DMA for copying the images, which significantly improves the boot time. - Any other key: Does a memcpy to load the image. This is introduced as a fallback for DMA copy. Add a script for generating boot images with the above options. Default generates image using rsa degenerate key in order to improve boot time. Signed-off-by: NLokesh Vutla <lokeshvutla@ti.com> Signed-off-by: NDave Gerlach <d-gerlach@ti.com> Signed-off-by: NAndreas Dannenberg <dannenberg@ti.com>
-
由 Vagrant Cascadian 提交于
Support for compressed fit-dtb.blob was added in: commit 95f4bbd5 ("lib: fdt: Allow LZO and GZIP DT compression in U-Boot") When building compressed (lzop, gzip) fit-dtb.blob images, the compression tool may embed the time or umask in the image. Work around this by manually setting the time of the source file using SOURCE_DATE_EPOCH and a hard-coded 0600 umask. With gzip, this could be accomplished by using -n/--no-name, but lzop has no current workaround: https://bugs.debian.org/896520 This is essentially the same fix applied to multi-dtb fit SPL images in: commit 8664ab7d ("Set time and umask on multi-dtb fit images to ensure reproducibile builds.") Signed-off-by: NVagrant Cascadian <vagrant@reproducible-builds.org>
-
由 Vagrant Cascadian 提交于
Support for compressed fit-dtb.blob was added in: commit 95f4bbd5 ("lib: fdt: Allow LZO and GZIP DT compression in U-Boot") Adjust Makefile to also clean compressed blobs. Signed-off-by: NVagrant Cascadian <vagrant@reproducible-builds.org>
-
由 Vagrant Cascadian 提交于
Support for compressed fit-dtb.blob was added in: commit 95f4bbd5 ("lib: fdt: Allow LZO and GZIP DT compression in U-Boot") Adjust .gitignore to also exclude compressed blobs. Signed-off-by: NVagrant Cascadian <vagrant@reproducible-builds.org>
-
由 Christoph Fritz 提交于
For chainboot configurations or test environments, this patch allows booting barebox images by using command bootz. Signed-off-by: NChristoph Fritz <chf.fritz@googlemail.com>
-
由 Stephen Warren 提交于
Fix test_mmc_dev(), test_mmc_rescan(), test_mmc_info() not to use the same configuration data that test_mmc_rd() does. Doing so causes the following issues: * The new code uncondtionally expects certain keys to exist in the configuration data. These keys do not exist in existing configuration data since they were not previously required, and there was no notification re: a requirement to add these new keys. This causes test failures due to thrown exceptions when accessing the non-existent keys. * The new tests logically operate on different objects. test_mmc_rd() operates on ranges of sectors on an MMC device (which may be the entire set of sectors of a device, or a part of a device), whereas all the new tests operate solely on entire devices. These are separate things, and it's entirely likely that the user will wish to runs the two types of tests on different sets of data; see the example configuration data that this commit adds. Ideally, the new tests would have been added to a separate Python file, since they aren' closely related to the existing tests. FIXME: Marek, can you please replace the "???" in this patch with some reasonable looking data? Thanks. Cc: Marek Vasut <marek.vasut@gmail.com> Fixes: 4ffec8cd ("test/py: mmc: Add 'mmc info' test") Fixes: ce4b2caf ("test/py: mmc: Add 'mmc rescan' test") Fixes: 86dfd152 ("test/py: mmc: Add 'mmc dev' test") Signed-off-by: NStephen Warren <swarren@nvidia.com>
-
由 Simon Goldschmidt 提交于
This function merely relocates the fdt blob, so don't let it alter it by adding reservations that didn't exist before. Instead, if the memory used for the fdt blob has been reserved before calling this function, ensure the relocated memory is marked as reserved instead. Reported-by: NKeerthy <j-keerthy@ti.com> Reported-by: NLokesh Vutla <lokeshvutla@ti.com> Signed-off-by: NSimon Goldschmidt <simon.k.r.goldschmidt@gmail.com> Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Fabrice Fontaine 提交于
Due to some mistakes in the source code, it was not possible to really turn FIT support off. This commit fixes the problem by means of the following changes: - Enclose "bootm_host_load_image" and "bootm_host_load_images" between checks for CONFIG_FIT_SIGNATURE, in common/bootm.c. - Enclose the declaration of "bootm_host_load_images" between checks for CONFIG_FIT_SIGNATURE, in common/bootm.h. - Condition the compilation and linking of fit_common.o fit_image.o image-host.o common/image-fit.o to CONFIG_FIT=y, in tools/Makefile. Signed-off-by: NCarlos Santos <casantos@datacom.ind.br> [fabio: adapt for 2016.07] Signed-off-by: NFabio Estevam <festevam@gmail.com> [Ricardo: fix conditional compilation and linking of the files mentioned above for 2016.07] Signed-off-by: NRicardo Martincoski <ricardo.martincoski@gmail.com> [Jörg: adapt for 2019.01] Signed-off-by: NJörg Krause <joerg.krause@embedded.rocks> [Retrieved from: https://git.buildroot.net/buildroot/tree/package/uboot-tools/0003-Make-FIT-support-really-optional.patch] Signed-off-by: NFabrice Fontaine <fontaine.fabrice@gmail.com>
-
由 Vagrant Cascadian 提交于
Signed-off-by: NVagrant Cascadian <vagrant@debian.org>
-
由 Marek Vasut 提交于
Fix the max frequency entry description, it's incorrect. Signed-off-by: NMarek Vasut <marek.vasut+renesas@gmail.com> Cc: Chris Brandt <chris.brandt@renesas.com> Cc: Jagan Teki <jagan@amarulasolutions.com> Cc: Tom Rini <trini@konsulko.com>
-
由 Igor Opaniuk 提交于
Fix test_avb_persistent_values() pytest, which was failing because of wrong size value provided from tee sandbox driver. Reported-by: NHeinrich Schuchardt <xypron.glpk@gmx.de> Signed-off-by: NIgor Opaniuk <igor.opaniuk@gmail.com>
-
由 Christian Gmeiner 提交于
malloc(..) and memalign(..) are both allocating memory and as a result we leak the memory allocated with malloc(..). Signed-off-by: NChristian Gmeiner <christian.gmeiner@gmail.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Adam Ford 提交于
Per feedback from Marek, he suggested better handling and to enable DM_FLAG_OS_PREPARE, this patch re-orders some of the error checking, and errors returns the error code right away and also sets DM_FLAG_OS_PREPARE. Signed-off-by: NAdam Ford <aford173@gmail.com>
-
由 Stefan Roese 提交于
As much of the watchdog system has been migrated to DM now, formalize a deadline for migration. Please note that the old CONFIG_HW_WATCHDOG macro should be removed completely at some point. Signed-off-by: NStefan Roese <sr@denx.de> Cc: Michal Simek <michal.simek@xilinx.com> Cc: Simon Glass <sjg@chromium.org> Cc: Tom Rini <trini@konsulko.com>
-