From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Marc-François LUCCA-DANIAU" <mfld.fr@gmail.com>
Cc: ELKS <Linux-8086@vger.kernel.org>
Subject: Re: Question on ELKS networking maturity
Date: Mon, 20 Feb 2017 15:16:27 +0000 [thread overview]
Message-ID: <20170220151627.059f65a5@www.etchedpixels.co.uk> (raw)
In-Reply-To: <CACpuWUnAtCnD2oTHG3CLPEAQMNa0m0gU+HNFLVoyJr7N4s+Nuw@mail.gmail.com>
It got to the
"gee it now and then makes a working connection"
state.
It would be far more effective to replace it with uIP or LWIP I think
than try and debug it. That's not to say you shouldn't try and make it
work if you ae going to enjoy the challenge.
Alan
prev parent reply other threads:[~2017-02-20 15:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 11:49 Question on ELKS networking maturity Marc-François LUCCA-DANIAU
2017-02-20 12:57 ` Jody Bruchon
2017-02-20 13:41 ` Georg Potthast 2
2017-02-20 15:16 ` Alan Cox [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=20170220151627.059f65a5@www.etchedpixels.co.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Linux-8086@vger.kernel.org \
--cc=mfld.fr@gmail.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).