mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Antony Pavlov <>
To: Ahmad Fatoum <>
Cc:, Sascha Hauer <>
Subject: Re: [PATCH 1/1] Documentation: devel: add new project ideas section
Date: Sat, 19 Feb 2022 00:25:18 +0300	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Thu, 17 Feb 2022 09:27:14 +0100
Ahmad Fatoum <> wrote:



> +Update barebox networking stack for IPv6 support
> +================================================
> +
> +Skills: C, Networking
> +
> +The barebox network stack is mainly used for TFTP and NFSv3 (over UDP) boot.
> +Most embedded systems barebox runs on aren't deployed to IPv6 networks yet,
> +so it's the right time now to future-proof and learn more about networking
> +internals. One major complication with IPv6 support is neighbor discovery
> +protocols that require networking to be possible "in the background".
> +barebox' recent improvements of resource sharing and cooperative scheduling
> +makes it possible to integrate an IPv6 stack, e.g. lwIP.

Several years ago I have tried to integrate picotcp network stack into barebox,
please see
This work can be revived after current picotcp state of affairs investigation.

> +There are also community patches to integrate a TCP stack into barebox.
> +These can be evaluated as time allows.

picotcp supports both IPv6 and TCP.

> +This project does not require dedicated hardware. QEMU or barebox built
> +to run under Linux (sandbox) may be used.
> +

Best regards,
  Antony Pavlov

barebox mailing list

  reply	other threads:[~2022-02-18 21:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-17  8:27 [PATCH 0/1] Applying barebox for Google Summer of Code 2022 Ahmad Fatoum
2022-02-17  8:27 ` [PATCH 1/1] Documentation: devel: add new project ideas section Ahmad Fatoum
2022-02-18 21:25   ` Antony Pavlov [this message]
2022-02-21 13:54     ` Ahmad Fatoum
2022-02-21 13:52 ` [PATCH 0/1] Applying barebox for Google Summer of Code 2022 Ahmad Fatoum
2022-03-06 19:19   ` Ahmad Fatoum

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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