Re: [lwip-users] port LwIP 1.3.0 to uC/OS-II with powerpc

[address@hidden]

That part of the port (as it is in cc.h, which stands for C-compiler, I 
guess) depends on the compiler you are using. As you are using gcc, I 
guess you can take the linux port (which also uses gcc) as a starter.

ATTENTION: the packing is a crucial part of the port: if it is not done 
correctly, lwIP will not be able to access the network headers in the 
packets correctly.

The linux port is available in the contrib ZIP available in the download 
section.


Simon



Kevin wrote:
> Hi, Simon:
>
> Thank you very much for the guidance: I am almost get there following 
> your suggestion.
>
> One thing I am concerning is that I got lots of warning associating 
> with "PACK_STRUCT_FIELD".
>
> I checked the cc.h and find this line:
> #define PACK_STRUCT_FIELD(x) x
>
> I think this line doesn't do any packing on 'x' as it claimed. In my 
> opinion, this line should be:
> #define PACK_STRUCT_FIELD(x) x __attribute__((packed))
>
> However, if I change it this way, I got lots of warnings as below:
>
> /lwip130/src/lwip-1.3.0/src/include/ipv4/lwip/ip.h:135: warning: 
> 'packed' attribute ignored for field of type 'struct ip_addr'
> /lwip130/src/lwip-1.3.0/src/include/ipv4/lwip/ip.h:136: warning: 
> 'packed' attribute ignored for field of type 'struct ip_addr'
>
> Could you please give me a help on why this warning and how I can get 
> rid of it?
>
> I am using powerpc-eabi-gcc and powerpc405.
>
> Thank you!
>
> Regards,
> Kevin
>
>
>
> On Sun, Jun 28, 2009 at 3:34 AM, address@hidden 
> <mailto:address@hidden> <address@hidden <mailto:address@hidden>> 
> wrote:
>
>     Kevin wrote:
>
>         Hi, Simon:
>
>         You mentioned "there are ports for uC/OS-II available on the
>         web", are they ports for lwip130? May I have a link to this port?
>
>         I found one for lwip110 and since lwip130 changed a lot from
>         lwip110, I am not sure how hard to move from 110 to 130 port
>         on uc/os-ii. Do I have to create new sys_arch.c? Any need to
>         touch api_lib.c and api_msg.c?
>
>
>     Oh, I didn't think of that. I used the port myself, but that was
>     with 1.2.0 and I think I didn't have to change anything. You might
>     have to change sys_arch.c and -.h as well as cc.h. For a port, you
>     *never* must change any file of the core lwIP code, so no, you
>     don't need to touch api_lib.c and api_msg.c!
>
>     I would just try to compile with the 1.1.0-port and see how far
>     you get: the compiler should tell you where the old port doesn't
>     fit the new lwIP code.
>
>     Simon
>
>
>
>     _______________________________________________
>     lwip-users mailing list
>     address@hidden <mailto:address@hidden>
>     http://lists.nongnu.org/mailman/listinfo/lwip-users
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> lwip-users mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/lwip-users