From: Andrew Lunn <andrew@lunn.ch>
To: ?yvind Harboe <oyvind.harboe@zylin.com>
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Problems with application to use lwIP
Date: Sat, 13 Oct 2007 15:06:00 -0000 [thread overview]
Message-ID: <20071013150608.GA24338@lunn.ch> (raw)
In-Reply-To: <c09652430710130050v54635dd5i8e382b45d809f9f2@mail.gmail.com>
> > Do you actually need net/common?
>
> That's where tftpd is.
>
> Perhaps tftpd does not belong in net/common?
Or you want to add cdl so you can compile individual parts.
> Index: io/eth/current/cdl/eth_drivers.cdl
> ===================================================================
> RCS file: /cvs/ecos/ecos/packages/io/eth/current/cdl/eth_drivers.cdl,v
> retrieving revision 1.20
> diff -u -r1.20 eth_drivers.cdl
> --- io/eth/current/cdl/eth_drivers.cdl 20 Mar 2003 15:44:39 -0000 1.20
> +++ io/eth/current/cdl/eth_drivers.cdl 13 Oct 2007 07:46:13 -0000
> @@ -174,7 +174,7 @@
> cdl_component CYGPKG_IO_ETH_DRIVERS_STAND_ALONE {
> display "Support for stand-alone network stack."
> flavor bool
> - active_if !CYGPKG_NET
> + active_if !CYGPKG_NET&&!CYGPKG_NET_LWIP
> requires CYGINT_ISO_STRING_MEMFUNCS
> default_value 1
> compile stand_alone/eth_drv.c
My first feeling, without looking at the code, is that this is
wrong. lwip does compile with Ethernet drivers the last time i
tried...
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2007-10-13 15:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 10:33 Øyvind Harboe
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 [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=20071013150608.GA24338@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=oyvind.harboe@zylin.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).