From: Sergei Gavrikov <sergei.gavrikov@gmail.com>
To: John Dallaway <john@dallaway.org.uk>
Cc: Simon Kallweit <simon.kallweit@intefo.ch>,
ecos-devel@ecos.sourceware.org
Subject: Re: lwIP port status
Date: Wed, 19 Aug 2009 09:21:00 -0000 [thread overview]
Message-ID: <20090819092259.GA16837@sg-ubuntu.local> (raw)
In-Reply-To: <4A8BA58D.8020805@dallaway.org.uk>
On Wed, Aug 19, 2009 at 08:11:09AM +0100, John Dallaway wrote:
> I can certainly test on an x86 PC target. I think Sergei Gavrikov has
> also been experimenting with your port (probably on ARM). Are there any
> volunteers to perform a basic sanity check of the eCos port on a
> big-endian target?
Hello John, Simon
Unfortunately, I ran in some issues when I tried lwip-20090722 on ARM
http://ecos.sourceware.org/ml/ecos-discuss/2009-07/msg00223.html It was
not possible to build lwip tests because new package had not a few
interface functions are used by io/eth/lwip/current/src/eth_drv.c
lwip_set_addr(), lwip_dhcp_init(), lwip_dsr_stuff(). Old eCos lwip
package has those implementations. Perhaps, I missed something. May be I
have to implement those in HAL? AFAIR I tweaked something in simple.c to
compile lwip_tcpip itself. My "memory sticks" are at home. May be I had
installed/built the package/tests in a wrong way. I used eCos CVS. The
steps were
rm -r $ECOS_REPOSITORY/net/lwip_tcpip
cp -a net/lwip_tcpip $ECOS_REPOSITORY/net
ecosconfig new <target> lwip_eth
...
Well, I did stop my attempts then. Waiting for new Simon stuff. Simon,
if I missed some things, forgive my stupidity. Both, thank you for your
persistence and your efforts!
Regards
Sergei
next prev parent reply other threads:[~2009-08-19 9:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-18 14:41 Simon Kallweit
2009-07-22 10:34 ` MaxiD
2009-07-22 11:22 ` Simon Kallweit
2009-08-18 16:59 ` John Dallaway
2009-08-18 17:33 ` Simon Kallweit
2009-08-19 7:11 ` John Dallaway
2009-08-19 9:21 ` Sergei Gavrikov [this message]
2009-08-19 12:11 ` Simon Kallweit
2009-08-19 12:10 ` Simon Kallweit
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=20090819092259.GA16837@sg-ubuntu.local \
--to=sergei.gavrikov@gmail.com \
--cc=ecos-devel@ecos.sourceware.org \
--cc=john@dallaway.org.uk \
--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).