Sylvain Rochet b55412a0c4 PPP, PPPoS, replaced static sio_write() calls to a user defined callback ... The overall lwIP design on data flows (netif,udp,tcp) is to use a user defined callback to get data from stack and a static function to send data to stack, which makes perfect sense. The SIO port was an exception, the PPP stack never really used the SIO port by only using the sio_send() function (and the ignominious sio_read_abort() function a while back). The way the SIO port is currently designed adds a tight coupling between the lwIP port and the user code if the user need to do specific user code if the current uart used is the PPPoS uart, which is not nice, especially because all the lwIP stack is quite clean at this subject. While we are at stabilizing the PPP API, change this behavior before it's too late by replacing the static sio_write() calls to a user defined callback.		2015-09-13 17:53:16 +02:00
..
doxygen
contrib.txt
FILES
ppp.txt	PPP, PPPoS, replaced static sio_write() calls to a user defined callback	2015-09-13 17:53:16 +02:00
rawapi.txt	Documentation, add pppapi.h to thread-safe header whitelist	2015-09-12 14:57:05 +02:00
savannah.txt
snmp_agent.txt
sys_arch.txt