Hi Sebastian,
On 04.09.24 02:03, Sebastian Reichel wrote:
Hi Soeren,
On Wed, Sep 04, 2024 at 12:26:43AM GMT, Soeren Moch wrote:
* non PD capable (reports 5V 0A)
With a dumb power supply (actually 12V w/o USB-PD) I see a error message
(not really sure if that makes sense, but no strong opin
Hi Chris,
On Fri, 30 Aug 2024 at 21:27, Chris Morgan wrote:
>
> From: Chris Morgan
>
> Add pinctrl nodes for the r_i2c node. Without the pinmux defined the
> r_i2c bus may fail to work, possibly if the bootloader uses rsb mode
> for the PMIC.
>
> Link:
> https://lore.kernel.org/linux-sunxi/1722
From: Stanley Chu
Clear all gpio events to avoid unexpected interrupts
during kernel booting.
Signed-off-by: Stanley Chu
---
drivers/pinctrl/nuvoton/pinctrl-npcm8xx.c | 18 ++
1 file changed, 18 insertions(+)
diff --git a/drivers/pinctrl/nuvoton/pinctrl-npcm8xx.c
b/drivers/pi
Change env offset and boot address for new design.
Signed-off-by: Jim Liu
---
configs/arbel_evb_defconfig | 4 ++--
include/configs/arbel.h | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/configs/arbel_evb_defconfig b/configs/arbel_evb_defconfig
index 08753aebc0..9983d
If CONFIG_SYS_MEM_TOP_HIDE is defined, gd->ram_size is reduced by
CONFIG_SYS_MEM_TOP_HIDE. Need to correct the actual ram size in
dram_init_banksize.
Signed-off-by: Jim Liu
---
board/nuvoton/arbel_evb/arbel_evb.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/board/n
Modify npcm8xx new boot design.
Correct memory setting and set gpio default value.
Jim Liu (2):
board: arbel: correct the dram bank size
configs: arbel_evb: change env offset and boot address
Stanley Chu (1):
pinctrl: npcm8xx: clear all gpio events
board/nuvoton/arbel_evb/arbel_evb.c
Modify npcm8xx new boot design.
Correct memory setting and set gpio default value.
Jim Liu (2):
board: arbel: correct the dram bank size
configs: arbel_evb: change env offset and boot address
Stanley Chu (1):
pinctrl: npcm8xx: clear all gpio events
board/nuvoton/arbel_evb/arbel_evb.c
On Mon, 26 Aug 2024 17:29:13 +0530, Sughosh Ganu wrote:
> This is a follow-up from an earlier RFC series [1] for making the LMB
> and EFI memory allocations work together. This is a non-rfc version
> with only the LMB part of the patches, for making the LMB memory map
> global and persistent.
>
>
Hi Soeren,
On Wed, Sep 04, 2024 at 12:26:43AM GMT, Soeren Moch wrote:
> > * non PD capable (reports 5V 0A)
>
> With a dumb power supply (actually 12V w/o USB-PD) I see a error message
> (not really sure if that makes sense, but no strong opinion from my side)
> and 5V/1.5A reported with 'tcpm in
Hi Sebastian,
Thanks for new patch version!
On 03.09.24 20:16, Sebastian Reichel wrote:
Hi,
On ROCK 5B power is usually supplied via it's USB-C port. This port has the
data lines connected to RK3588, VBUS connected to the input regulator and
CC pins connected to FUSB302. FUSB302 is a USB-C con
The commit mentioned in Fixes broke the
CONFIG_DEVICE_TREE_INCLUDES feature, with the result that any board
setting any non-empty value for that fails to build.
The parent of the mentioned commit refactoring a bit by introducing
the dtsi_include_list variable and changing cmd_dtc to loop over that
On Tue, Sep 03, 2024 at 05:21:51PM +0530, Prasad Kummari wrote:
> Add a generic rule in Makefile.lib to automatically apply
> fdtoverlay, so that each platform doesn't need to include
> a complex rule. This also automatically appends
> DTC_FLAGS_foo_base += -@ to all base files.
>
> The platform'
On Fri, 02 Aug 2024 11:25:34 +0200, Philip Oberfichtner wrote:
> This patch series implements the dwc_eth_qos glue driver for Intel SOCs.
> Before doing that, a few general adaptions to the dwc_eth_qos.c main
> driver are required. Most notably, the preparation for PCI based driver
> instances, wh
On Mon, Sep 02, 2024 at 03:07:44PM +0200, Caleb Connolly wrote:
> Hi Simon,
>
> On 01/09/2024 21:10, Simon Glass wrote:
> > Hi Caleb,
> >
> > On Sun, 1 Sept 2024 at 08:21, Caleb Connolly
> > wrote:
> >>
> >> Hi,
> >>
> >> On 31/08/2024 23:22, E Shattow wrote:
> >>> Hi Caleb, the problem here is
On Sat, Aug 31, 2024 at 05:46:19PM +0100, Caleb Connolly wrote:
> When using the FDT command to inspect an arbitrary FDT in memory, it
> will always be necessary to explicitly set the FDT address. However it
> is also quite likely that the command is being used to inspect U-Boot's
> own FDT. Simpl
On Sun, Sep 01, 2024 at 02:09:47PM -0600, Simon Glass wrote:
[snip]
> > As an aside, please review the ti,am625 stuff with some TI folks, that's
> > both far too specific (you're going to need to add different am62 and
> > am64 and am69 and j7... and on and on cases) and I forget if there's
> > so
On Sun, Sep 01, 2024 at 02:09:58PM -0600, Simon Glass wrote:
> Hi Tom,
>
> On Fri, 30 Aug 2024 at 08:26, Tom Rini wrote:
> >
> > On Thu, Aug 29, 2024 at 07:04:36PM -0600, Simon Glass wrote:
> > > Hi Tom,
> > >
> > > On Thu, 29 Aug 2024 at 10:59, Tom Rini wrote:
> > > >
> > > > On Thu, Aug 29, 20
Now that all code has been prepared update the default configuration to
make use of it.
Reviewed-by: Kever Yang
Signed-off-by: Sebastian Reichel
---
configs/rock5b-rk3588_defconfig | 4
1 file changed, 4 insertions(+)
diff --git a/configs/rock5b-rk3588_defconfig b/configs/rock5b-rk3588_de
Add new section for USB TypeC Port Manager (TCPM) support, which
is needed to figure out cable orientation of USB-C plus and to do
USB PD communication.
Signed-off-by: Sebastian Reichel
---
MAINTAINERS | 9 +
1 file changed, 9 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 2
Since older U-Boot releases do not negotiate USB PD, the kernel
DT may not enable the USB-C controller by default to avoid a
regression. The plan is to upstream it with 'status = "fail";'
instead. U-Boot should then mark it as 'status = "okay";' if
it negotiated USB PD. Currently existing upstream
Hi,
On ROCK 5B power is usually supplied via it's USB-C port. This port has the
data lines connected to RK3588, VBUS connected to the input regulator and
CC pins connected to FUSB302. FUSB302 is a USB-C controller, which can be
accessed via I2C from RK3588. The USB-C controller is needed to figure
This adds TCPM framework in preparation for fusb302 support, which can
handle USB power delivery messages. This is needed to solve issues with
devices, that are running from a USB-C port supporting USB-PD, but not
having a battery.
Such a device currently boots to the kernel without interacting wi
Now that the TCPM framework exists we can introduce fusb302
driver using it. This chip is a very common USB-C controller
chip with PD support, which can be found in the Radxa Rock 5B
among many other boards. Apart from Power Delivery, it also
handles detection of the cable orientation. That can be
Add USB-C controller (fusb302), which will be used by U-Boot to
initialize USB-PD. This is needed, because USB-PD communication
must happen within 5 seconds after the USB-C connector got plugged.
On my Rock 5B it often takes 5 seconds to jump to the Linux binary,
so it must happen before Linux is i
Hi,
On Tue, Sep 03, 2024 at 03:42:51PM GMT, Sören Moch wrote:
> On 03.09.24 13:00, Soeren Moch wrote:
> > Hi Sebastian,
> >
> > On 31.08.24 15:36, Soeren Moch wrote:
> > [...]
> > > Unfortunately I see the same problem as in v3: boot loop when powering
> > > the board from my notebook (ThinkPad X
On 9/3/24 9:42 AM, Mattijs Korpershoek wrote:
On lun., sept. 02, 2024 at 15:41, Quentin Schulz
wrote:
Hi Marek,
On 9/2/24 3:37 PM, Marek Vasut wrote:
The mmc speed command configuration option keeps showing up in
Kconfig directly in 'Command line interface'. Move MMC_SPEED_MODE_SET
under CM
On Tue, Sep 03, 2024 at 07:09:41PM +0200, Francis Laniel wrote:
> Hi!
>
> With this series, I bumped the new hush to get the latest commits from
> upstream.
>
> Also, I added back a reverted commit which goal was to fix a bad behavior in
> old hush test.
> I had to tweak a bit this commit, but
This commit adds the following hush busybox upstream commits:
23da5c4b716b ("hush: do not exit interactive shell on some redirection errors")
14e28c18ca1a ("hush: fix "exec 3>FILE" aborting if 3 is exactly the next free
fd")
6c38d0e9da2d ("hush: avoid duplicate fcntl(F_SETFD, FD_CLOEXEC) during in
From: Ion Agorria
The dollar test was merged with bugous console behavior, and
instead of fixing it, this behavior was just workarounded.
This was done to keep compatibility with the existing behavior.
It seems like without the fix the ut_assert_skipline(); didn't clear
console and running ut_as
Hi!
With this series, I bumped the new hush to get the latest commits from upstream.
Also, I added back a reverted commit which goal was to fix a bad behavior in
old hush test.
I had to tweak a bit this commit, but everything worked both locally and in the
CI [1].
Francis Laniel (1):
cli: mode
On 8/30/24 13:40, Sughosh Ganu wrote:
In the version 2 of the FWU metadata, the metadata is broken into two
parts, a top-level structure, which provides information on the total
size of the structure among other things. Try reading the primary
partition first, and if that fails, try reading th
On 9/3/24 16:56, Tom Rini wrote:
On Mon, Sep 02, 2024 at 11:53:46AM +0200, Michal Simek wrote:
Hi,
please pull these changes to your next branch. Changes have been sent for a
while and there was no reply to them.
Here is the thread.
https://lore.kernel.org/all/20240605100221.3571-1-venkates
Because DEBUG_UART_BOARD_INIT depends on DEBUG_UART, hard dependency
to DEBUG_UART_BOARD_INIT in ROCKCHIP_PX30 can cause warnings if
DEBUG_UART is disabled.
The DEBUG_UART_BOARD_INIT is already implied by ARCH_ROCKCHIP entry.
Remove hard dependency from ROCKCHIP_PX30, so that it will be
consistent
Allow to disable serial console in TPL and SPL. Weak dependency
to SPL_SERIAL and TPL_SERIAL is also used in other Rockchip boards.
Signed-off-by: Lukasz Czechowski
Reviewed-by: Quentin Schulz
---
arch/arm/mach-rockchip/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --
Introduce new config symbols TPL_RAM_ROCKCHIP_DEBUG and
SPL_RAM_ROCKCHIP_DEBUG to allow for better dependencies control
of RAM driver debugging configuration.
Add negative dependencies to TPL_SILENT_CONSOLE and
SPL_SILENT_CONSOLE, respectively.
Replace IS_ENABLED(CONFIG_RAM_ROCKCHIP_DEBUG) directi
The RAM_ROCKCHIP_DEBUG can be used only if DEBUG_UART is
available, otherwise it won't have any effect.
Signed-off-by: Lukasz Czechowski
---
drivers/ram/rockchip/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/ram/rockchip/Kconfig b/drivers/ram/rockchip/Kconfig
index 67c63ecb
In case DEBUG UART is not used, define dummy macros replacing
the actual function implementations that will not be available.
This allows to compile code and avoid linker errors.
Because the DEBUG_UART_FUNCS macro should not be used if
DEBUG UART is not available, redefine it to generate compilatio
Currently it is not possible to completely silent the debug console
in i.e. PX30, what might be required in some embedded devices
Disabling DEBUG_UART results in errors, due to missing symbols.
In particular, rockchip sdram driver performs calls to debug_uart
functions (i.e. printascii), defined di
The TCS writes has no effect after the removal of the __tcs_set_trigger()
call, obviously it seems the RSC version 3 requires it to complete the
transactions.
Fixes: 80c5be164ad ("soc: qcom: rpmh-rsc: drop unused multi-threading and
non-active TCS support")
Signed-off-by: Neil Armstrong
---
dr
Add the PM8550 & related regulators found on the SM8550 and SM8650 platforms.
The tables are imported from the Linux driver.
Signed-off-by: Neil Armstrong
---
drivers/power/regulator/qcom-rpmh-regulator.c | 136 ++
1 file changed, 136 insertions(+)
diff --git a/drivers/p
ower/regulator/qcom-rpmh-regulator.c | 136 ++
drivers/soc/qcom/rpmh-rsc.c | 43
2 files changed, 179 insertions(+)
---
base-commit: bb403c895887eb5b29652f916646f886b34c6309
change-id: 20240903-topic-sm8x50-regulators-support-b149f2417299
Best reg
Hi Simon,
On Sat, 17 Aug 2024 at 11:58, Simon Glass wrote:
> Hi Raymond,
>
> On Fri, 16 Aug 2024 at 09:47, Raymond Mao wrote:
> >
> > Motivations for changes:
> > Current SMBIOS library and command-line tool is not fully matching with
> > the requirements:
> > 1. Missing support for other manda
Hi Ilias,
On Fri, 30 Aug 2024 at 05:37, Ilias Apalodimas
wrote:
> Hi Simon,
>
> On Thu, 29 Aug 2024 at 18:01, Simon Glass wrote:
> >
> > Hi Raymond,
> >
> > On Fri, 16 Aug 2024 at 15:47, Raymond Mao
> wrote:
> > >
> > > Integrate common/hash.c on the hash shim layer so that hash APIs
> > > fro
Hi Ilias,
On Wed, 28 Aug 2024 at 05:54, Ilias Apalodimas
wrote:
> Hi Raymond
>
> On Sat, 17 Aug 2024 at 00:47, Raymond Mao wrote:
> >
> > Integrate common/hash.c on the hash shim layer so that hash APIs
> > from mbedtls can be leveraged by boot/image and efi_loader.
> >
> > Signed-off-by: Raymo
Hi Simon,
On Thu, 29 Aug 2024 at 11:01, Simon Glass wrote:
> Hi Raymond,
>
> On Fri, 16 Aug 2024 at 15:47, Raymond Mao wrote:
> >
> > Integrate common/hash.c on the hash shim layer so that hash APIs
> > from mbedtls can be leveraged by boot/image and efi_loader.
> >
> > Signed-off-by: Raymond M
Hi Ilias,
On Wed, 28 Aug 2024 at 06:37, Ilias Apalodimas
wrote:
> Hi Raymond,
>
> [...]
>
> > --- a/lib/mbedtls/Makefile
> > +++ b/lib/mbedtls/Makefile
> > @@ -5,17 +5,23 @@
> >
> > MBEDTLS_LIB_DIR = external/mbedtls/library
> >
> > +# shim layer for hash
> > +obj-$(CONFIG_$(SPL_)MD5_MBEDTLS) +
On Mon, Sep 02, 2024 at 06:26:20PM +0200, Neil Armstrong wrote:
> Hi Tom,
>
> A simple set of changes to allow using the bootrom NAND pages, ported from
> Linux.
>
> Thanks,
> Neil
>
> The following changes since commit ee2af844ba1b27b2e959c4e649e4b769fbeb4074:
>
> Merge tag 'efi-2024-10-rc
On Mon, Sep 02, 2024 at 02:41:18PM -0300, Fabio Estevam wrote:
> Hi Tom,
>
> Please pull from u-boot-imx/next, thanks.
>
> The following changes since commit e83ced1a24095de66e526bd6c10f0f24584baaee:
>
> bootstage: Fix unstash of records from SPL (2024-08-28 10:07:59 -0600)
>
> are available
Hi Ilias,
On Wed, 28 Aug 2024 at 05:25, Ilias Apalodimas
wrote:
> On Sat, 17 Aug 2024 at 00:46, Raymond Mao wrote:
> >
> > Adapt digest header files to support both original libs and MbedTLS
> > by switching on/off MBEDTLS_LIB_CRYPTO.
> > Introduce _LEGACY kconfig for legacy hash implementation
Hi Tom,
On Mon, 19 Aug 2024 at 17:04, Tom Rini wrote:
> On Fri, Aug 16, 2024 at 02:43:49PM -0700, Raymond Mao wrote:
>
> > Integrate MbedTLS v3.6 LTS (currently v3.6.0) with U-Boot.
> >
> > Motivations:
> >
> >
> > 1. MbedTLS is well maintained with LTS versions.
> > 2. LWIP is inte
Hi Simon,
On Sat, 17 Aug 2024 at 11:58, Simon Glass wrote:
> Hi Raymond,
>
> On Fri, 16 Aug 2024 at 15:44, Raymond Mao wrote:
> >
> > Integrate MbedTLS v3.6 LTS (currently v3.6.0) with U-Boot.
> >
> > Motivations:
> >
> >
> > 1. MbedTLS is well maintained with LTS versions.
> > 2.
On Mon, Sep 02, 2024 at 11:53:46AM +0200, Michal Simek wrote:
> Hi,
>
> please pull these changes to your next branch. Changes have been sent for a
> while and there was no reply to them.
> Here is the thread.
> https://lore.kernel.org/all/20240605100221.3571-1-venkatesh.abbar...@amd.com/
>
> We
On 9/2/24 04:43, Michal Simek wrote:
>
>
> On 8/13/24 00:07, Sean Anderson wrote:
>>
>> Boot devices (QSPI, MMC, NAND, and Ethernet) use secure access for DMA
>> by default. As this causes problems when using the SMMU [1], configure
>> them for normal access instead.
>>
>> [1] https://support.xil
On 8/30/24 13:40, Sughosh Ganu wrote:
The version 2 of the FWU metadata has a top level structure, followed
by optional information on the updatable images. Perform some sanity
checks on some of the fields in the top level structure to determine
if the rest of the structure has to be read.
Si
On 9/2/24 12:26, Venkatesh Yadav Abbarapu wrote:
This series adds support for Xilinx qspi parallel and
stacked memeories.
In parallel mode, the current implementation assumes that a maximum
of two flashes are connected. The QSPI controller splits the data
evenly between both the flashes so, b
On 03.09.24 13:00, Soeren Moch wrote:
Hi Sebastian,
On 31.08.24 15:36, Soeren Moch wrote:
[...]
Unfortunately I see the same problem as in v3: boot loop when powering
the board from my notebook (ThinkPad X1 Nano running Ubuntu 24.04.1
LTS),
see boot log below.
Patch version v2 is still running
Add a generic rule in Makefile.lib to automatically apply
fdtoverlay, so that each platform doesn't need to include
a complex rule. This also automatically appends
DTC_FLAGS_foo_base += -@ to all base files.
The platform's Makefile only needs to have this now:
foo-dtbs := foo_base.dtb foo_overlay
Remove device tree overlay (DTBO) entries for the ZynqMP target
from the Makefile. Add new device tree binaries (DTBs) for the
zynqmp-sm-k24-revA and zynqmp-smk-k24-revA configurations.
Signed-off-by: Michal Simek
Signed-off-by: Prasad Kummari
---
arch/arm/dts/Makefile | 21
Prasad Kummari (2):
kbuild: Add generic rule to apply fdtoverlay
arm64: zynqmp: Remove overlays and add new dtb entries for ZynqMP
arch/arm/dts/Makefile | 78 +-
scripts/Kbuild.include | 4 +++
scripts/Makefile.build | 1 +
scripts/Makefile.lib | 2
Enable both the BIST driver and the R5 remoteproc to be able to
successfully probe and trigger BIST tests on MAIN_R5 cores.
Signed-off-by: Neha Malcom Francis
---
configs/j784s4_evm_r5_defconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/configs/j784s4_evm_r5_defconfig b/configs/j784s
Trigger BIST on MAIN_R5_2_x cores from R5 SPL on J784S4.
Signed-off-by: Neha Malcom Francis
---
arch/arm/mach-k3/j784s4/j784s4_init.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/arch/arm/mach-k3/j784s4/j784s4_init.c
b/arch/arm/mach-k3/j784s4/j784s4_init.c
index 07b5d7d7504.
Add a driver for the BIST module which currently includes support for
BIST IPs that trigger PBIST (Memory BIST).
Signed-off-by: Neha Malcom Francis
---
drivers/misc/Kconfig | 8 +
drivers/misc/Makefile | 1 +
drivers/misc/k3_bist.c | 507 +++
Add bootph-pre-ram as well as the clocks and power-domains for
MAIN_R5_2_x. This ensures that LPSC sets the appropriate power and clock
and allows for BIST to turn the cores on and off for running the
self-test at R5 SPL stage.
Signed-off-by: Neha Malcom Francis
---
dts/upstream/src/arm64/ti/k3-
Add DT node for PBIST_14 that is responsible for triggering the BIST
self-tests for the MAIN_R5_2_x cores.
Signed-off-by: Neha Malcom Francis
---
dts/upstream/src/arm64/ti/k3-j784s4-main.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/dts/upstream/src/arm64/ti/k3-j784s4-main
Add clock and power domains for MAIN_R5_2_0, MAIN_R5_2_1 and PBIST_14.
Signed-off-by: Neha Malcom Francis
---
arch/arm/mach-k3/r5/j784s4/clk-data.c | 13 +
arch/arm/mach-k3/r5/j784s4/dev-data.c | 7 +++
2 files changed, 20 insertions(+)
diff --git a/arch/arm/mach-k3/r5/j784s4/c
This is an RFC series that aims to implement a driver for the BIST
(Built-In Self Test) module for K3 devices. The BIST driver must ideally
support triggering of BIST tests, both PBIST (Memory BIST) and LBIST
(Logic BIST) on a core. Both tests are destructive in nature. Please see
links [1] and [2]
HI,
čt 8. 2. 2024 v 16:00 odesílatel Massimiliano Minella
napsal:
>
> From: Massimiliano Minella
>
> In gsub, when the destination string is empty, the string 't' is
> provided and the regular expression doesn't match, then the final result
> is an empty string.
>
> Example:
>
> => echo ${foo}
>
Hi Sebastian,
On 31.08.24 15:36, Soeren Moch wrote:
[...]
Unfortunately I see the same problem as in v3: boot loop when powering
the board from my notebook (ThinkPad X1 Nano running Ubuntu 24.04.1 LTS),
see boot log below.
Patch version v2 is still running totally fine in the exact same setup
(
> Same question as for v1, are we sure that the partition block size is
> the same as the MMC erase block size? Is this guaranteed by all
> standards (all MMC standards, and all partition table standards)?
> Otherwise I assume we should do some maths here to figure out the MMC
> start block AND blo
Hi Simon,
On 9/2/24 12:26 AM, Simon Glass wrote:
This unmaps a different address from what was mapped. Fix it.
Signed-off-by: Simon Glass
---
(no changes since v1)
cmd/mem.c | 26 +-
1 file changed, 13 insertions(+), 13 deletions(-)
diff --git a/cmd/mem.c b/cmd/me
On 9/3/24 10:04, Marek Behún wrote:
On Tue, Sep 03, 2024 at 08:57:24AM +0200, Stefan Roese wrote:
On 8/29/24 10:08, Marek Behún wrote:
Use the i2c_eeprom miscellaneous driver for reading Turris Omnia EEPROM
in U-Boot proper. Keep using dm_i2c_read() in SPL build, since adding
the i2c_eeprom dri
Hi Tomas,
On 9/2/24 8:49 PM, Tomas Paukrt wrote:
The mmc erase command currently requires blk# and cnt parameters
which can be obtained using the part start and part size commands
if the entire partition needs to be erased.
Simplify the use of the mmc erase command by allowing the partition
nam
cmd/pxe.c (CMD_PXE) calls do_get_tftp() (CMD_TFTPBOOT) therefore add
an "imply" to cmd/Kconfig.
Signed-off-by: Jerome Forissier
Reviewed-by: Peter Robinson
---
cmd/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/cmd/Kconfig b/cmd/Kconfig
index 978f44eda42..be15a4d2670 100644
--- a/c
common/update.c (UPDATE_COMMON) depends on tftp_timeout_ms which is
defined in cmd/tftp.c (CMD_TFTPBOOT). Therefore add the appropriate
imply statement to Kconfig.
Signed-off-by: Jerome Forissier
Reviewed-by: Peter Robinson
---
common/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/
Add a test to test_efi_loader.py similar to the TFTP test but for HTTP
with the wget command.
Suggested-by: Tom Rini
Signed-off-by: Jerome Forissier
Tested-by: Tom Rini
Reviewed-by: Peter Robinson
---
test/py/tests/test_efi_loader.py | 62 +++-
1 file changed, 46 i
test_efi_helloworld_net() and test_efi_grub_net() depend on
cmd_tftpboot so add the missing annotations.
Reported-by: Tom Rini
Signed-off-by: Jerome Forissier
Reviewed-by: Peter Robinson
Reviewed-by: Ilias Apalodimas
---
test/py/tests/test_efi_loader.py | 2 ++
1 file changed, 2 insertions(+)
If env__pxe_boot_test_skip is not present, it defaults to True not
False. Therefore fix the comment.
Signed-off-by: Jerome Forissier
Reviewed-by: Peter Robinson
Reviewed-by: Ilias Apalodimas
---
test/py/tests/test_net_boot.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/
The fec_mxc_init() function currently always returns 0. This does not
allow the callers to detect when for instance the PHY initialization
failed due to the port being unconnected. Fix that by returning the
status of fec_open().
Signed-off-by: Jerome Forissier
Reviewed-by: Fabio Estevam
Reviewed
wget followed by bootefi currently fails as follows:
U-Boot> wget 20 192.168.0.30:helloworld.efi
Waiting for Ethernet connection... done.
HTTP/1.0 200 OK
Packets received 13, Transfer Successful
Bytes transferred = 12720 (31b0 hex)
U-Boot> bootefi 20
No UEFI binary known at 20
FTGMAC100 enables drivers/net/ftgmac100.c which uses
PHY_INTERFACE_MODE_NCSI, which is defined only when PHY_NCSI is enabled.
Therefore FTGMAC100 depends on PHY_NCSI. However adding such a
dependency causes a "recursive dependency detected!" message, so
add a dependency on NET instead (PHY_NCSI dep
PHY_NCSI enables drivers/net/phy/ncsi.c which calls net_loop() and
net_set_timeout_handler(). That's the legacy NET stack (as opposed to
NET_LWIP). Therefore add the dependency to Kconfig.
Signed-off-by: Jerome Forissier
Reviewed-by: Peter Robinson
Reviewed-by: Ilias Apalodimas
---
drivers/net
wget_success() is used nowhere so remove it.
Signed-off-by: Jerome Forissier
Reviewed-by: Ilias Apalodimas
Reviewed-by: Peter Robinson
---
net/wget.c | 7 ---
1 file changed, 7 deletions(-)
diff --git a/net/wget.c b/net/wget.c
index f1dd7abeff6..0e4dc5159d0 100644
--- a/net/wget.c
+++ b/n
dtsec_init_phy() is defined only with MII so add the proper conditional
in the caller code.
Signed-off-by: Jerome Forissier
Reviewed-by: Peter Robinson
---
drivers/net/fm/eth.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/drivers/net/fm/eth.c b/drivers/net/fm/e
emac.c implements cpu_eth_init() so it needs to pull the corresponding
header file.
Signed-off-by: Jerome Forissier
Reviewed-by: Tom Rini
Reviewed-by: Peter Robinson
Reviewed-by: Ilias Apalodimas
---
arch/arm/mach-omap2/omap3/emac.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm
The AT91-based platforms have a mem_init() function declared in
arch/arm/mach-at91/include/mach/at91_common.h and implemented in various
places. In preparation of the introduction of the lwIP networking library
which also has a global mem_init() function, rename the AT91 one to
at91_mem_init().
Si
Prefix the flash status codes (ERR_*) with FL_ in order to avoid clashes
with third-party libraries. Case in point: including the lwIP library
header file which defines err_enum_t as an enum with values
being ERR_*.
Signed-off-by: Jerome Forissier
Reviewed-by: Tom Rini
Reviewed-by: Ilias Apalod
When building for sandbox, self.cross is empty.
In MakeEnvironment(), CROSS_COMPILE is defined to be self.cross (with
or without a full path), optionally prefixed by the toolchain wrapper
defined in ~/.buildman. This is fine when self.cross is not empty, but
it doesn't make sense when it is:
- Eit
When CROSS_COMPILE contains multiple words, HOST_ARCH is not properly
detected and the sandbox build fail. It typically happens when using
ccache. For example:
$ make sandbox_defconfig
$ make CROSS_COMPILE="ccache x86_64-linux-gnu-" \
CC="ccache x86_64-linux-gnu-gcc"
[...]
In file incl
Miscellaneous fixes made when developing the lwIP series [1]. They are
posted separately since they make sense on their own. Subsequent
versions of the lwIP series will contain a squashed version of this one.
[1]
http://patchwork.ozlabs.org/project/uboot/list/?series=420712&state=%2A&archive=both
On Tue, Sep 03, 2024 at 08:57:24AM +0200, Stefan Roese wrote:
> On 8/29/24 10:08, Marek Behún wrote:
> > Use the i2c_eeprom miscellaneous driver for reading Turris Omnia EEPROM
> > in U-Boot proper. Keep using dm_i2c_read() in SPL build, since adding
> > the i2c_eeprom driver to SPL build increases
Enable simple-pm-bus driver to handle case where axi bus coming between PS
(fixed) part to PL (programmable) part has own clock or power domain.
That's why enable driver to be ready for this configuration.
Signed-off-by: Michal Simek
---
configs/amd_versal2_virt_defconfig | 1 +
configs/x
On lun., sept. 02, 2024 at 15:41, Quentin Schulz
wrote:
> Hi Marek,
>
> On 9/2/24 3:37 PM, Marek Vasut wrote:
>> The mmc speed command configuration option keeps showing up in
>> Kconfig directly in 'Command line interface'. Move MMC_SPEED_MODE_SET
>> under CMD_MMC to make it show up alongside t
Hi Guillaume,
Thank you for the patch.
On lun., sept. 02, 2024 at 18:31, Guillaume La Roque
wrote:
> From: Mattijs Korpershoek
>
> When CONFIG_BOOTMETH_ANDROID is set, enable Android boot flow support.
>
> To build for AM62Px for Android, we can re-use
> the am62x_a53_android.config fragment
Hi Guillaume,
Thank you for the patch.
On lun., sept. 02, 2024 at 18:31, Guillaume La Roque
wrote:
> From: Mattijs Korpershoek
>
> Beagle Play has a different boot flow than the AM62x SK EVM.
>
> AM62x SK EVM:
> 1. Boot rom reads UDA (User Data Area), looking for tiboot3
> 2. Boot rom finds t
Hi Guillaume,
Thank you for the patch.
On lun., sept. 02, 2024 at 18:31, Guillaume La Roque
wrote:
> Add Android bootflow support for AM62X SK EVM board with
> new android boot method.
Maybe add some lines here on how to enable this. I know it's in the docs
but it would be helpful to have it
On 8/29/24 10:08, Marek Behún wrote:
Users experiencing random kernel crashes due to new versions of
Marvell's DDR training algorithm can solve the issue by setting DDR
speed to 1333H.
But if kernel crashes, it has to be done in U-Boot, which is impossible
without UART connection.
In order to m
96 matches
Mail list logo
