lwip-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lwip-users] LWIP -> Microblaze


From: Sathya Thammanur
Subject: Re: [lwip-users] LWIP -> Microblaze
Date: Wed, 26 Apr 2006 10:40:54 -0700

Hi Lachlan,
Xilinx provides different ethernet MAC hardware configurations and hence you will find different xemacif_*.c file under contrib/ports/v2pro area.  As of fixing the file, I will take a stab at this one and get back to you.

I have always see that RAW API performs much better than the Sockets API mode. However, writing a program using the RAW API takes quite a bit of time. It is always performance vs ease-of-use in programming which is what the RAW vs Sockets mode offers. Depending on the requirement you could choose to use one vs the other.


Sathya


On 4/26/06, Christiaan Simons <address@hidden> wrote:
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
address@hidden
http://lists.nongnu.org/mailman/listinfo/lwip-users


reply via email to

[Prev in Thread] Current Thread [Next in Thread]