We use LWIP l.4.l with RAW (no OS). I had to query my PHY's
control/status register to determine the link status... I did this from
main loop (non-interrupt) time. There is also a protocol for requesting
direct PHY access, depending on the uP's interface. Huge PITA, but
entirely necessary
Hi Gustavo
You're missing one very important point, that is below lwip is a part
that you are responsible for, this is the "driver" and it is not a part
of lwip. This part handles among other things the link status and should
notify lwip if it changes. Your callbacks are probably not called
Well, I'm no expert on whatever you are trying to do with this, so take
it with a grain of salt.
you alloc a pbuf (1)
then you concatenate to the tail of another pbuf (0)
now (1) does not exist anymore as a lonely pbuf but is attached to (0),
all that exists now is (0).
Somehow, you are
Hi Jens,
thank you for your colaboration. Is it possible that you share if me your
fix? I am trying not to reinvent the wheel.
As I said to Simon, I am trying to use the LWIP_NETIF_LINK_CALLBACK
and LWIP_NETIF_STATUS_CALLBACK functions to keep track of the Phy Link, but
these functions never
*> Have you reported a problem? If not why are you surprised it's not
fixed?*
I'm Sorry if I sounded harsh or pretencious, it was not my intention. I did
not have reported this issue because as far as I could see it is well known
by the community.
*> Now this can't be an lwIP bug: lwIP knows
