On Tue, 2012-07-31 at 09:49 -0400, Chen wrote:
> My application requires to tag a small codes to the lowest level of
> read routine to monitor a private non-standard packet as soon as it
> arrives (I am using lwip+FreeRTOS+AVR32). preferable at the interrupt
> that retrieves the data from the PH
Never mind, I missed the other thread ethernetif_input
ethernetif_input calls netif->input, which is tcpip_input, set up by netif_add
--
Message: 2
Date: Wed, 01 Aug 2012 11:39:43 -0400
From: Chen
To: lwip-users@nongnu.org
Subject: Re: [lwip-users] lwip'
Marty, Thanks for your reply
tcpip_thread receives what tcpip_input posted, but who calls it? I
have trouble figure it out, any pointer? thanks again
Typically your driver is going to pass the packet back to lwIP via a
function like tcpip_input(...). Look at it just before that, and maybe
do
users-bounces+martypomeroy=novabio@nongnu.org] On
Behalf Of Chen
Sent: Tuesday, July 31, 2012 9:49 AM
To: lwip-users@nongnu.org
Subject: [lwip-users] lwip's lowest level read routine?
Hi there,
My application requires to tag a small codes to the lowest level of read
routine to monitor a p
Hi there,
My application requires to tag a small codes to the lowest level of
read routine to monitor a private non-standard packet as soon as it
arrives (I am using lwip+FreeRTOS+AVR32). preferable at the interrupt
that retrieves the data from the PHY: cature the special packet and
perform a
