From: Jerome Forissier <jerome.forissier@linaro.org>
To: Michal Simek <michal.simek@amd.com>,
u-boot@lists.denx.de, git@xilinx.com
Cc: Adriano Cordova <adrianox@gmail.com>,
Anand Moon <linux.amoon@gmail.com>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Joe Hershberger <joe.hershberger@ni.com>,
Marek Vasut <marek.vasut+renesas@mailbox.org>,
Ramon Fried <rfried.dev@gmail.com>, Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH] net: Kconfig: Select DM_RNG for LWIP
Date: Tue, 4 Feb 2025 16:49:47 +0100 [thread overview]
Message-ID: <cd384aa6-c4fd-41ea-a092-8dbd4059fe0f@linaro.org> (raw)
In-Reply-To: <e1dddae3-d44d-4b76-a1a1-a30e19e6c3ed@amd.com>
On 2/4/25 12:22, Michal Simek wrote:
>
>
> On 2/3/25 16:03, Michal Simek wrote:
>> LWIP wget.c/mbedtls_hardware_poll() is calling dm_rng_read() but dependency
>> is not recorded anywhere that's why select DM_RNG when LWIP stack i used.
>>
>> Signed-off-by: Michal Simek <michal.simek@amd.com>
>> ---
>>
>> net/Kconfig | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/net/Kconfig b/net/Kconfig
>> index 24508026200d..6c684624fd6f 100644
>> --- a/net/Kconfig
>> +++ b/net/Kconfig
>> @@ -249,6 +249,7 @@ config WGET
>> select PROT_TCP if NET
>> select PROT_TCP_LWIP if NET_LWIP
>> select PROT_DNS_LWIP if NET_LWIP
>> + select DM_RNG if NET_LWIP
>> help
>> Selecting this will enable wget, an interface to send HTTP requests
>> via the network stack.
>
> Just a summary. Jerome and Ilias will look at solving this dependency in C file not to have this dependency listed. WGET will work without RNG device but HTTPS won't work. There is also connection to MBEDTLS which will be handled.
>
> Thanks,
> Michal
Superseded by https://lists.denx.de/pipermail/u-boot/2025-February/579396.html.
Thanks,
--
Jerome
prev parent reply other threads:[~2025-02-04 15:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 15:03 [PATCH] net: Kconfig: Select DM_RNG for LWIP Michal Simek
2025-02-03 15:13 ` Ilias Apalodimas
2025-02-03 15:22 ` Michal Simek
2025-02-03 16:17 ` Ilias Apalodimas
2025-02-03 15:13 ` Jerome Forissier
2025-02-04 11:22 ` Michal Simek
2025-02-04 15:49 ` Jerome Forissier [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cd384aa6-c4fd-41ea-a092-8dbd4059fe0f@linaro.org \
--to=jerome.forissier@linaro.org \
--cc=adrianox@gmail.com \
--cc=git@xilinx.com \
--cc=ilias.apalodimas@linaro.org \
--cc=joe.hershberger@ni.com \
--cc=linux.amoon@gmail.com \
--cc=marek.vasut+renesas@mailbox.org \
--cc=michal.simek@amd.com \
--cc=rfried.dev@gmail.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox