From: Sascha Hauer <s.hauer@pengutronix.de>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: barebox@lists.infradead.org
Subject: barebox + picotcp
Date: Mon, 3 Jun 2024 19:09:40 +0200 [thread overview]
Message-ID: <Zl341MMAYanIfGAt@pengutronix.de> (raw)
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?
Regards
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next reply other threads:[~2024-06-03 17:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 17:09 Sascha Hauer [this message]
2024-06-07 0:47 ` Antony Pavlov
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=Zl341MMAYanIfGAt@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.org \
/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