Re: [lwip-users] 1.4.0 -> 1.4.1 or 2.0.0

2016-08-08 Thread Sylvain Rochet
Hi Simon, On Mon, Aug 08, 2016 at 10:17:15PM +0200, goldsi...@gmx.de wrote: > Sylvain Rochet wrote: > >Humm, I would have thought that a revision release didn't change the API > >at all, > > Thinking about it again, I guess it was an ABI change, not an API change. > For the target of lwIP (at

Re: [lwip-users] 1.4.0 -> 1.4.1 or 2.0.0

2016-08-08 Thread goldsi...@gmx.de
Sylvain Rochet wrote: Humm, I would have thought that a revision release didn't change the API at all, Thinking about it again, I guess it was an ABI change, not an API change. For the target of lwIP (at that time?) keeping the API stable was enough. And remember the API does *not* include

Re: [lwip-users] 1.4.0 -> 1.4.1 or 2.0.0

2016-08-08 Thread Sylvain Rochet
Hi, On Mon, Aug 08, 2016 at 08:17:42PM +0200, goldsi...@gmx.de wrote: > > Right. We didn't have binary compatiblity in mind, so after removing some > flags, some other flags' values have changed. That might still work if you > fix them up after netif_add() (which calls the netif's init

Re: [lwip-users] 1.4.0 -> 1.4.1 or 2.0.0

2016-08-08 Thread goldsi...@gmx.de
Sylvain Rochet wrote: Humm, the raw API didn't change much, so it should be fine. I guess so, too. In any way, if you have the sources, you could even fix it if it needs fixing. I hope it doesn't (unless you add IPv6, in that case, it might). However, the netif API changed… especially if

[lwip-users] 1.4.0 -> 1.4.1 or 2.0.0

2016-08-08 Thread Sergio R. Caprile
Hi there, here I am with this chinese module having linkable libraries for the link layer driver (no source) and an (I think) netconn-like layer over RAW API (yes source), developed for lwIP 1.4.0RC2. Introducing ESP8266. Let's say I want to move to 1.4.1 or even 2.0.0 For 2.0.0, I think that

Re: [lwip-users] Connection freeze after 29200 Bytes

2016-08-08 Thread Norbert Kleber
Hi all, after porting to v2.0.0 and reducing the cunks to 16kB everything works fine. Seems like the limited S-RAM and Frequency of the Mikrocontroller couldn't handle chunks this large. Thanks for all your help. Regards, Norbert Am 07.08.2016 um 11:57 schrieb Norbert Kleber: Hi

[lwip-users] tcp_accepted() and 1.4.1 -> 2.0.0

2016-08-08 Thread Sergio R. Caprile
I've just read the brand new shiny 2.0.0 docs, and tcp_accepted() has been put to sleep, six feet under, pushing up the daisies. Mi example TCP server code does this: static err_t myconnected(void *arg, struct tcp_pcb* pcb, err_t err) { if(err == ERR_OK){

Re: [lwip-users] lwIP documentation update

2016-08-08 Thread Sergio R. Caprile
Great! The text in http://www.nongnu.org/lwip/2_0_0/raw_api.html still references tcp_accepted(), which has been removed ___ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users

Re: [lwip-users] Connection freeze after 29200 Bytes

2016-08-08 Thread Patrick Klos
On 8/6/2016 7:03 AM, Norbert Kleber wrote: ...As long the file to transfer is smaller than this magical 29200 Bytes every thing works fine, but if it exceeds that limit the TCP connection freezes after transmitting the 29200Bytes i would be grateful for any hint. For what it's worth,

Re: [lwip-users] Connection freeze after 29200 Bytes

2016-08-08 Thread Sergio R. Caprile
Please search the list, read the wiki, http://lwip.wikia.com/wiki/Raw/TCP and or go to this recent msg http://lists.nongnu.org/archive/html/lwip-users/2016-08/msg00063.html there you'll see a working way to interact with TCP. You can also check the code in the web server and the

Re: [lwip-users] Large File transfer-- FTP lwIP 1.4.1

2016-08-08 Thread Sergio R. Caprile
I don't follow your logic, and don't have the time to sort it out. Sorry. You have a server. A server receives a request on the rx path, on an rx frame. I wouldn't process that on a poll callback, which is called at fixed intervals. Then the server tries to send something back, and it may have

Re: [lwip-users] http server problems/bug

2016-08-08 Thread Sergio R. Caprile
> 1. We got the web server original code from STM32 provided example > "LwIP_HTTP_Server_Raw" , but also mixed with 1.4.1 contrib, which are > quite the same. Then go to ST, "mixed" and "quite the same" is not the thoroughly tested server in the contrib tree. It is your code, your

[lwip-users] lwIP documentation update

2016-08-08 Thread Dirk Ziegelmeier
Hello all, the lwIP documentation at http://www.nongnu.org/lwip/2_0_0/index.html was greatly improved. Have a look, and please tell me if you have any comments, corrections or improvements! Dirk ___ lwip-users mailing list lwip-users@nongnu.org