- 19 6月, 2018 22 次提交
-
-
由 Alex Kiernan 提交于
When the `mmc hwpartition` command is disabled, remove the associated help text. Signed-off-by: NAlex Kiernan <alex.kiernan@gmail.com>
-
由 Yevgeny Popovych 提交于
This is the case when reading freshly created filesystem. The error message is like the following: btrfs_read_superblock: No valid root_backup found! Since the data from super_roots/root_backups is not actually used - decided to rework btrfs_newest_root_backup() into btrfs_check_super_roots() that will only check if super_roots array is valid and correctly handle empty scenario. As a result: * btrfs_read_superblock() now only checks if super_roots array is valid; the case when it is empty is considered OK. * removed root_backup pointer from btrfs_info, which would be NULL in case of empty super_roots. * btrfs_read_superblock() verifies number of devices from the superblock itself, not newest root_backup. Signed-off-by: NYevgeny Popovych <yevgenyp@pointgrab.com> Cc: Marek Behun <marek.behun@nic.cz> Cc: Sergey Struzh <sergeys@pointgrab.com>
-
由 Masahiro Yamada 提交于
Follow Linux commit 10b62a2f785a (".gitignore: move *.dtb and *.dtb.S patterns to the top-level .gitignore"). Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
-
由 Masahiro Yamada 提交于
Follow Linux commit 1377dd3e2987 (".gitignore: sort normal pattern rules alphabetically"). This would allow us to easily catch duplicated patterns if any. Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
-
由 Adam Ford 提交于
This adds DM_GPIO support for the davinici GPIO driver with DT support. Signed-off-by: NAdam Ford <aford173@gmail.com>
-
由 Ramon Fried 提交于
Replace Mateusz as Maintainer for ARM Snapdragon arch. Signed-off-by: NRamon Fried <ramon.fried@gmail.com> Acked-by: NMateusz Kulikowski <mateusz.kulikowski@gmail.com>
-
由 Ramon Fried 提交于
Alignment was wrong, missing one tab. fix it. Signed-off-by: NRamon Fried <ramon.fried@gmail.com>
-
由 Ramon Fried 提交于
Don't continue updating the offset when buffer is full. When the buffer size exhausts and there's no space left to write warn the user and update only the needed size and not both the offset and needed size. Add needed buffer size information in the iotrace command. Signed-off-by: NRamon Fried <ramon.fried@gmail.com>
-
由 Ramon Fried 提交于
Add dump trace command which dump all trace buffer content in a much more readable fashion than md. Signed-off-by: NRamon Fried <ramon.fried@gmail.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Ramon Fried 提交于
The header definitions are needed for reading record information in cmd/iotrace.c Signed-off-by: NRamon Fried <ramon.fried@gmail.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Chris Packham 提交于
Whatever code this was guarding has been removed so remove the guards too. Signed-off-by: NChris Packham <judge.packham@gmail.com>
-
由 Chris Packham 提交于
Whatever code this was guarding has been removed so remove the guards too. Signed-off-by: NChris Packham <judge.packham@gmail.com>
-
由 Chris Packham 提交于
Remove empty #ifdef/#ifndef..#endif blocks where the configuration they guarded has been completely removed. Signed-off-by: NChris Packham <judge.packham@gmail.com>
-
由 Igor Opaniuk 提交于
Contains: 1. Overview of Android Verified Boot 2.0 2. Description of avb subset of commands 3. Examples of errors when boot/vendor/system/vbmeta partitions are tampered 4. Examples of enabling AVB2.0 on your setup Signed-off-by: NIgor Opaniuk <igor.opaniuk@linaro.org>
-
由 Igor Opaniuk 提交于
1. Run AVB 2.0 full verification chain, avb verify 2. Check if 'avb get_uuid' works, compare results with 'part list mmc 1' output 3. Test `avb read` commands, which reads N bytes from a partition identified by a name Signed-off-by: NIgor Opaniuk <igor.opaniuk@linaro.org>
-
由 Igor Opaniuk 提交于
1. Add vbmeta partition info to android partition layout for TI platforms. 2. Add support of AVB 2.0 (including avb subset of commands) for am57xx HS Signed-off-by: NIgor Opaniuk <igor.opaniuk@linaro.org> [trini: Move to include/environment/ti/boot.h, reword commit slightly] Signed-off-by: NTom Rini <trini@konsulko.com>
-
由 Igor Opaniuk 提交于
1. Add initial support of boot states mode (red, green, yellow) 2. Add functions for enforcing dm-verity configurations Signed-off-by: NIgor Opaniuk <igor.opaniuk@linaro.org>
-
由 Igor Opaniuk 提交于
Enable a "avb" command to execute Android Verified Boot 2.0 operations. It includes such subcommands: avb init - initialize avb2 subsystem avb read_rb - read rollback index avb write_rb - write rollback index avb is_unlocked - check device lock state avb get_uuid - read and print uuid of a partition avb read_part - read data from partition avb read_part_hex - read data from partition and output to stdout avb write_part - write data to partition avb verify - run full verification chain Signed-off-by: NIgor Opaniuk <igor.opaniuk@linaro.org>
-
由 Igor Opaniuk 提交于
Implement AVB ops on top of existing mmc subsystem API. Currently there is a full implementation of such operations, defined by [1] AVB2.0 specification: .read_from_partition() - reads N bytes from a partition identified by a name. .write_to_partition() - Writes N bytes to a partition identified by a name. .validate_vbmeta_public_key() - checks if the given public ‘vbmeta’ partition is trusted. .get_unique_guid_for_partition() - Gets the GUID for a partition identified by a string name. As [1] specification recommends to use tamper-evident storage for storing rollback indexes and device state (LOCKED/UNLOCKED), currently are only stubs instead of full implementation for these ops: .read_rollback_index() - Gets the rollback index for a given index location .write_rollback_index() - Sets the rollback index to a given location .read_is_device_unlocked() - Gets where the device is unlocked [1] https://android.googlesource.com/platform/external/avb/+/master/README.mdSigned-off-by: NIgor Opaniuk <igor.opaniuk@linaro.org>
-
由 Igor Opaniuk 提交于
Integrate libavb into the build system. Introduce CONFIG_LIBAVB build option. Signed-off-by: NIgor Opaniuk <igor.opaniuk@linaro.org>
-
由 Igor Opaniuk 提交于
Add libavb lib (3rd party library from AOSP), that implements support of AVB 2.0. This library is used for integrity checking of Android partitions on eMMC. libavb was added as it is and minimal changes were introduced to reduce maintenance cost, because it will be deviated from AOSP upstream in the future. Changes: - license headers changed to conform SPDX-style - avb_crc32.c dropped - updates in avb_sysdeps_posix.c/avb_sysdeps.h For additional details check [1] AVB 2.0 README. [1] https://android.googlesource.com/platform/external/avb/+/master/README.mdSigned-off-by: NIgor Opaniuk <igor.opaniuk@linaro.org>
-
-
- 17 6月, 2018 14 次提交
-
-
由 Bin Meng 提交于
Currently when EFI application boots, it says: CPU: x86_64, vendor <invalid cpu vendor>, device 0h Fix this by calling x86_cpu_init_f() in arch_cpu_init(). Signed-off-by: NBin Meng <bmeng.cn@gmail.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Bin Meng 提交于
To avoid confusion, let's rename the efi-x86 target to efi-x86_app. Signed-off-by: NBin Meng <bmeng.cn@gmail.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Bin Meng 提交于
This turns on the EFI framebuffer driver support so that a graphics console can be of additional help. Signed-off-by: NBin Meng <bmeng.cn@gmail.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Bin Meng 提交于
This adds a DM video driver for U-Boot as the EFI payload. The driver makes use of all necessary information from the passed EFI GOP info to create a linear framebuffer device, as if it were initialized by U-Boot itself. Signed-off-by: NBin Meng <bmeng.cn@gmail.com> Reviewed-by: NAnatolij Gustschin <agust@denx.de>
-
由 Bin Meng 提交于
If UEFI BIOS has the graphics output protocol (GOP), let's pass its information to U-Boot payload so that U-Boot can utilize it (eg: an EFI framebuffer driver). Signed-off-by: NBin Meng <bmeng.cn@gmail.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Bin Meng 提交于
Now that we have generic EFI payload support, drop EFI-specific test logics in BayTrail Kconfig and codes, and all BayTrail boards too. Signed-off-by: NBin Meng <bmeng.cn@gmail.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Bin Meng 提交于
Now that we have generic EFI payload support for all x86 boards, drop the QEMU-specific one. Signed-off-by: NBin Meng <bmeng.cn@gmail.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Bin Meng 提交于
It is possible to create a generic EFI payload for all x86 boards. The payload is configured to include as many generic drivers as possible. All stuff that touches low-level initialization are not allowed as such is the EFI BIOS's responsibility. Platform specific drivers (like gpio, spi, etc) are not included. Signed-off-by: NBin Meng <bmeng.cn@gmail.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Bin Meng 提交于
This adds arch_cpu_init() to the payload codes, in preparation for supporting a generic efi payload. Signed-off-by: NBin Meng <bmeng.cn@gmail.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Bin Meng 提交于
At present the EFI application and payload support codes in the x86 directory is distributed in a hybrid way. For example, the Kconfig options for both app and payload are in arch/x86/lib/efi/Kconfig, but the source codes in the same directory get built only for CONFIG_EFI_STUB. This refactors the codes by consolidating all the EFI support codes into arch/x86/cpu/efi, just like other x86 targets. Signed-off-by: NBin Meng <bmeng.cn@gmail.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Bin Meng 提交于
Since commit f3b5056c ("efi_loader: split README.efi into two separate documents"), the original README.efi was renamed to README.u-boot_on_efi, but x86 doc still refers to the old one. This updates the x86 doc to reference both README.u-boot_on_efi and README.uefi. Signed-off-by: NBin Meng <bmeng.cn@gmail.com>
-
由 Ivan Gorinov 提交于
UEFI specifies the calling convention used in Microsoft compilers; first arguments of a function are passed in (%rcx, %rdx, %r8, %r9). All other compilers use System V ABI by default, passing first integer arguments of a function in (%rdi, %rsi, %rdx, %rcx, %r8, %r9). These ABI also specify different sets of registers that must be preserved across function calls (callee-saved). GCC allows using the Microsoft calling convention by adding the ms_abi attribute to a function declaration. Current EFI implementation in U-Boot specifies EFIAPI for efi_main() in the test apps but uses default calling convention in lib/efi. Save efi_main() arguments in the startup code on x86_64; use EFI calling convention for _relocate() on x86_64; consistently use EFI calling convention for efi_main() everywhere. Signed-off-by: NIvan Gorinov <ivan.gorinov@intel.com> Reviewed-by: NAlexander Graf <agraf@suse.de> Reviewed-by: NBin Meng <bmeng.cn@gmail.com> Tested-by: NBin Meng <bmeng.cn@gmail.com>
-
由 Bin Meng 提交于
Fix warning when compiling cherryhill.dts with latest DTC: "Warning (avoid_unnecessary_addr_size): /pci/pch@1f,0: unnecessary #address-cells/#size-cells without "ranges" or child "reg" property" Signed-off-by: NBin Meng <bmeng.cn@gmail.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
-
- 16 6月, 2018 4 次提交
-
-
-
由 Marek Vasut 提交于
The V3M Eagle uses flash with 128 kiB or 256 kiB sectors, disable the 4k sector support. Signed-off-by: NMarek Vasut <marek.vasut+renesas@gmail.com> Cc: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
-
由 Marek Vasut 提交于
Turning the cache off can help when experimenting with bare metal applications, enable the cache command on V3M Eagle to make that easier. Signed-off-by: NMarek Vasut <marek.vasut+renesas@gmail.com> Cc: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
-
由 Marek Vasut 提交于
Fix the CPGWPR/CPGWPCR register address on V3M Eagle to unlock access to the CPG clock control registers. Signed-off-by: NMarek Vasut <marek.vasut+renesas@gmail.com> Cc: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
-