This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: tftp lwIP and SLIP
- From: Jani Monoses <jani at iv dot ro>
- To: ecos-discuss at ecos dot sourceware dot org
- Date: Wed, 14 Apr 2004 18:42:47 +0300
- Subject: Re: [ECOS] tftp lwIP and SLIP
- References: <1081950438.31910.7.camel@famine>
> Is there a particular reason why tftp is part of the "net" package?
I think the reason is that the "NET package" is ecos is/was synonimous
with 'one of the BSD derived stacks'.
tftp sntp httpd microwindows and other network code were written
to work with the bsd stacks. Making them work with lwip would mean
doing:
1) all the cdl work to at least allow them to be selectable together and
separating the idea of TCP/IP and BSD socket from the specific
implementation.(2 years ago the first such change was adding a config
option to mean interrupt support in eth drivers != CYGPKG_NET) so lwip
could work in interrupt mode
2) where lwip can not handle the features requested (there are many
still missing) implement those.
step 0 would be including lwip in CVS so there's a codebase people can
base their patches on. Of course they can do it against savannah but
since it's not 'offcial' it tends to encourage quick private hacks
instead of clean solutions.
Jani
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss