This is the mail archive of the ecos-discuss@sourceware.cygnus.com mailing list for the eCos project. See the eCos home page for more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
>>>>> "Jay" == Jay Lepreau <lepreau@cs.utah.edu> writes: >> Is anyone interested in working on an open TCP/IP stack for >> eCos? Jay> It probably would take very little effort to get the OSKit's Jay> TCP/IP stack working in eCos, because one of the OSKit's Jay> goals is that each component not only be entirely separable Jay> and optional, but be able to fit into *other* operating Jay> systems and environments. Jay> Copious docs, examples, papers and source available at Jay> http://www.cs.utah.edu/flux/oskit/ . <snip> Jay> It's written in C, uses autoconf, the GNU toolchain, supports Jay> ELF and a.out on the x86. Many components export the COM Jay> object model (scary sounding I know, but it's really just a Jay> glorified function table, so it's fast). You can debug on top Jay> of Unix or use remote gdb. In some ways eCos and the OSKit Jay> overlap but in more ways they are complementary. Good things Jay> could be done with them together. All true, and OSKit is certainly worth a look. However readers should also be aware that at least some parts of the software are GPL'd, which would be a problem for many embedded systems developers. See http://www.cs.utah.edu/flux/oskit/LICENSE for details. Bart Veer // eCos net maintainer