On Mon, Aug 26, 2024 at 01:45:10PM +0200, Jerome Forissier wrote:
On 8/23/24 23:18, Tom Rini wrote:
On Fri, Aug 23, 2024 at 03:48:04PM +0200, Jerome Forissier wrote:
This is a rework of a patch series by Maxim Uvarov: "net/lwip: add lwip library for the network stack" [1]. The goal is to introduce the lwIP TCP/IP stack [2] [3] as an alternative to the current implementation in net/, selectable with Kconfig, and ultimately keep only lwIP if possible. Some reasons for doing so are:
- Make the support of HTTPS in the wget command easier. Javier T. and
Raymond M. (CC'd) have some additional lwIP and Mbed TLS patches to do so. With that it becomes possible to fetch and launch a distro installer such as Debian etc. using a secure, authenticated connection directly from the U-Boot shell. Several use cases:
- Authentication: prevent MITM attack (third party replacing the
binary with a different one)
- Confidentiality: prevent third parties from grabbing a copy of the
image as it is being downloaded
- Allow connection to servers that do not support plain HTTP anymore
(this is becoming more and more common on the Internet these days)
- Possibly benefit from additional features implemented in lwIP
- Less code to maintain in U-Boot
As an odd thing, the series leads to ethernut5 failing to build, strangely over the RTC driver it uses, for me.
Weird.
I did have to manually merge the CMD_WGET related patch,
Weird.
but I don't think that was what went wrong here.
Could you try to build from GitHub perhaps? Branch https://github.com/jforissier/u-boot/tree/to-upstream/v9 builds fine here:
$ ./tools/buildman/buildman ethernut5 Building current source for 1 boards (1 thread, 24 jobs per thread) arm: w+ ethernut5 +===================== WARNING ====================== +This board does not use CONFIG_DM_I2C (Driver Model +for I2C drivers). Please update the board to use +CONFIG_DM_I2C before the v2022.04 release. Failure to +update by the deadline may result in board removal. +See doc/develop/driver-model/migration.rst for more info. +==================================================== 0 1 0 /1 ethernut5
I think you weren't on latest next branch when you posted v9, and that's at least the merge conflict. I see the platform builds on your branch as well, but fails still, on mine.