Re: [lwip-users] Problem with do_writemore() + LWIP for AVR32

[patelbaroda]

However, I read the description at ethernet_input() (which is part of lwip)
as
"

/**
 * Process received ethernet frames. Using this function instead of directly
 * calling ip_input and passing ARP frames through etharp in
ethernetif_input,
 * the ARP cache is protected from concurrent access.
 *
 * @param p the recevied packet, p->payload pointing to the ethernet header
 * @param netif the network interface on which the packet was received
 */
err_t
ethernet_input(struct pbuf *p, struct netif *netif)

"

It advice to use this function instead of directly using ip_input to protect
ARP cache.





Simon Goldschmidt wrote:
> 
> address@hidden wrote:
>> That file is written by ATMEL? I would have expected them to be able to
>> read our example driver file... However, it seems like they have done it
>> as they thought it has to be without really checking it :-( See below.
>>    
> Sorry, didn't mean to be rude, it's just that things like these keep 
> popping up again and again... I updated the wiki page about "Writing a 
> device driver" to correctly point out this.
> 
> Simon
> 
> 
> _______________________________________________
> lwip-users mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/lwip-users
> 
> 

-- 
View this message in context: 
http://old.nabble.com/Problem-with-do_writemore%28%29-%2B-LWIP-for-AVR32-tp26681732p26753994.html
Sent from the lwip-users mailing list archive at Nabble.com.