Tim,
https://github.com/muvarov/u-boot/tree/master_lwip_test_v10
(branch master_lwip_test_v10)
Commit 8617b290e79e526119ccef0b0090cb220c78dd34
All later commits are experimental and I'm testing them in the CI.
And yes, this series has to apply to the current master without rejects.
BR,
Maxim.
Hi Heinrich,
On Wed, 29 Nov 2023 at 03:26, Heinrich Schuchardt wrote:
>
> On 11/28/23 20:10, Ilias Apalodimas wrote:
> > commit 239d59a65e20 ("efi_loader: reconnect drivers on failure")
> > tried to fix the UninstallProtocol interface which must reconnect
> > any controllers it disconnected by
On 2023-11-29 00:35, Szőke Kálmán Benjamin wrote:
Sorry i can not fix it, this is an average e-mail service provider
that provides the expected tech level in 2023.Please upgrade your
u-boot list website engine to able to support e-mail
formats/technologies from 2020s ages. I suggest to use
On Wed, 15 Nov 2023 13:44:15 +0100, christian.taedcke-...@weidmueller.com wrote:
> From: Christian Taedcke
>
>
> This series fixes an issue where the FAT type (FAT12, FAT16) is not
> correctly detected, e.g. when the BPB field BS_FilSysType contains the
> valid value "FAT ".
>
> [...]
On 11/28/23 20:10, Ilias Apalodimas wrote:
commit 239d59a65e20 ("efi_loader: reconnect drivers on failure")
tried to fix the UninstallProtocol interface which must reconnect
any controllers it disconnected by calling ConnectController()
in case of failure. However, the reconnect functionality
On Tue, 14 Nov 2023 14:02:44 +0300, Igor Prusov wrote:
> This series imports generic versions of ioread_rep/iowrite_rep and
> reads/writes from Linux. Some cleanup is done to make sure that all
> platforms have proper defines for implemented functions and there are no
> redefinitions.
>
>
>
Allow dm_pci_map_bar() usage on systems with CONFIG_SYS_PCI_64BIT.
Reviewed-by: Philip Oberfichtner
Signed-off-by: Moritz Fischer
---
Changes from v1:
- Fixed commit message
---
drivers/pci/pci-uclass.c | 11 +++
include/pci.h| 4 ++--
2 files changed, 13 insertions(+), 2
Hi Tim,
On Tue, Nov 28, 2023 at 9:10 PM Tim Harvey wrote:
> Fabio,
>
> You won't see this build issue with the entire series applied... only
> with the patches up to and including 'net/lwip: integrate lwIP
> library'. My point was there are points in the series where
> compilation fails which
On Tue, Nov 28, 2023 at 3:21 PM Fabio Estevam wrote:
>
> Hi Tim and Maxim,
>
> On Tue, Nov 28, 2023 at 8:05 PM Tim Harvey wrote:
>
> > Hi Maxim,
> >
> > I've tried this series on my imx8mm-venice boards and find that basic
> > ping/dhcp/tftp breaks:
> > u-boot=> net list
> > eth0 :
Sorry i can not fix it, this is an average e-mail service provider that
provides the expected tech level in 2023.Please upgrade your u-boot list
website engine to able to support e-mail formats/technologies from 2020s ages.
I suggest to use similar what Yocto project has:
Hi Tim and Maxim,
On Tue, Nov 28, 2023 at 8:05 PM Tim Harvey wrote:
> Hi Maxim,
>
> I've tried this series on my imx8mm-venice boards and find that basic
> ping/dhcp/tftp breaks:
> u-boot=> net list
> eth0 : ethernet@30be 00:d0:12:78:f8:01 active
> u-boot=> setenv ipaddr 192.168.1.1
>
On Mon, 27 Nov 2023 23:26:08 + (GMT)
Szőke Kálmán Benjamin wrote:
> It was absolutely conform, i supressed the potentional warning. Once again i
> say, i will not remove it, if you do not liket it you can remoce as a
> maintainer. My patch is ready and final. Let's do something to improve
On Mon, Nov 27, 2023 at 5:00 AM Maxim Uvarov wrote:
>
> Hello,
>
> Please find updated version of lwip patches. Changes are in the
> changelog bellow.
>
> Thank you,
> Maxim.
>
Hi Maxim,
I've tried this series on my imx8mm-venice boards and find that basic
ping/dhcp/tftp breaks:
u-boot=> net
> -Original Message-
> From: Ard Biesheuvel
> Sent: Tuesday, November 28, 2023 10:08 AM
> To: Chiu, Chasel
> Cc: Simon Glass ; devicet...@vger.kernel.org; Mark Rutland
> ; Rob Herring ; Tan, Lean Sheng
> ; lkml ; Dhaval
> Sharma ; Brune, Maximilian
> ; Yunhui Cui ;
> Dong, Guo ; Tom
On Tue, Nov 28, 2023 at 03:14:30PM -0600, Simon Glass wrote:
> Hi Tom,
>
>
> On Tue, Nov 28, 2023, 12:21 Tom Rini wrote:
>
> > On Sat, Nov 18, 2023 at 02:05:19PM -0700, Simon Glass wrote:
> >
> > > At present bootstd requires CONFIG_CMDLINE to operate. Add a new
> > > 'programmatic' boot which
On 13:40-20231128, Vishal Mahaveer wrote:
> This patch series brings in the latest board configurations for
> am62 and am62a device.
>
> Patch "board: ti: am62x/am62ax: Update virtual interrupt allocations
> in board config" is needed for booting with the latest
Hi Tom,
On Tue, Nov 28, 2023, 12:21 Tom Rini wrote:
> On Sat, Nov 18, 2023 at 02:05:19PM -0700, Simon Glass wrote:
>
> > At present bootstd requires CONFIG_CMDLINE to operate. Add a new
> > 'programmatic' boot which can be used when no command line is available.
> > For now it does almost
On Sun, 12 Nov 2023 19:58:20 -0700, Simon Glass wrote:
> The show_board_info() function was adjusted to weak so that it could be
> entirely replaced with a board-specific implementation.
>
> The intended way for boards to provide their own information is via a
> sysinfo driver. But currently
On Tue, Nov 28, 2023 at 12:41:44PM -0800, Tim Harvey wrote:
> On Tue, Nov 28, 2023 at 11:12 AM Fabio Estevam wrote:
> >
> > Hi Maxim,
> >
> > On Tue, Nov 28, 2023 at 4:07 PM Maxim Uvarov
> > wrote:
> >
> > > From this log it's a little bit different wget output. My version prints
> > > "#"
On Tue, Nov 28, 2023 at 11:12 AM Fabio Estevam wrote:
>
> Hi Maxim,
>
> On Tue, Nov 28, 2023 at 4:07 PM Maxim Uvarov wrote:
>
> > From this log it's a little bit different wget output. My version prints
> > "#" for status. So I guess it's original wget. You can spend time on
> > debugging it
Below is the consol log from trying to use mtd_debug write. It returned
immediately with a strange success message.
root@orangepizero3:~# mtd_debug write /dev/mtd0 0 0xf
/home/sysadmin/u-boot-sunxi-with-spl.bin
file_to_flash: fread, size 0xf, n 0xf
fread(): Success
I then used
Minor formatting updates to the rm board configuration file for
am62x and am62ax boards.
Signed-off-by: Vishal Mahaveer
---
board/ti/am62ax/rm-cfg.yaml | 454 +---
board/ti/am62x/rm-cfg.yaml | 445 +--
2 files changed, 326
Share the MCU GPIO interrupts between A53 core and DM R5 core. Allocating
2 instances each to A53 and DM R5.
Signed-off-by: Vishal Mahaveer
---
board/ti/am62ax/rm-cfg.yaml | 16 ++--
board/ti/am62x/rm-cfg.yaml | 16 ++--
2 files changed, 28 insertions(+), 4 deletions(-)
Update am62ax rm-cfg with allocation entries for C7x core. Following
updates are added for C7x:
- Share split BCDMA tx and rx channels between DM R5 and C7x
- Share rings for split BCDMA tx and rx channels between DM R5 and C7x
- Add Global events and Virtual interrupts for C7x
Signed-off-by:
Updates as a result of TIFS core now reserving a virtual interrupt
for enabling interrupts between DM to TIFS core. Because of this
change other virtual interrupt counts decrease by one.
Signed-off-by: Vishal Mahaveer
---
board/ti/am62ax/rm-cfg.yaml | 22 +++---
This patch series brings in the latest board configurations for
am62 and am62a device.
Patch "board: ti: am62x/am62ax: Update virtual interrupt allocations
in board config" is needed for booting with the latest TIFS and DM
firmware [1].
[1]
On Tue, 28 Nov 2023 at 16:37, wrote:
> Hi,
>
> On 27/11/2023 13:56, Maxim Uvarov wrote:
> > Hello,
> >
> > Please find updated version of lwip patches. Changes are in the
> > changelog bellow.
>
> I've ran it on the libretech-cc board, and tried to load grub over tftp,
> and I got this strange
Hi Maxim,
On Tue, Nov 28, 2023 at 4:07 PM Maxim Uvarov wrote:
> From this log it's a little bit different wget output. My version prints "#"
> for status. So I guess it's original wget. You can spend time on debugging it
> but this code will be replaced.
> With my code I tried big iso
commit 239d59a65e20 ("efi_loader: reconnect drivers on failure")
tried to fix the UninstallProtocol interface which must reconnect
any controllers it disconnected by calling ConnectController()
in case of failure. However, the reconnect functionality was wired in
efi_disconnect_all_drivers()
On Tue, 28 Nov 2023 at 22:34, wrote:
> Hi Maxim,
>
> On 27/11/2023 13:56, Maxim Uvarov wrote:
> > U-Boot recently got support for an alternative network stack using LWIP.
> > Replace tftp command with the LWIP variant while keeping the output and
> > error messages identical.
> >
> >
On Tue, 28 Nov 2023 at 17:32, Fabio Estevam wrote:
> Hi Maxim,
>
> On Mon, Nov 27, 2023 at 5:46 PM Maxim Uvarov
> wrote:
> >
> > U-Boot recently got support for an alternative network stack using LWIP.
> > Replace wget command with the LWIP variant while keeping the output and
> > error
On Sat, Nov 18, 2023 at 02:05:19PM -0700, Simon Glass wrote:
> At present bootstd requires CONFIG_CMDLINE to operate. Add a new
> 'programmatic' boot which can be used when no command line is available.
> For now it does almost nothing, since most bootmeths require the
> command line.
>
>
You are referring to a 2000 line patch so it is not 100% clear where
to look tbh.
On Tue, 21 Nov 2023 at 19:37, Chiu, Chasel wrote:
>
>
> In PR, UefiPayloadPkg/Library/FdtParserLib/FdtParserLib.c, line 268 is for
> related example code.
>
That refers to a 'memory-allocation' node, right? How
On 28.11.23 18:40, Ilias Apalodimas wrote:
Hi Heinrich
On Tue, 28 Nov 2023 at 18:30, Heinrich Schuchardt wrote:
On 28.11.23 16:45, Ilias Apalodimas wrote:
commit 239d59a65e20 ("efi_loader: reconnect drivers on failure")
tried to fix the UninstallProtocol interface which must reconnect
any
Hi Heinrich
On Tue, 28 Nov 2023 at 18:30, Heinrich Schuchardt wrote:
>
> On 28.11.23 16:45, Ilias Apalodimas wrote:
> > commit 239d59a65e20 ("efi_loader: reconnect drivers on failure")
> > tried to fix the UninstallProtocol interface which must reconnect
> > any controllers it disconnected by
All normal memory areas should be mapped as such.
We added these un-cached holes in our memory map to hack around the
remoteproc driver missing the proper cache maintenance operations.
The problem is having these non-cached memory map areas causes stability
issues later in system operation due
The Device vs Normal memory map is the same for all K3 SoCs. Merge
the SoC specific maps into one.
Signed-off-by: Andrew Davis
Reviewed-by: Nishanth Menon
Tested-by: Nishanth Menon
---
arch/arm/mach-k3/arm64-mmu.c | 228 +--
1 file changed, 2 insertions(+), 226
NR_MMU_REGIONS is a copy/paste from another platform that extends
this list later. We do not do that, so let the list be the size
of the initializer list.
Signed-off-by: Andrew Davis
Reviewed-by: Nishanth Menon
Tested-by: Nishanth Menon
---
arch/arm/mach-k3/arm64-mmu.c | 35
ATF and OPTEE regions may be firewalled from non-secure entities. To
prevent access to this area we leave a hole there in the MMU map. This
is the same idea as [0] but we complete that patch by adding the same
for AM65, J721e, J7200, and J721s2 here.
[0] commit 0688ff3ae23c ("arm: mach-k3:
Hello all,
This was an RFC as it might still break remoteproc loading, but
posted now for merge as worst case this would expose the issue
in remoteproc loading better and force someone to go fix it. :)
Changes for v2:
- Add patch adding firewall MMU hole for Jacinto devices
Changes for
On 11/27/23 9:47 AM, Nishanth Menon wrote:
On 23:04-20231123, Vignesh Raghavendra wrote:
On 11/23/2023 10:52 PM, Andrew Davis wrote:
@@ -219,16 +177,9 @@ struct mm_region am62_mem_map[] = {
}, {
.virt = 0x8000UL,
.phys = 0x8000UL,
-
On 28/11/2023 17:30, Caleb Connolly wrote:
Linux devicetrees use the "gpio-ranges" property, add support for
parsing it instead of "gpio-count" so that upstream DTs can be used with
U-Boot.
Signed-off-by: Caleb Connolly
---
arch/arm/dts/dragonboard410c.dts | 3 +--
On 28/11/2023 17:30, Caleb Connolly wrote:
The power and resin keys were implemented as GPIOs here, but their only
use would be as buttons. Avoid the additional layer of introspection and
rework this driver into a button driver.
While we're here, replace the "qcom,pm8998-pwrkey" compatible with
Hi Maxim,
On 27/11/2023 13:56, Maxim Uvarov wrote:
U-Boot recently got support for an alternative network stack using LWIP.
Replace tftp command with the LWIP variant while keeping the output and
error messages identical.
Signed-off-by: Maxim Uvarov
---
include/net/lwip.h | 13
Linux DTs stuff a value indicating if the USID is a USID or a GSID in the
reg property, the Linux SPMI driver then reads the two address cells
separately. U-boot's dev_read_addr() doesn't know how to handle this, so
use ofnode_read_u32_index() to get just the USID.
The Qcom pmic driver doesn't
The power and resin keys were implemented as GPIOs here, but their only
use would be as buttons. Avoid the additional layer of introspection and
rework this driver into a button driver.
While we're here, replace the "qcom,pm8998-pwrkey" compatible with
"qcom,pm8941-pwrkey" to match upstream
The core and chnl register ranges were swapped on SDM845. Fix it, and
fetch the register ranges by name instead of by index.
Drop the cosmetic "version" variable and clean up the debug logging.
Signed-off-by: Caleb Connolly
---
arch/arm/dts/qcs404-evb.dts| 7 +++--
Linux devicetrees use the "gpio-ranges" property, add support for
parsing it instead of "gpio-count" so that upstream DTs can be used with
U-Boot.
Signed-off-by: Caleb Connolly
---
arch/arm/dts/dragonboard410c.dts | 3 +--
arch/arm/dts/dragonboard820c.dts | 3 +--
arch/arm/dts/qcs404-evb.dts
priv->pid is uint32_t, but dev_read_addr() returns a uint64_t on arm64,
with the upper bits being used for error codes. Do error checking before
downcasting to u32 to prevent errors being silently ignored.
Reviewed-by: Sumit Garg
Signed-off-by: Caleb Connolly
---
drivers/gpio/qcom_pmic_gpio.c
This series addresses some long-standing issues with the SPMI arb
driver, the PMIC, and the PMIC GPIO. It fixes compatibility with
upstream Linux devicetrees, and simplifies pwrkey/resin support by
rewriting the pon driver to be a button driver rather than a GPIO
driver.
Existing users are
On 28.11.23 16:45, Ilias Apalodimas wrote:
commit 239d59a65e20 ("efi_loader: reconnect drivers on failure")
tried to fix the UninstallProtocol interface which must reconnect
any controllers it disconnected by calling ConnectController()
in case of failure. However, the reconnect functionality
On Tue, Nov 28, 2023 at 12:16:06PM +0900, Minkyu Kang wrote:
> Dear Tom,
>
> The following changes since commit 17e9db18f17b6cad278694d4a61df95e96bdf4f5:
>
> Merge tag 'doc-2024-01-rc3' of
> https://source.denx.de/u-boot/custodians/u-boot-efi (2023-11-11 09:22:54
> -0500)
>
> are available
On Tue, 31 Oct 2023 20:46:49 +0200, Svyatoslav Ryhel wrote:
> I would like to volunteer as Tegra SOC co-maintainer.
>
> Svyatoslav Ryhel (1):
> MAINTAINERS: Step up as co-maintainer of Tegra SOC platform
>
> MAINTAINERS | 7 +--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> [...]
Hi Robert,
On 11/28/23 16:44, Stefan Roese wrote:
Hi Robert,
On 11/28/23 11:19, Robert Marko wrote:
On Fri, Oct 20, 2023 at 12:21 PM Robert Marko
wrote:
Currently, Esspresobin FDT is being fixed up directly in
ft_board_setup()
which makes it hard to add support for any other board to be
commit 239d59a65e20 ("efi_loader: reconnect drivers on failure")
tried to fix the UninstallProtocol interface which must reconnect
any controllers it disconnected by calling ConnectController()
in case of failure. However, the reconnect functionality was wired in
efi_disconnect_all_drivers()
Hi Robert,
On 11/28/23 11:19, Robert Marko wrote:
On Fri, Oct 20, 2023 at 12:21 PM Robert Marko wrote:
Currently, Esspresobin FDT is being fixed up directly in ft_board_setup()
which makes it hard to add support for any other board to be fixed up.
So, lets just move the FDT fixup code to a
On Tue, Nov 28, 2023 at 03:35:00PM +0600, Maxim Uvarov wrote:
> On Mon, 27 Nov 2023 at 22:31, Tom Rini wrote:
>
> > On Mon, Nov 27, 2023 at 03:52:50PM +, Peter Robinson wrote:
> > > On Mon, Nov 27, 2023 at 3:32 PM Maxim Uvarov
> > wrote:
> > > >
> > > >
> > > >
> > > > On Mon, 27 Nov 2023
>> + pm8998_resin: resin {
>> + compatible =
>> "qcom,pm8941-resin";
>> + debounce = <15625>;
>> + bias-pull-up;
>> +
ab_control_store() can return an error if writing to disk fails.
In this case, we have to pass the error code to the caller.
Signed-off-by: Alexey Romanov
---
boot/android_ab.c | 18 --
1 file changed, 16 insertions(+), 2 deletions(-)
diff --git a/boot/android_ab.c
It adds the ATCWDT200 support for Andes AE350 platform.
It also enables wdt command support.
Signed-off-by: CL Wang
Signed-off-by: Randolph
---
configs/ae350_rv32_defconfig | 4
configs/ae350_rv32_spl_defconfig | 4
configs/ae350_rv32_spl_xip_defconfig | 4
This patch adds an implementation of the Andes watchdog ATCWDT200 driver.
Signed-off-by: CL Wang
Signed-off-by: Randolph
---
drivers/watchdog/Kconfig | 6 +
drivers/watchdog/Makefile| 1 +
drivers/watchdog/atcwdt200_wdt.c | 219 +++
3 files
Hi Maxim,
On Mon, Nov 27, 2023 at 5:46 PM Maxim Uvarov wrote:
>
> U-Boot recently got support for an alternative network stack using LWIP.
> Replace wget command with the LWIP variant while keeping the output and
> error messages identical.
>
> Signed-off-by: Maxim Uvarov
Do you know whether
On 27/11/2023 19:18, Tom Rini wrote:
On Mon, Nov 27, 2023 at 06:56:58PM +0600, Maxim Uvarov wrote:
bootefi code relays in internal variable then to filesize environment.
lwip tftp do not update this variable. For not I update test to provide
correct size.
Signed-off-by: Maxim Uvarov
This
This is a debug command to monitor the retention state of the data on
the array. The command needs a duplication of the mtd_read_oob()
function to actually return the maximum number of bitflips encountered
while reading the page. We could write a specific implementation for the
Sunxi driver but
Hi,
On 27/11/2023 13:56, Maxim Uvarov wrote:
Hello,
Please find updated version of lwip patches. Changes are in the
changelog bellow.
I've ran it on the libretech-cc board, and tried to load grub over tftp,
and I got this strange EFI boot error:
Introduce support for Conclusive WHLE-LS1088A Single Board Computer.
Co-developed-by: Jakub Klama
Signed-off-by: Jakub Klama
Signed-off-by: Artur Rojek
---
v3: new patch
arch/arm/Kconfig | 19 ++
arch/arm/dts/Makefile | 1 +
Introduce support for Conclusive WHLE-LS1046A Single Board Computer.
Co-developed-by: Jakub Klama
Signed-off-by: Jakub Klama
Signed-off-by: Artur Rojek
---
v3: no change
v2: - drop non-DM_ETH case
- clean-up defines in configs/whle_ls1046a.h: remove unneeded ones,
move others to
From: Jakub Klama
Some boards keep their environment on MMC storage within an ext4
partition.
Signed-off-by: Jakub Klama
Signed-off-by: Artur Rojek
Reviewed-by: Tom Rini
---
v2-v3: no change
arch/arm/cpu/armv8/fsl-layerscape/cpu.c | 5 +
1 file changed, 5 insertions(+)
diff --git
Hi all,
this is v3 of the WHLE-LS1 support.
The major change in this version is addition of WHLE-LS1088A board
support, next to the WHLE-LS1046A found in previous iterations of this
series.
Patch [1/3] and [2/3] remain unchanged.
Patch [3/3] introduces WHLE-LS1088A board support.
Artur Rojek
On Fri, Oct 20, 2023 at 12:21 PM Robert Marko wrote:
>
> Currently, Esspresobin FDT is being fixed up directly in ft_board_setup()
> which makes it hard to add support for any other board to be fixed up.
>
> So, lets just move the FDT fixup code to a separate function and call it
> if compatible
On Mon, 27 Nov 2023 at 22:31, Tom Rini wrote:
> On Mon, Nov 27, 2023 at 03:52:50PM +, Peter Robinson wrote:
> > On Mon, Nov 27, 2023 at 3:32 PM Maxim Uvarov
> wrote:
> > >
> > >
> > >
> > > On Mon, 27 Nov 2023 at 20:08, Tom Rini wrote:
> > >>
> > >> On Mon, Nov 27, 2023 at 08:06:23PM
Hi Simon,
On 12:05-20231106, Andrew Davis wrote:
> On 11/6/23 11:47 AM, Simon Glass wrote:
> > Hi Andrew,
> >
> > On Mon, 6 Nov 2023 at 10:27, Andrew Davis wrote:
> > >
> > > On 11/6/23 9:31 AM, Tom Rini wrote:
> > > > On Mon, Nov 06, 2023 at 11:23:51AM +0530, Manorit Chawdhry wrote:
> > > > >
On 27/11/2023 16:43, Michael Nazzareno Trimarchi wrote:
> Hi dario
>
> On Mon, Nov 27, 2023 at 3:00 PM Leto, Enrico wrote:
>>
>> Hi,
>>
>> Works on my draco thuban AM335x based boards booting from NAND with ECC BCH8
>> code.
>>
>> Tested-by: Enrico Leto
>>
>> Thanks
>>
>>
>>> -Original
Hi Neha,
$sub: s/j721e/j721s2/
On 12:50-20231128, Neha Malcom Francis wrote:
> Switch to using bootstd. Note that with this change, we will stop using
> distro_bootcmd and instead depend entirely on bootflow method of
> starting the system up.
>
> Also config_distro_bootcm
74 matches
Mail list logo
