[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-users] LwIP port on Blackfin, some questions and 1.3.0
From: |
Stéphane Lesage |
Subject: |
[lwip-users] LwIP port on Blackfin, some questions and 1.3.0 |
Date: |
Sat, 24 Nov 2007 17:24:59 +0100 |
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] LwIP port on Blackfin, some questions and 1.3.0, Stéphane Lesage, 2007/11/24
- [lwip-users] LwIP port on Blackfin, some questions and 1.3.0,
Stéphane Lesage <=
- Re: [lwip-users] LwIP port on Blackfin, some questions and 1.3.0, address@hidden, 2007/11/24
- RE: [lwip-users] LwIP port on Blackfin, some questions and 1.3.0, Stéphane Lesage, 2007/11/24
- Re: [lwip-users] LwIP port on Blackfin, some questions and 1.3.0, Frédéric BERNON, 2007/11/24
- Re: [lwip-users] LwIP port on Blackfin, some questions and 1.3.0, address@hidden, 2007/11/24
- Re: [lwip-users] LwIP port on Blackfin, some questions and 1.3.0, Frédéric BERNON, 2007/11/24
- RE: [lwip-users] LwIP port on Blackfin, some questions and 1.3.0, Stéphane Lesage, 2007/11/24
- Re: [lwip-users] LwIP port on Blackfin, some questions and 1.3.0, Frédéric BERNON, 2007/11/24
Re: [lwip-users] LwIP port on Blackfin, some questions and 1.3.0, Frédéric BERNON, 2007/11/24