RE: [lwip-devel] [bug #19177] Faulty arp initialization inethernetif_init skeleton

[Taranowski, Thomas \(SWCOE\)]

Hmm, I remember reading that thread.  Now that I look back on it, doing it in 
the tcpip_init_done makes sense, and looks safe to call before the netif_add 
routine.  I'm now recommending your solution, as it does away with the messy 
static flag variable, and associated check.

> -----Original Message-----
> From: address@hidden
> [mailto:address@hidden On
> Behalf Of Frédéric BERNON
> Sent: Thursday, March 01, 2007 12:53 AM
> To: Frédéric BERNON; Thomas Taranowski; address@hidden
> Subject: [lwip-devel] [bug #19177] Faulty arp initialization
> inethernetif_init skeleton
> 
> 
> Follow-up Comment #1, bug #19177 (project lwip):
> 
> I think that  etharp_init() would have to be call before any net_add,
> because
> ARP Table is a global resource. Initialization sequence should be :
> 
>      #if LWIP_STATS
>      stats_init      ();
>      #endif /* STATS */
>      #if (NO_SYS == 0)
>      sys_init        ();
>      #endif /* (NO_SYS == 0) */
>      mem_init        ();
>      memp_init       ();
>      pbuf_init       ();
>      etharp_init     ();
>      netif_init      ();
>      lwip_socket_init();
> 
>      //...
>      netif_add( ...);
>      //...
> 
> 
> About the arp_timer, I proposed yesterday in the forum's thread "Timers &
> lwip tasks (a multithreadquestionwithLwIP)" to initialize it in the
> tcpip_init_done (if you use tcpip_thread).
> 
> 
> 
>     _______________________________________________________
> 
> Reply to this item at:
> 
>   <http://savannah.nongnu.org/bugs/?19177>
> 
> _______________________________________________
>   Message posté via/par Savannah
>   http://savannah.nongnu.org/
> 
> 
> 
> _______________________________________________
> lwip-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/lwip-devel