Hi Lachlan, > I need to clarify that Im using Xilinx Micro Kernel and using the MAC in > Interrupt Mode so the acutaly contrib file Im after is > Xemacif_intr_xmk.c. (I believe this is copied and renamed as xemacif.c > during the libgen process).
Ah, I was wondering where to look. The line number you mentioned was beyond EOF. > My device implements a web site very similar to that of a residential > gateway device, however the device does not rely on the network connection > for any serious amounts of data transfer. > > In your opinion, would I be better looking at using the RAW_API? Well, the raw-API is a little more difficult to use since it has an event driven nature. You need to create your own thread and timers for handling these events. You can read more about this in lwip/doc/rawapi.txt This code is currently maintained by about 3 to 4 project members. The socket + sequential API is easier to use but is pretty much unmaintained nowadays. I was lost trying to fix some TCP problems and some other users only came up with useless quick-and-dirty hacks. Note the example http server uses the sequential API. It is really up to you. We (Axon) use the raw-API (the files in lwip/src/core/) and forget about the files in lwip/src/api. Christiaan Simons Hardware Designer Axon Digital Design http://www.axon.tv _______________________________________________ lwip-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lwip-users
