- Dec 09, 2023
-
-
We need to set boot->fname before calling efi_set_bootdev otherwise this crashes as bflow->fname is null. Reviewed-by:
Simon Glass <sjg@chromium.org> Signed-off-by:
Shantur Rathore <i@shantur.com>
-
bootmeth_efi sets up bootp_arch which is read later in bootp.c Currently bootp_arch is being set as integer string and being read in bootp.c as hex, this sends incorrect arch value to dhcp server which in return sends wrong file for network boot. For ARM64 UEFI Arch value is 0xb (11), here we set environment as 11 and later is read as 0x11 and 17 is sent to dhcp server. Setting it as hex string fixes the problem. Reviewed-by:
-
- Nov 17, 2023
-
-
EFI applications can be very large and thus used to cause boot failures when malloc() space was exhausted. A recent changed fixed this by using the kernel_addr_r environment var as the address of the buffer. However, it still frees the buffer when the bootflow is discarded. Fix this by introducing a flag to indicate whether the buffer was allocated, or not. Note that kernel_addr_r is not the last word here. It might be better to use lmb to place images. But there is a lot of refactoring to do before we can remove the environment variables. The distro scripts rely on them so it is safe for bootstd to do so too. Fixes: 6a8c2f97 bootstd: Avoid allocating memory for the EFI file Signed-off-by:
Heinrich Schuchardt <xypron.glpk@gmx.de> Tested-by:
-
- Nov 15, 2023
-
-
https://source.denx.de/u-boot/custodians/u-boot-dmTom Rini authored
patman correct import of u_boot_pylib correct long-standing EFI framebuffer bug minor test refactor
-
Simon Glass authored
Correct this typo in the warning message shown when no more bootstage records can be added. Signed-off-by:
Patrick Delaunay <patrick.delaunay@foss.st.com>
Reviewed-by: -
After opening pathname, we must close ifd once we are done with it. Fixes: b9274095 ("sandbox: Add a way to map a file into memory") Signed-off-by:
Sean Anderson <seanga2@gmail.com> Reviewed-by:
-
CONFIG_DM_WARN has a text indicating that these messages should only provided when debugging. This implies that the setting must be default no. We should still create debug messages. Reported-by:
Andre Przywara <andre.przywara@arm.com> Signed-off-by:
Heinrich Schuchardt <heinrich.schuchardt@canonical.com> Reviewed-by:
-
Simon Glass authored
The importlib_resources import is not actually used. Fix this so that patman can run on Python 3.6 to some extent, once 'pip3 install importlib-resources' has been run. Signed-off-by: -
Simon Glass authored
Import this only when it is needed, since it is not present when installed via 'pip install'. Signed-off-by:
-
Simon Glass authored
Tidy up the code a little to reduce the number of pylint warnings. Signed-off-by: -
Simon Glass authored
Add a new run_patman() function to hold the main logic. Signed-off-by: -
Simon Glass authored
Move this code into a separate cmdline module, as is done with the other tools. Use the same HAS_TESTS check as buildman Signed-off-by: -
Simon Glass authored
Use the correct background colour when using white-on-black. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> -
Simon Glass authored
Return an error when the user does not select an OS, so we know whether to boot or not. Move calling of bootflow_menu_run() into a separate function so we can call it from other places. Expand the test to cover these cases. Add some documentation also, while we are here. Signed-off-by: -
Simon Glass authored
Adjust scan_mmc4_bootdev() and related function so that the caller can do its own 'bootflow scan' command. This allows it to change the flags if needed. Signed-off-by: -
Simon Glass authored
The efi_gop driver uses private fields from the video uclass to obtain a pointer to the frame buffer. Use the platform data instead. Check the VIDEO_COPY setting to determine which frame buffer to use. Once the next stage is running (and making use of U-Boot's EFI boot services) U-Boot does not handle copying from priv->fb to the hardware framebuffer, so we must allow EFI to write directly to the hardware framebuffer. We could provide a function to read this, but it seems better to just document how it works. The original change ignored an explicit comment in the video.h file ("Things that are private to the uclass: don't use these in the driver") which is why this was missed when the VIDEO_COPY feature was added. Signed-off-by:Bin Meng <bmeng.cn@gmail.com>
-
- Nov 12, 2023
-
-
https://source.denx.de/u-boot/custodians/u-boot-sunxiTom Rini authored
To quote Andre: The first few patches are some easy refactorings and fixes, most of them actually don't change the generated binaries at all. Then there is a defconfig for a new board, for which we just gained the .dts file from the last kernel DT sync. On top there is support for a new PMIC (AXP313), and LPDDR4 support for the Allwinner H616 SoC, both of which are needed to support new devices that appeared lately, especially cheap TV boxes. While those are technically new features, they don't affect existing boards, for instance the LPDDR4 support code is guarded by a new DRAM type Kconfig variable. So the risk for regressions is very slim. Gitlab CI passed, and I booted that briefly on some boards, including an H616 and an H618 one (with LPDDR4).
-
The H616 SoC family has support for several types of DRAM: DDR3, LPDDR3, DDR4 and LPDDR4. At the moment, the driver only supports DDR3 and LPDDR3 memory. Let's extend the driver to support the LPDDR4 memory. This type of memory widely used in device with T507(-H) SoC and new orangepi zero3 with H618. The compatibility with T507 is not yet complete, because there is difference in the phy_init array. The LPDDR4-2133 timings correspond to DRAM Rayson RS1G32LO4D2BDS-53BT found on the NOR SPI from the Orangepi Zero 3 4GB. Signed-off-by:
Mikhail Kalashnikov <iuncuim@gmail.com> Tested-by:
Piotr Oniszczuk <piotr.oniszczuk@gmail.com> Reviewed-by:
Jernej Skrabec <jernej.skrabec@gmail.com> Acked-by:
-
André Przywara authored
The original H616 DDR3 ODT configuration code wrote board specific values into a sequence of paired registers. For LPDDR3 support we needed to special-case one group of registers, because for that DRAM type we need to write 0 into the lower register of each pair. That already made the code less readable. LPDDR4 support will make things even messier, so let's refactor that code now: We allow to write different values into the lower and upper half of each pair. The masking is moved into a macro, and use in each write statement. The effect is not as obvious yet, as we don't need the full flexibility at the moment, but the motivation will become clearer with LPDDR4 support. Signed-off-by:
-
André Przywara authored
The X-Powers AXP313a is a small PMIC with just three buck converters and three LDOs, one of which is actually fixed (so not modelled here). Add the compatible string and the respective regulator ranges to allow drivers to adjust voltages. Signed-off-by:
Jaehoon Chung <jh80.chung@samsung.com>
-
André Przywara authored
On boards using the AXP313 PMIC, the DRAM rail is often not setup correctly at reset time, so we have to program the PMIC very early in the SPL, before running the DRAM initialisation. Add a simple AXP313 PMIC driver that knows about DCDC2(CPU) and DCDC3(DRAM), so that we can bump up the voltage before the DRAM init. Signed-off-by:
-
Add board support for ICnova A20 SomPi compute module on ICnova ADB4006 development board. Specification: SoM - Processor: Allwinner A20 Cortex-A7 Dual Core at 1GHz - 512MB DDR3 RAM - Fast Ethernet (Phy: Realtek RTL8201CP) ADB4006 - I2C - 2x USB 2.0 - 1x Fast Ethernet port - 1x SATA - 2x buttons (PWRON, Boot) - 2x LEDS - serial console - HDMI - µSD-Card slot - Audio Line-In / Line-Out - GPIO pinheaders https://wiki.in-circuit.de/index.php5?title=ICnova_ADB4006 https://wiki.in-circuit.de/index.php5?title=ICnova_A20_SODIMM devicetree upstreamed with linux 6.5 Signed-off-by:
Ludwig Kormann <ludwig.kormann@ict42.de> Reviewed-by:
-
sunxi platforms put .bss in DRAM, so .bss is not available in SPL before DRAM controller initialization. Therefore, this buffer must be placed in the .data section. Signed-off-by:
Samuel Holland <samuel@sholland.org> Reviewed-by:
-
commit 95168d77 ("sunxi: add Allwinner R528/T113 SoC support") added the new entry out of order. Signed-off-by:
-
CONFIG_ARCH_SUNXI will not be enabled for RISC-V SoCs using this driver. Use the symbol for the driver itself instead. Signed-off-by:
-
The MMC controller driver is (and ought to be) the only user of these register definitions. Put them in a header next to the driver to remove the dependency on a specific ARM platform's headers. Due to the sunxi_mmc_init() prototype, the file was not renamed. None of the register definitions were changed. Signed-off-by:
-
DM_GPIO is always enable in U-Boot proper for ARCH_SUNXI, and this driver is never enabled in SPL, so the condition is always true. Signed-off-by:
-
When building this with clang, we get a warning about having excess parenthesis here, or that we're incorrectly using "==" when we want "=". Correct these by using the common size macro. Signed-off-by:
Tom Rini <trini@konsulko.com> Reviewed-by:
-
André Przywara authored
So far we have a convoluted #ifdef mesh that guards the early AXP PMIC setup in board.c. That combination of &&, || and negations is very hard to read, maintain and especially to extend. Fortunately we have those same conditions already modelled in the Kconfig file, so they are actually redundant. On top of that the real reason we have those preprocessor guards in the first place is about the symbols that are *conditionally* defined: without #ifdefs the build would break because of them being undefined for many boards. To simplify this, just change the guards to actually look at the symbols needed, so CONFIG_AXP_xxx_VOLT instead of CONFIG_AXPyyy_POWER. This drastically improves the readability of this code, and makes adding PMIC support a pure Kconfig matter. Doing this revealed one bug in Kconfig: there is no axp_set_dcdc4() for the AXP818, even though CONFIG_AXP_DCDC4_VOLT includes that PMIC. Since the AXP818 wasn't included when calling axp_set_dcdc4() in board.c, this wasn't an issue, but becomes one now, so also remove the AXP818 from the DCDC4 Kconfig symbol. Signed-off-by:
-
- Nov 11, 2023
-
-
https://source.denx.de/u-boot/custodians/u-boot-efiTom Rini authored
Documentation: * hikey960: update link URLs * j7200_evm: Fix OPTEE platform name * ti: fix style of examples * fix typos
-
Heinrich Schuchardt authored
%s/form/from/ Fixes: d46bee8c ("doc: qfw man-page") Signed-off-by:
-
Use prompt instead of code-block to have copy-paste friendly command documentation. Signed-off-by:Nishanth Menon <nm@ti.com>
-
The sphinx-prompt documentation[0] provides examples on how we can use prompt as a parameter to simplify the description. Use the same. While at it, ensure to make all relevant prompts clarified such as gdb prompts. [0] http://sbrunner.github.io/sphinx-prompt/ Signed-off-by:
-
Signed-off-by:
Milan P. Stanić <mps@arvanta.net> Reviewed-by:
-
Heinrich Schuchardt authored
Title underlines should match the length of the title. Unfortunately docutils only catches underlines that are too short. Add some missing empty lines after titles. Signed-off-by: -
k3-j7200 does not exist in upstream OPTEE. Use j721e as the platform name. Using k3-j7200 as OPTEE name results in broken boot due to wrong configuration being picked. Fixes: c727b81d ("doc: board: ti: k3: Reuse build instructions") Signed-off-by:
-
The build instructions for the hikey960 had some broken links. Update the links to use new vendor URLs. Also change build instructions to reference a different file name. Signed-off-by:Dylan Corrales <deathcamel58@gmail.com> Cc: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
-
- Nov 10, 2023
-
-
Tom Rini authored
To quote the author: Since commit [1], Ethernet is broken on TI AM62 and AM64 platforms. The commit [1] is not the culprit. It just unearths the problem by fixing the error check in k3-udma.c. This issue was silently being ignored earlier due to wrong error check. [NULL instead of FDT_ADDR_T_NONE]. Fix the issue by adding the necessary register spaces for the u-boot K3-UDMA driver for AM62 and AM64 platforms. These properties will eventually make it into the SoC DTSi files [2] after which these can be dropped from k3-*-u-boot.dtsi files. [1] - 5fecea171de3dd ("treewide: use dev_read_addr_*_ptr() where appropriate") [2] - https://lore.kernel.org/linux-arm-kernel/20230810174356.3322583-1-vigneshr@ti.com/ -
Update main_bcdma and main_pktdma nodes for native configuration in the absence of DM services. Drop duplicate main_pktdma node in k3-am642-sk-u-boot.dtsi. Reported-by:
Siddharth Vadapalli <s-vadapalli@ti.com> Signed-off-by:
Roger Quadros <rogerq@kernel.org> Reviewed-by:
-
Update main_bcdma and main_pktdma nodes for native configuration in the absence of DM services. u-boot k3-udma driver expects these additional register fields else probe will fail. Reported-by:
Marcel Ziswiler <marcel.ziswiler@toradex.com>
-
