GSoC 2012

[Kevin Polulak]

I've begun working on my proposal. Right now, I'm filling out all the
general information like the project description and work experience. I
want to have it so that everything is filled out except for the timeline.
At that point, I'll put it up on Google Docs and begin breaking the project
down into smaller tasks. I should have it up later tonight.

To begin identifying the general deliverables of the project, I'm looking
through the current LWIP port at the moment and I have a few questions. I'm
a little confused by all the ports in contrib-20050213.tgz. There are ports
for different operating systems like eCos and UNIX. Why are these here?
Shouldn't there only be one: RTEMS? Why would a port of LWIP for RTEMS
include ports for other unrelated operating systems? Also, why is msvc6
there? It's not even an operating system to begin with.

How is it possible to make LWIP portable across different architectures?
Isn't LWIP high-level enough that it doesn't rely on architecture-dependent
features? Refer to the RTEMS architecture
diagram<http://www.rtems.org/wiki/index.php/Media:RTEMSArchitecture.png>on
the wiki. LWIP is at the same abstraction level as the BSD stack since
they're supposed to be freely interchangeable. Wouldn't something at the
highest level of abstraction not be concerned with architecture-specific
features?

How do I build RTEMS so that it uses LWIP instead of the BSD stack? I'm
going to need to be able to run test applications like the CHARGEN service
in the current port. I would like to set up an environment so that I can
easily test two communicating applications as soon as possible. That way I
can better gauge how long things will take when writing my proposal
timeline.

-- 
- Kevin Polulak (soh_cah_toa)
- http://cybercrud.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20120324/b9efa7f0/attachment-0001.html>