public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Øyvind Harboe" <oyvind.harboe@zylin.com>
To: "eCos Discussion" <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] Problems with application to use lwIP
Date: Fri, 12 Oct 2007 10:33:00 -0000	[thread overview]
Message-ID: <c09652430710120333t5f2574cejfa58bd931cace48@mail.gmail.com> (raw)

I'm trying to use lwIP, but I run into problems because lwIP uses
macros, e.g. #define read(a,b,c), which screws things up. I've seen
some posts about people wishing for/thinking about making lwIP more
compatible with a "standard" eCos TCP/IP stack.

Rather than try to adapt the code that is going to use lwIP(it
currently uses eCos FreeBSD + POSIX) or changing lwIP, I was wondering
if I could somehow pull off the following:

- Use the standard include files from eCos instead of lwIP include
files so application continues to compile fine.
- Link w/lwIP only instead of trying to compile with it.

This would require adding a .c file that implemented functions that
used the lwIP include files and exported function calls that were
compatible with lwIP.

Any thoughts on this approach?

lwIP is attractive to us as it is small enough to fit into the fastest
RAM available for our project, we do have enough RAM for FreeBSD, but
it is dog slow as it needs to use DRAM instead of SRAM.

-- 
Øyvind Harboe
http://www.zylin.com - eCos ARM & FPGA  developer kit

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

             reply	other threads:[~2007-10-12 10:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-12 10:33 Øyvind Harboe [this message]
2007-10-12 12:26 ` Andrew Lunn
2007-10-12 20:08   ` Øyvind Harboe
2007-10-12 21:03     ` Andrew Lunn
2007-10-13  7:50       ` Øyvind Harboe
2007-10-13 15:06         ` Andrew Lunn

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=c09652430710120333t5f2574cejfa58bd931cace48@mail.gmail.com \
    --to=oyvind.harboe@zylin.com \
    --cc=ecos-discuss@ecos.sourceware.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 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).