On 1/31/24 08:09, Dan Carpenter wrote:
> This condition has a bitwise & vs logical && typo so it only preserves
> odd number error codes.
>
> Fixes: 3b880757abca ("dm: regulator: uclass driver code cleanup")
> Signed-off-by: Dan Carpenter
> ---
> drivers/power/regulator/regulator-uclass.c |
Hello qianfan Zhao,
The patch 62649165cb02: "lib: sparse: Make CHUNK_TYPE_RAW buffer
aligned" from Nov 16, 2021, leads to the following Smatch static
checker warning:
lib/image-sparse.c:214 write_sparse_image()
warn: unsigned 'blks' is never less than zero.
lib/image-sparse.c
This error path should return -EINVAL instead of success.
Fixes: e261fbf34785 ("blk: host_dev: Sanity check on the size of host backing
file")
Signed-off-by: Dan Carpenter
---
drivers/block/host_dev.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/block/host_dev.c
This condition has a bitwise & vs logical && typo so it only preserves
odd number error codes.
Fixes: 3b880757abca ("dm: regulator: uclass driver code cleanup")
Signed-off-by: Dan Carpenter
---
drivers/power/regulator/regulator-uclass.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
The pmic_reg_read() function can return errors. Add a check for that.
Fixes: 4e8aa0065d4b ("button: qcom-pmic: introduce Qualcomm PMIC button driver")
Signed-off-by: Dan Carpenter
---
This patch is mostly to make static checkers happy but it's obvious and
harmless.
Shift all setup stages one step earlier to better fit the
existing uclass.
Signed-off-by: Svyatoslav Ryhel
---
drivers/video/renesas-r61307.c | 93 +++---
drivers/video/renesas-r69328.c | 81 +++--
2 files changed, 95 insertions(+), 79
Shift all setup stages one step earlier to better fit the
existing uclass.
Signed-off-by: Svyatoslav Ryhel
---
drivers/video/bridge/ssd2825.c | 86 ++
1 file changed, 45 insertions(+), 41 deletions(-)
diff --git a/drivers/video/bridge/ssd2825.c
Shift all setup stages one step earlier to better fit the
existing uclass.
Signed-off-by: Svyatoslav Ryhel
---
drivers/video/endeavoru-panel.c | 128 +---
1 file changed, 68 insertions(+), 60 deletions(-)
diff --git a/drivers/video/endeavoru-panel.c
Add initial support for the Toshiba TC358768 RGB to DSI bridge.
The driver is based on the mainline Linux Toshiba TC358768
bridge driver and implements the same set of features.
Tested-by: Andreas Westman Dorcsak # ASUS TF700T
Signed-off-by: Svyatoslav Ryhel
---
drivers/video/bridge/Kconfig
From: Jonas Schwöbel
The Parade DP501 is a DP & DVI/HDMI dual-mode transmitter. It
enables an RGB/Parallel SOC output to be converted, packed and
serialized into either DP or TMDS output device. Only DisplayPort
functionality of this transmitter has been implemented and tested.
Signed-off-by:
From: Anton Bambura
LTL106HL02 is a color active matrix TFT (Thin Film Transistor)
liquid crystal display (LCD) that uses amorphous silicon TFT as
switching devices. This model is composed of a TFT LCD panel, a
driver circuit and a backlight unit. The resolution of a 10.6"
contains 1920 x 1080
The LD070WX3 is a Color Active Matrix Liquid Crystal Display with
an integral Light Emitting Diode (LED) backlight system. The
matrix employs a-Si Thin Film Transistor as the active element. It
is a transmissive type display operating in the normally Black
mode. This TFT-LCD has 7.0 inches
The current patch set improves the logic of existing panels and
bridge used by Tegra 3 devices and brings support for additional
DSI panels used by Tegra 4 devices.
New and existing drivers are fully reusable, contain no device
specific parts, and are written according to existing datasheets.
On Wed, Jan 24, 2024 at 09:37:41AM +0100, Stefan Roese wrote:
Hi Stefan,
Thank you for testing and reviewing.
I have checked the error message and the relationship to my patch.
The reason for the failure has nothing to do with my patch.
Could you kindly help me run the CI test again?
Randolph
Hi Neha,
On 15:53-20240130, Neha Malcom Francis wrote:
> The number of DDR controllers to be initialised and used should depend
> on the device tree with the constraint of the maximum number of
> controllers the device supports. Since J721S2 has multiple (2)
> controllers, instead o
> -Original Message-
> From: U-Boot On Behalf Of "Alexander
> Daum"
> Sent: Wednesday, January 4, 2023 5:11 AM
> To: u-boot@lists.denx.de
> Cc: "Alexander Daum"
> Subject: [PATCH 1/1] socfpga_de1_soc: Specify Uart clock in dts
>
> UART output was broken since commit c402e8170245
On Sat, Jan 27, 2024 at 02:48:45PM +0100, Aurelien Jarno wrote:
> The VisionFive 2 board supports saving the u-boot environment settings
> are saved to on-board SPI flash. However the defconfig enables both
> ENV_IS_NOWHERE and ENV_IS_IN_SPI_FLASH, preventing the "saveenv" command
> to work. Fix
On Wed, Jan 17, 2024 at 05:46:52PM +0100, Heinrich Schuchardt wrote:
> Detect and show if the SBI implements the Debug Trigger Extension.
>
> Signed-off-by: Heinrich Schuchardt
> ---
> arch/riscv/include/asm/sbi.h | 1 +
> cmd/riscv/sbi.c | 1 +
> 2 files changed, 2 insertions(+)
On Tue, Jan 16, 2024 at 02:35:57PM +0800, Nylon Chen wrote:
> From: Vincent Chen
>
> LEDs and multiple fans can be controlled by SPL. This patch ensures
> that all fans have been enabled in the SPL stage. In addition, the
> LED's color will be set to yellow.
>
> Signed-off-by: Vincent Chen
>
On Wed, Jan 10, 2024 at 09:26:53PM +0100, Aurelien Jarno wrote:
> QEMU RISC-V supports multiple virtio devices, but only tries to boot to
> the first one. Enable support for a second virtio device, that is useful
> for instance to boot on a disk image + an installer. Ideally that should
> be made
On Wed, Jan 10, 2024 at 09:17:44PM +0100, Aurelien Jarno wrote:
> The difference between the StarFive VisionFive 2 1.2A and 1.3B boards is
> handled dynamically by looking at the PCB version in the EEPROM in order
> to have a single u-boot version for both versions of the board. While
> the
On Fri, Dec 29, 2023 at 04:32:23PM +0800, Randolph wrote:
> Add the address to which the FDT blob is to be moved.
>
> Signed-off-by: Randolph
> ---
> configs/ae350_rv32_falcon_defconfig | 1 +
> configs/ae350_rv32_falcon_xip_defconfig | 1 +
> configs/ae350_rv64_falcon_defconfig | 1 +
>
On Fri, Dec 29, 2023 at 04:32:22PM +0800, Randolph wrote:
> In Falcon Boot mode, the fdt blob should be move to the RAM from
> kernel BSS section. To avoid being cleared by BSS initialisation.
> SPL_PAYLOAD_ARGS_ADDR is the address where SPL copies.
>
> Signed-off-by: Randolph
> ---
>
On Fri, Dec 29, 2023 at 04:32:21PM +0800, Randolph wrote:
> Add documentation to introduce the Falcon Mode on RISC-V.
> In this mode, the boot sequence is SPL -> OpenSBI -> Linux kernel.
>
> Signed-off-by: Randolph
> ---
> doc/develop/falcon.rst | 158 +
>
On Mon, Jan 29, 2024 at 8:34 AM Fabio Estevam wrote:
>
> On Sun, Jan 28, 2024 at 6:43 PM Jesse Taube wrote:
>
> > +++ b/configs/imxrt1050-evk_fspi_defconfig
> > @@ -0,0 +1,100 @@
> > +CONFIG_ARM=y
> > +CONFIG_SYS_DCACHE_OFF=y
>
> Out of curiosity: what are the problems if the D-Cache is turned
I am using an orangepizero3 and trying to boot from spi flash and then a usb3
SSD on usb-1 port, which is usb2. U-boot does not detect the usb3 SSD drive.
I have been booting Armbian regularly from an old usb2 hard disk drive in the
same way.
After Armbian starts the usb3 SSD drive is
Fabio Estevam writes:
> Hi Milan,
>
> On Tue, Jan 30, 2024 at 9:22 AM Milan Zamazal wrote:
>
>> Well, after trying both the SD cards again with fresh reinstallations, it
>> works
>> with a 32 GB card and I get the error above with a 64 GB card. Is it
>> possible
>> that there is something
Hi Milan,
On Tue, Jan 30, 2024 at 9:22 AM Milan Zamazal wrote:
> Well, after trying both the SD cards again with fresh reinstallations, it
> works
> with a 32 GB card and I get the error above with a 64 GB card. Is it possible
> that there is something wrong with SDXC cards?
Does the change
Dne torek, 30. januar 2024 ob 15:16:42 CET je Andre Przywara napisal(a):
> The OrangePi Zero 2W is a tiny development board featuring the Allwinner
> H618 SoC, shipping with up to 4GB of LPDDR4 DRAM, a mini-HDMI connector,
> two USB Type-C sockets and a 16MB SPI NOR flash.
> There is an FPC
On Mon, Jan 29, 2024 at 11:43:23PM -0500, Sean Anderson wrote:
> The following changes since commit 6faba41927bdc8973b59678649ef83c564cc421e:
>
> Prepare v2024.04-rc1 (2024-01-29 20:53:19 -0500)
>
> are available in the Git repository at:
>
>
On Tue, Jan 30, 2024 at 06:40:45PM +0800, Kelly Hung wrote:
> This initial device-tree provides the necessary configuration for
> basic BMC functionality and work on ASUS X4TF production.
>
> Signed-off-by: Kelly Hung
> ---
> arch/arm/dts/Makefile | 3 +-
>
Add initial support for the PHYTEC phyBOARD-Segin-i.MX93 board based on
the PHYTEC phyCORE-i.MX93 SoM.
Supported features:
- 1GB LPDDR4 RAM
- eMMC
- external SD
- FEC Ethernet
- debug UART
- watchdog
Signed-off-by: Mathieu Othacehe
---
Hello,
This new revision fixes the remarks of Primoz. The
Add a comment to explain the code under is_secure condition of
ti_sci_do_xfer. This will help avoid confusion amongst people who may in
future touch upon this code.
Reviewed-by: Nishanth Menon
Signed-off-by: Dhruva Gole
---
drivers/firmware/ti_sci.c | 6 ++
1 file changed, 6 insertions(+)
The ti_sci driver in U-Boot has support for secure_msg as part of it's
do_xfer function. This let's U-boot send secure messages during boot up.
The protocol to send such secure messages is described as part of the
struct ti_sci_secure_msg_hdr. As part of this, there are 2 fields for
checksum and
This series adds a fix to make the initial 4 bytes of the secure_hdr to be 0 as
per the protocol requirement as of now.
Also, inorder to provide a little more context to people add a comment to
explain why secure calls are made from uboot
For context, please refer to the discussion from the
kr260 revA/revA01 is using discrete oscilator for DP (27MHz) and si5332 for
other clocks but clocks are different compare to kv260 that's why fix it to
aligned with the latest schematics.
On the other handle kr260 revB/revA03 also contains 74.25 MHz discrete
clock chip for SLVC-EC output which is
On Tue, Jan 30, 2024 at 03:26:56PM +0100, Mike Looijmans wrote:
> When an XXX_BOOTCOMMAND isn't defined, the result is that bootcmd is set
> to some random memory content. Fix it so that the function does nothing
> in that case and leaves the bootcmd environment unmodified.
>
> Signed-off-by:
On Tue, Jan 30, 2024 at 02:05:02PM +, Caleb Connolly wrote:
> @@ -119,6 +120,26 @@ static int ehci_usb_of_to_plat(struct udevice *dev)
> return 0;
> }
>
> +static int ehci_usb_of_bind(struct udevice *dev)
> +{
> + ofnode ulpi_node = ofnode_first_subnode(dev_ofnode(dev));
> +
On Tue, Jan 30, 2024 at 02:04:51PM +, Caleb Connolly wrote:
> +
> + /* The clock is already enabled by the clk_bulk above */
> + ret = clk_set_rate(>clks.clks[i], clk_rate);
> + if (!ret) {
> + printf("Couldn't set core clock rate: %d\n", ret);
> + return
When an XXX_BOOTCOMMAND isn't defined, the result is that bootcmd is set
to some random memory content. Fix it so that the function does nothing
in that case and leaves the bootcmd environment unmodified.
Signed-off-by: Mike Looijmans
---
arch/arm/cpu/armv8/fsl-layerscape/soc.c | 5 +
1
Hey,
> And see if it fixes Ethernet on the board?
Yes, it works! That allowed me to check that netboot was working as well
on my patch.
Thanks,
Mathieu
Hello,
> Fixes: d5eae216d833 ("net: dwc_eth_qos: Add board_interface_eth_init() for
> i.MX93")
> Signed-off-by: Primoz Fiser
I confirm that it fixes Ethernet connection when using FEC as a primary
port on the phyBOARD-Segin-i.MX93.
Tested-by: Mathieu Othacehe
Mathieu
The OrangePi Zero 2W is a tiny development board featuring the Allwinner
H618 SoC, shipping with up to 4GB of LPDDR4 DRAM, a mini-HDMI connector,
two USB Type-C sockets and a 16MB SPI NOR flash.
There is an FPC connector to connect an expansion board, which sports
two more USB Type-A sockets and a
Drop the U-Boot specific dragonboard820c.dts file in favour of the
upstream apq8096-db820c.dts and an additional -u-boot.dtsi with the
U-Boot specific additions.
Taken from kernel tag v6.7
Reviewed-by: Neil Armstrong
Signed-off-by: Caleb Connolly
---
arch/arm/dts/Makefile |
On 30/01/2024 14:05, Caleb Connolly wrote:
> On Qualcomm platforms, the TZ may already have certain memory regions
> under protection by the time U-Boot starts. There is a rare case on some
> platforms where the prefetcher might speculatively access one of these
> regions resulting in a board
Add drivers and DTS files, as well as regex matches for
qcom/qualcomm/snapdragon.
Reviewed-by: Neil Armstrong
Signed-off-by: Caleb Connolly
---
MAINTAINERS | 12
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index
Upstream devicetrees label GPIOs with "gpioX", not "GPIO_X", fix this
for SoCs where we're now using upstream DT.
Signed-off-by: Caleb Connolly
---
drivers/pinctrl/qcom/pinctrl-apq8016.c | 26 +-
drivers/pinctrl/qcom/pinctrl-apq8096.c | 16
Drop the U-Boot specific DTS in favour of upstream. We'll only include
the -4000 variant as that is what U-Boot already supported.
Taken from kernel tag v6.7
Reviewed-by: Neil Armstrong
Signed-off-by: Caleb Connolly
---
arch/arm/dts/Makefile|2 +-
This board is entirely supported by the generic arch code and DTS. The
board code used to handle turning on the vbus regulator, however this is
now handled via DT.
With this, the board specific defconfig is also no longer needed, so
drop it as well.
Reviewed-by: Neil Armstrong
Signed-off-by:
Import the headers needed for QCS404-evb.
Taken from kernel tag v6.7
Reviewed-by: Neil Armstrong
Signed-off-by: Caleb Connolly
---
include/dt-bindings/clock/qcom,turingcc-qcs404.h | 15 +++
1 file changed, 15 insertions(+)
diff --git
Don't use hardcoded clock IDs, use the IDs from the dt-bindings to be
compatible with upstream.
Taken from kernel tag v6.7
Reviewed-by: Neil Armstrong
Signed-off-by: Caleb Connolly
---
arch/arm/dts/dragonboard820c.dts | 5 +++--
drivers/clk/qcom/clock-apq8096.c | 5 +++--
2 files changed, 6
Import PM8994 and PMI8994 DTSI files in preparation for switching
MSM8996 boards to upstream DTS.
Taken from kernel tag v6.7
Reviewed-by: Neil Armstrong
Signed-off-by: Caleb Connolly
---
arch/arm/dts/pm8994.dtsi | 152 ++
arch/arm/dts/pmi8994.dtsi
Import dt-binding headers for MSM8996/APQ8096 from Linux.
Taken from kernel tag v6.7
Reviewed-by: Neil Armstrong
Signed-off-by: Caleb Connolly
---
include/dt-bindings/clock/qcom,gcc-msm8996.h | 362 +
include/dt-bindings/clock/qcom,mmcc-msm8996.h | 295
Drop the U-Boot specific dragonboard410c.dts in favour of the upstream
msm8916-sbc.dts. No additional changes are needed to this DTS for U-Boot
support.
Taken from kernel tag v6.7
Reviewed-by: Neil Armstrong
Signed-off-by: Caleb Connolly
---
arch/arm/dts/Makefile |2 +-
Import the supporting pm8916.dtsi and msm8916-pm8916.dtsi files from
upstream in preparation for switching boards over.
Taken from kernel tag v6.7
Reviewed-by: Neil Armstrong
Signed-off-by: Caleb Connolly
---
arch/arm/dts/msm8916-pm8916.dtsi | 157 ++
Import the dt-bindings headers in preparation for switching to upstream
DTS for MSM8916.
Taken from kernel tag v6.7
Reviewed-by: Neil Armstrong
Signed-off-by: Caleb Connolly
---
include/dt-bindings/arm/coresight-cti-dt.h | 37 +
include/dt-bindings/clock/qcom,rpmcc.h | 174
Import the PM8998 and PMI8998 PMIC DTSI files from Linux as well
as the common audio codec in preperation for replacing board DTS files
with upstream.
Taken from kernel tag v6.7
Reviewed-by: Neil Armstrong
Signed-off-by: Caleb Connolly
---
arch/arm/dts/pm8998.dtsi | 130
Import the DT bindings headers that are used by SDM845 from Linux.
Taken from kernel tag v6.7
Reviewed-by: Neil Armstrong
Signed-off-by: Caleb Connolly
---
include/dt-bindings/clock/qcom,camcc-sdm845.h | 116 ++
include/dt-bindings/clock/qcom,dispcc-sdm845.h | 56 +++
Replace the board specific docs with a generic board.rst file which
documents the build/boot process for the sdm845 and qcs404 boards now
that the only differences are the DTB in use.
At the same time, create a debugging page to document some useful
snippets and tips for working with Qualcomm
On Qualcomm platforms, the TZ may already have certain memory regions
under protection by the time U-Boot starts. There is a rare case on some
platforms where the prefetcher might speculatively access one of these
regions resulting in a board crash (TZ traps and then resets the board).
We
With just a few basic rules, we can generate the $fdtfile environment
variable to match the format used in Linux. This uses the root
compatible property inside u-boot, with specific handling for the
Dragonboard845c which is a special case, and for the qrb robotics
boards.
This is known to work on
Heavily inspired by Apple board code. Use the LMB allocator to configure
load addresses at runtime, and implement a lookup table for selecting a
devicetree.
As some Qualcomm RBx boards have different RAM capacities and base
addresses, it isn't possible to hardcode these regions.
Signed-off-by:
Historically, Qualcomm boards have relied on heavy hardcoding in U-Boot,
in many cases to the specific SoC but also to the board itself (e.g.
memory map). This has been largely resolved by modernising the Qualcomm
drivers in U-Boot, however the board code still largely follows this
model.
This
db820c predated support for prepending the kernel image header
automatically, drop it's custom linker script and head.S in favour of
this generic support.
Reviewed-by: Neil Armstrong
Signed-off-by: Caleb Connolly
---
arch/arm/mach-snapdragon/Kconfig | 1 +
Some of the db410c board support code was written to be generic and
placed in mach-snapdragon. However, as the db410c is the only board
using this, move the code out of mach-snapdragon. This makes is more
obvious what code is relevant for which targets and helps tidy things up
a little more.
Use the root compatible strings from upstream Linux, add missing
'#clock-cells' property to the gcc node.
Adjust some of the msm8916/apq8016 drivers to use the correct upstream
compatible properties and DT bindings.
This prepares us to switch to upstream DT in a future patch.
Reviewed-by: Neil
Add a config fragment for building U-Boot such that it can be
chainloaded by aboot/LK rather than being flashed directly to the aboot
partition.
Reviewed-by: Neil Armstrong
Signed-off-by: Caleb Connolly
---
board/qualcomm/dragonboard410c/configs/chainloaded.config | 7 +++
1 file changed,
Introduce a basic pinctrl driver for the SPMI PMIC GPIOs. This is
necessary to make proper use of upstream DT bindings specifically on the
dragonboard410c where they're used to switch between USB host and device
modes.
Only support for driving the pins as output low or high is enabled for
now.
Some platforms hard reset when attempting to configure PMIC GPIOs. Add
support for quirks specified in match data with a single quirk to skip
this configuration. We rely on the GPIO already be configured correctly,
which is always the case for volume up (the only current user of these
GPIOs).
Qualcomm PMICs number their GPIOs starting from 1, implement a custom
.xlate method to handle this.
Reviewed-by: Neil Armstrong
Signed-off-by: Caleb Connolly
---
drivers/gpio/qcom_pmic_gpio.c | 22 ++
1 file changed, 22 insertions(+)
diff --git
There is not "uart" pinctrl state.
Signed-off-by: Caleb Connolly
---
drivers/serial/serial_msm.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/serial/serial_msm.c b/drivers/serial/serial_msm.c
index 0148ddb54df6..c2da313c94e2 100644
--- a/drivers/serial/serial_msm.c
+++
Use the modern helpers to fetch the clock and use the correct property
("clocks" instead of "clock")
Signed-off-by: Caleb Connolly
---
arch/arm/dts/dragonboard410c.dts | 3 ++-
arch/arm/dts/dragonboard820c.dts | 3 ++-
drivers/serial/serial_msm.c | 24 +---
3 files
Introduce support for early debugging. This relies on the previous stage
bootloader to initialise the UART clocks, when running with U-Boot as
the primary bootloader this feature doesn't work. It will require a way
to configure the clocks before the driver model is available.
Signed-off-by: Caleb
We should be returning the rate that we set the clock to, drivers like
MMC rely on this. So fix it.
Signed-off-by: Caleb Connolly
---
drivers/clk/qcom/clock-qcs404.c | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/drivers/clk/qcom/clock-qcs404.c
Adjust the apq8016 and apq8096 drivers to use the upstream compatible
properties, and adjust the associated dts files in U-Boot.
Reviewed-by: Neil Armstrong
Signed-off-by: Caleb Connolly
---
arch/arm/dts/dragonboard410c.dts | 2 +-
drivers/clk/qcom/clock-apq8016.c | 2 +-
The upstream DT is supported here, so drop the U-Boot specific binding
docs.
Reviewed-by: Neil Armstrong
Signed-off-by: Caleb Connolly
---
doc/device-tree-bindings/mmc/msm_sdhci.txt | 25 -
1 file changed, 25 deletions(-)
diff --git
Use the clk_* helper functions and the correct property name for clocks.
Reviewed-by: Neil Armstrong
Signed-off-by: Caleb Connolly
---
drivers/mmc/msm_sdhci.c | 69 -
1 file changed, 46 insertions(+), 23 deletions(-)
diff --git
Add support for a vbus-supply regulator specified in devicetree. This
provides generic support to avoid hardcoded GPIO configuration in board
init code.
Reviewed-by: Neil Armstrong
Signed-off-by: Caleb Connolly
---
This patch has no dependencies
Cc: Marek Vasut
---
When booting U-Boot on board with a locked down first-stage bootloader,
we emulate the Linux boot header. By passing the U-Boot FDT through this
first-stage bootloader and retrieving it afterwards we can pre-populate
the memory nodes and other info like the KASLR address.
Add a function to export
Historically, Qualcomm boards in U-Boot have all had their own
board/qualcomm/xyz directory, their own CONFIG_TARGET_XYZ option, their
own hardcoded sysmap-xyz.c file, and their own U-Boot specific
devicetree with little/no compatibility with upstream DT.
This series makes a few final prepatory
On Sat, 9 Dec 2023 18:10:56 +
Shantur Rathore wrote:
Hi,
> Currently when a hub is turned on, all the ports are powered on.
> This works well for hubs which have individual power control.
>
> For the hubs without individual power control this has no effect.
> Mostly in these scenarios the
> I am based on latest master 6faba41927bd (tag: v2024.04-rc1)
That was it. I rebased from 043ca8c8a9b to 6faba41927bd and I now have
the same behaviour as you. I cannot find which commit fixed the
situation in that interval though.
Preparing the v4,
Thanks,
Mathieu
Hi Mathieu,
On 30. 01. 24 14:37, Mathieu Othacehe wrote:
>
>> I am based on latest master 6faba41927bd (tag: v2024.04-rc1)
>
> That was it. I rebased from 043ca8c8a9b to 6faba41927bd and I now have
> the same behaviour as you. I cannot find which commit fixed the
> situation in that interval
> And what awk do you both have? environment.h is generated via
> scripts/env2string.awk
On my side:
mathieu@meije ~/u-boot [env]$ awk --version
GNU Awk 5.2.1, API 3.2, PMA Avon 8-g1
and I have a similar result with:
mathieu@FRMONPC1176:~$ awk --version
GNU Awk 5.0.1, API: 2.0 (GNU MPFR
Stop using the findfdt script and switch to setting the fdtfile from C
code.
Reviewed-by: Jonathan Humphreys
Reviewed-by: Roger Quadros
Signed-off-by: Nishanth Menon
---
Changes in V3:
- none other than picking up reviews.
V2: https://lore.kernel.org/r/20240109191506.3820908-9...@ti.com
We now can provide a map and have the standard fdtfile variable set from
code itself. This allows for bootstd to "just work".
While at this, replace findfdt in environment with a warning as it is no
longer needed.
Reviewed-by: Jonathan Humphreys
Reviewed-by: Roger Quadros
Signed-off-by:
Hi Mathieu,
On 30. 01. 24 13:49, Mathieu Othacehe wrote:
>
> Hey,
>
>> Can you re-check, please?
>>
>> Maybe check your include/generated/environment.h?
>
> Thanks for checking. It is strange that you do not reproduce that one.
>
> My include/generated/environment.h looks like:
>
>
We shouldn't need finfdt anymore. Drop the env script.
Reviewed-by: Jonathan Humphreys
Reviewed-by: Roger Quadros
Signed-off-by: Nishanth Menon
---
Changes in V3:
- none other than picking up reviews.
V2: https://lore.kernel.org/r/20240109191506.3820908-11...@ti.com
Stop using the findfdt script and switch to setting the fdtfile from
C code.
While at this, replace findfdt in environment with a warning as it is
no longer needed
Reviewed-by: Jonathan Humphreys
Reviewed-by: Roger Quadros
Signed-off-by: Nishanth Menon
---
Changes in V3:
- none other than
We now can provide a map and have the standard fdtfile variable set from
code itself. This allows for bootstd to "just work".
While at this, replace findfdt in environment with a warning as it is no
longer needed.
Reviewed-by: Jonathan Humphreys
Reviewed-by: Roger Quadros
Signed-off-by:
We now can provide a map and have the standard fdtfile variable set from
code itself. This allows for bootstd to "just work".
While at this, replace findfdt in environment with a warning as it is no
longer needed.
Reviewed-by: Jonathan Humphreys
Reviewed-by: Roger Quadros
Signed-off-by:
Stop using the findfdt script and switch to setting the fdtfile from
C code.
While at this, replace findfdt in environment with a warning as it is
no longer needed
Reviewed-by: Jonathan Humphreys
Reviewed-by: Roger Quadros
Signed-off-by: Nishanth Menon
---
Changes in V3:
- none other than
Introduce a common fdt operations library for basic device tree
operations that are common between various boards.
The first library to introduce here is the capability to set up
fdtfile as a standard variable as part of board identification rather
than depend on scripted ifdeffery.
Reviewed-by:
Stop using the findfdt script and switch to setting the fdtfile from C
code.
Reviewed-by: Jonathan Humphreys
Reviewed-by: Roger Quadros
Signed-off-by: Nishanth Menon
---
Changes in V3:
- none other than picking up reviews.
V2: https://lore.kernel.org/r/20240109191506.3820908-10...@ti.com
Add missing board/ti/common/Kconfig references for the platforms that
missed it. The intent is for the common Kconfig to be usable across TI
reference boards as required.
Reported-by: Tom Rini
Signed-off-by: Nishanth Menon
---
New patch:
Fixed build fail that Tom noted:
We now can provide a map and have the standard fdtfile variable set from
code itself. This allows for bootstd to "just work".
While at this, replace findfdt in environment with a warning as it is no
longer needed.
Reviewed-by: Jonathan Humphreys
Reviewed-by: Roger Quadros
Signed-off-by:
This is a wide cleanup to switch to setting fdtfile using env_set
instead of scripted magic. 'fdtfile' is expected to be set by default.
This allows the stdboot triggered efi loaders to find the correct OS
device tree file even if regular boot process is interrupted by user
intervention.
Updates
On Tue, Jan 30, 2024 at 01:49:26PM +0100, Mathieu Othacehe wrote:
>
> Hey,
>
> > Can you re-check, please?
> >
> > Maybe check your include/generated/environment.h?
>
> Thanks for checking. It is strange that you do not reproduce that one.
>
> My include/generated/environment.h looks like:
>
Hey,
> Can you re-check, please?
>
> Maybe check your include/generated/environment.h?
Thanks for checking. It is strange that you do not reproduce that one.
My include/generated/environment.h looks like:
--8<---cut here---start->8---
#define
This initial device-tree provides the necessary configuration for
basic BMC functionality and work on ASUS X4TF production.
Signed-off-by: Kelly Hung
---
arch/arm/dts/Makefile | 3 +-
arch/arm/dts/ast2600-x4tf.dts | 239 ++
2 files changed, 241
1 - 100 of 121 matches
Mail list logo
