3. The old version I'm currently using is stable with the socket API. But I needed of lot of basic features which were not implemented (MSG_PEEK, receive time-out) Unfortunately, the corresponding macros are defined, letting the user think they are implemented !!!
I think it's normal for "options": like this, you got source code compatibility, and using these options should return ENOPROTOOPT. About flags like MSG_PEEK, you're right.
4. I have a big problem for handling TCP connection loss. When I unplug my device, or shut-down the peer, no error is reported and I can't know the connection is lost. Is this bug corrected ?
Simon is right, the problem is mainly the default lwIP values. To reduce that, you can reduce your TCP_SLOW_INTERVAL, and reduce TCP_MAXRTX. It's a kind of "send timeout", but global, and not "per socket".
5. About 1.3.0 required features: -> backlog for listening sockets. I think this is a very basic feature, and I actually accidentally learned it was not implemented in this list !
We have talk about that in http://savannah.nongnu.org/task/?7421 (task #7421 : Implement SO_RCVBUF)
----- Original Message ----- From: "Stéphane Lesage" <[EMAIL PROTECTED]>
To: <[email protected]> Sent: Saturday, November 24, 2007 5:24 PM Subject: [lwip-users] LwIP port on Blackfin, some questions and 1.3.0 Hi, I'm using LwIP on Blackfin for my VoIP project, and I've been reading the mailing lists for a few months. First of all, it's great to see this project is very active, developers are reactive, and new features I will need in the future have been added :-) 1. We can't say so about the Blackfin/VDK port from Analog Devices :-( I've been very disapointed with the new release of Visual DSP 5.0. S. Ali Tokmen said they ported 1.2.0, but a diff with VDSP 4.5 latest update shows it's still the same old version... Or am I wrong ? Several months ago I tried to compile the CVS head, but didn't go further, considering all the modifications the guys from A.D made. (alignment problems ?) Did someone succeed to compile ? 2. I think I will investigate on the BF536/7 driver, because we have problems with real-time audio interrupts, and I'm not convinced by the performance of the implementation. (double-layer for the sys_arch, ADI driver model) Is there someone interested in the development of a new port ? Maybe someone already did it ? 3. The old version I'm currently using is stable with the socket API. But I needed of lot of basic features which were not implemented (MSG_PEEK, receive time-out) Unfortunately, the corresponding macros are defined, letting the user think they are implemented !!! Can you please be careful about that in the next release ? -> comment the #define with something like // Currently not implemented 4. I have a big problem for handling TCP connection loss. When I unplug my device, or shut-down the peer, no error is reported and I can't know the connection is lost. Is this bug corrected ? (I currently must send data and time-out, and I feel like doing TCP's job !) 5. About 1.3.0 required features: -> backlog for listening sockets. I think this is a very basic feature, and I actually accidentally learned it was not implemented in this list ! -> more documentation about lwip_select(), and implementation of exceptset How is a TCP connection close reported ? How is a TCP connection accept reported ? Why is a new connection on a listening socket reported by readset ? What will be signalled on exceptset ? Best regards. -- Stéphane Lesage ATEIS International _______________________________________________ lwip-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lwip-users _______________________________________________ lwip-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lwip-users
