mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: barebox@lists.infradead.org, Sascha Hauer <sha@pengutronix.de>,
	Jules Maselbas <jmaselbas@kalray.eu>
Subject: Re: [PATCH 1/1] Documentation: devel: add new project ideas section
Date: Mon, 21 Feb 2022 14:54:54 +0100	[thread overview]
Message-ID: <070a17f9-d2c0-d58d-abca-29defd04023b@pengutronix.de> (raw)
In-Reply-To: <20220219002518.54e7eec76ca0e716131f07c5@gmail.com>

On 18.02.22 22:25, Antony Pavlov wrote:
> On Thu, 17 Feb 2022 09:27:14 +0100
> Ahmad Fatoum <a.fatoum@pengutronix.de> wrote:
> 
> Hi!
> 
> ...
> 
>> +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 http://lists.infradead.org/pipermail/barebox/2015-June/thread.html#23749
> and https://github.com/frantony/barebox/tree/20190707.picotcp
> 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.

Ye, I saw that at your Github fork. lwIP was Sascha's suggestion.
Jules also has hacked a TCP stack into barebox. If we get an applicant,
I will suggest they reach out to you.

Are you on IRC btw? There's a matrix channel bridged there now, which
you can use instead of setting up a bouncer.

Cheers,
Ahmad

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


-- 
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 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox


  reply	other threads:[~2022-02-21 14:06 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
2022-02-21 13:54     ` Ahmad Fatoum [this message]
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:
  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=070a17f9-d2c0-d58d-abca-29defd04023b@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=antonynpavlov@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=jmaselbas@kalray.eu \
    --cc=sha@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