All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alessandro Rubini <rubini-list@gnudd.com>
To: antonynpavlov@gmail.com
Cc: barebox@lists.infradead.org
Subject: Re: TODO: Rewrite network stack.
Date: Mon, 5 May 2014 14:29:44 +0200	[thread overview]
Message-ID: <20140505122944.GA1567@mail.gnudd.com> (raw)
In-Reply-To: <20140505145512.133932fc3ee2247b660638c2@gmail.com>

> The most notable is lwIP (http://savannah.nongnu.org/projects/lwip/).

I'm not happy at all about this code base, it looks quite ugly and
old-fashioned. It's not the barebox kind of quality. I'd stay with the
current code rather than lwip, despite the number of users.

If any, I'd evaluate picotcp (https://github.com/tass-belgium/picotcp).

/alessandro

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

  reply	other threads:[~2014-05-05 12:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-05 10:55 TODO: Rewrite network stack Antony Pavlov
2014-05-05 12:29 ` Alessandro Rubini [this message]
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

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=20140505122944.GA1567@mail.gnudd.com \
    --to=rubini-list@gnudd.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.