public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: Sergei Gavrikov <sergei.gavrikov@gmail.com>
To: Simon Kallweit <simon.kallweit@intefo.ch>
Cc: ecos-devel@ecos.sourceware.org
Subject: Re: lwip 1.3.1 testing
Date: Fri, 21 Aug 2009 18:43:00 -0000	[thread overview]
Message-ID: <20090821184336.GA24882@ubuntu.local> (raw)
In-Reply-To: <4A8E48C2.10802@intefo.ch>

On Fri, Aug 21, 2009 at 09:12:02AM +0200, Simon Kallweit wrote:
> Hi
>
> If anyone volunteers, I'd be glad if you could test the current state of  
> the lwip 1.3.1 port. It has been updated with the latest changes from  
> the 1.3.1 release. I currently left in my changes for SLIP and PPP (see  
> my last mail for details), but this should not matter for testing. The  
> package can be installed by just replacing the existing lwip and eth  
> drivers packages.
>
> http://download.westlicht.ch/lwip-20090821.tar.gz

Hi Simon,

I need a bit clarification from you. Does it mean that we should try
'lwip_eth' template only on real HW? I stub on 'left in' phrase. Did
your SLIP/PPP hack leave this tarball? Does it mean what tests of SLIP,
for example, will be useless just now?

And more, could you, please, post a reason ECM (the legal eCos minimal
configuration file for such a called 'Sequential' mode)? I hope you have
something for synthetic target, IMO, it would help to setup tests more
quickly, I see that real hardware will be to require the uploads and
debugging via serial (at the least for my target), because, I will need
to test the net tests. Well, that would be great and that will save a
time for "digging"/uploading.

If you did not save own ECM(s), the simplest question is, Did you use
DHCP or static IPs in your tests?

I'm going to try your lwip port on ARM-7 (LE) this weekend.

FYI: My first compile-stop did occur in simple.c, then I send a patch.

Thank you.

Sergei

> Thanks
> Simon

  parent reply	other threads:[~2009-08-21 18:43 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-21  7:11 Simon Kallweit
2009-08-21  7:43 ` John Dallaway
2009-08-21  9:12   ` Edgar Grimberg
2009-08-21 18:43 ` Sergei Gavrikov [this message]
2009-08-24 20:18   ` Sergei Gavrikov
2009-08-25  6:09     ` Simon Kallweit
2009-08-25  7:41       ` Simon Kallweit
2009-08-25 12:08         ` Sergei Gavrikov
2009-08-25 20:33           ` Sergei Gavrikov
2009-08-26  6:38             ` Simon Kallweit
2009-08-26  8:43               ` Sergei Gavrikov
2009-08-26 20:46               ` Sergei Gavrikov
2009-08-27  7:17                 ` Simon Kallweit
2009-08-27  8:03                   ` Sergei Gavrikov
2009-10-25 16:46         ` John Dallaway
2009-10-26 13:00           ` Simon Kallweit
2009-10-26 13:54             ` John Dallaway
2009-10-26 14:29               ` Simon Kallweit
2009-10-26 17:13                 ` John Dallaway
2009-10-27 13:06                   ` Simon Kallweit
2009-11-20 10:24                     ` John Dallaway
2009-12-07 13:41                       ` Simon Kallweit
2009-12-17 10:45                         ` John Dallaway
2010-01-19 12:07                         ` John Dallaway

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=20090821184336.GA24882@ubuntu.local \
    --to=sergei.gavrikov@gmail.com \
    --cc=ecos-devel@ecos.sourceware.org \
    --cc=simon.kallweit@intefo.ch \
    /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).