From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: TODO: Rewrite network stack.
Date: Thu, 8 May 2014 09:32:11 +0200 [thread overview]
Message-ID: <20140508073211.GE28564@pengutronix.de> (raw)
In-Reply-To: <20140505132240.GX5858@pengutronix.de>
On Mon, May 05, 2014 at 03:22:40PM +0200, Sascha Hauer wrote:
> On Mon, May 05, 2014 at 02:55:12PM +0400, Antony Pavlov wrote:
> > Hi!
> >
> > I have inspected TODO file from barebox repo. Here is a quote:
> >
> > [ ] Rewrite network stack. The one-loop-for-all-protocols stack is just too
> > ugly and big and uses thousands of global variables. Identify common
> > functions and make a loop per network protocol
> >
> > There is no much tiny TCP/IP stack candidates for porting to barebox.
> > The most notable is lwIP (http://savannah.nongnu.org/projects/lwip/).
> >
> > See "project that use lwIP" list here: http://lwip.wikia.com/wiki/Projects_that_use_lwIP
> >
> > lwip code is BSD-licensed. Is it possible to use lwip code in barebox?
> >
> > --
> > Best regards,
> > Antony Pavlov
> >
> > P.S. Anyway TODO file from barebox repo is outdated (last change Jul 22 2010).
>
> Indeed. Maybe we should add the following item to it.
>
> Sascha
>
> diff --git a/TODO b/TODO
> index 6350799..59fdade 100644
> --- a/TODO
> +++ b/TODO
> @@ -76,6 +76,7 @@ TODO
> devices should be represented as a hierarchical tree in /dev
> [ ] Work out, how to mount driver on PCI devices. The mechanism should be
> transparent to the driver code.
> +[ ] remove this file. It doesn't contain much useful information.
I took this patch, removed the file and wanted to move this entry below
DONE. This resulted in a git conflict. Please advise.
Uwe
>
> DONE
> ----
>
> --
> Pengutronix e.K. | |
> Industrial Linux Solutions | http://www.pengutronix.de/ |
> Peiner Str. 6-8, 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
>
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2014-05-08 7:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 10:55 Antony Pavlov
2014-05-05 12:29 ` Alessandro Rubini
2014-05-05 13:08 ` Antony Pavlov
2014-05-08 12:43 ` Jean-Christophe PLAGNIOL-VILLARD
2014-05-08 17:20 ` Antony Pavlov
2014-05-05 13:22 ` Sascha Hauer
2014-05-08 7:32 ` Uwe Kleine-König [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=20140508073211.GE28564@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--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