From: Antony Pavlov <antonynpavlov@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: barebox + picotcp
Date: Fri, 7 Jun 2024 03:47:17 +0300 [thread overview]
Message-ID: <20240607034717.a55d06b83aecfe8088077d88@gmail.com> (raw)
In-Reply-To: <Zl341MMAYanIfGAt@pengutronix.de>
On Mon, 3 Jun 2024 19:09:40 +0200
Sascha Hauer <s.hauer@pengutronix.de> wrote:
Hi Sascha!
> Hi Antony,
>
> I am currently playing with your barebox picotcp integration in order to
> get it into mainline. I am currently on your picotcp v2.1 branch and
> noticed you had to disable TCP support. I wonder if v2.1 is the way
> forward or if it's the v1.7 based branch instead. The v2.1 branch is
> newer, but also hasn't seen any activity for multiple years now. One of
> the main features of the v2.1 branch is that it introduces
> PICO_SUPPORT_TICKLESS, from which I don't exactly know if we want/need
> it, but what I do see is that the stack won't compile when this option
> is enabled.
>
> Do you have any thoughts what could be the way forward?
I suppose that most beneficial picotcp feature is TCP support.
Working with picotcp v1.7 I have used tcp examples from
https://github.com/tass-belgium/picotcp-modules
It looks like that the tcp code does not work "as-is" after switching from
v1.7 to v2.1 so I have disabled it.
At the moment I have no good idea on picotcp integration next step.
This year I have faced with iPXE (https://ipxe.org/) as a user.
iPXE just works. It supports TCP and IPv6. It uses GPLv2.
May be iPXE would be a better choice?
However, I have not looked at the iPXE code yet.
--
Best regards,
Antony Pavlov
prev parent reply other threads:[~2024-06-07 0:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 17:09 Sascha Hauer
2024-06-07 0:47 ` Antony Pavlov [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=20240607034717.a55d06b83aecfe8088077d88@gmail.com \
--to=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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