Luca Ottaviano wrote:
> However the project started a while ago and now I'd like to
> finish it as soon as possible.
Then that's a good reason not to upgrade now :-)
> > From what I understand, you implemented your driver in the tcpip_thread
> and are blocking on a semaphore. This is not a good
On ven, 2011-05-20 at 10:59 +0200, Simon Goldschmidt wrote:
> Luca Ottaviano wrote:
> > Hi,
> > I'm having a few issues in porting lwip 1.3.2 on BeRTOS
> > (www.bertos.org).
>
> If you're doing a new port, I *stronlgy* suggest to use 1.4.0, not 1.3.2,
> which is outdated.
Yes, I've seen there a
Kieran Mansley wrote:
> Documentation changes are a great way to help a project like lwIP,
Especially after using it for over a year now, it would be great if you would
help by contributing (to the wiki, at least, as it's rather easy to contribute
there)! lwIP is run by people in their free ti
Luca Ottaviano wrote:
> Hi,
> I'm having a few issues in porting lwip 1.3.2 on BeRTOS
> (www.bertos.org).
If you're doing a new port, I *stronlgy* suggest to use 1.4.0, not 1.3.2, which
is outdated.
> I have implemented my EMAC driver and the low_level_input() functions.
> I've used BeRTOS faci
Hi,
I'm having a few issues in porting lwip 1.3.2 on BeRTOS
(www.bertos.org).
I have implemented my EMAC driver and the low_level_input() functions.
I've used BeRTOS facilities to implement the EMAC driver; however,
whenever I wait inside the driver timeouts are not processed and so TCP
does not re
On Fri, 2011-05-20 at 09:23 +0200, Walter Saegesser wrote:
> The Wiki (http://lwip.wikia.com/wiki/LwIP_Wiki) is thoroughly out of
> date and I scarcely consult it.
It shouldn't be. Do you have an example of something that is wrong
there? If so, please let us know or even better just fix it.
Docu
On Fri, 2011-05-20 at 09:45 +0200, Enrico Murador - Research &
Development - CET wrote:
> Hello,
> I'm sorry, I would need some more information...
>
> I would know wether it is ok to call tcp_close() everytime the receive
> callback is called with NULL data pointer,
Yes.
> and wether it is safe
Hello Simon
>>Concerns lwIP v1.3.2.
>> ...
> ... can be modified using
netconn_set_recvtimeout()/netconn_get_recvtimeout()
> to set the timeout in miliseconds. ...
Thanks for the input! That's what I have been looking for, unfortunately
in vain because version 1.3.2 did not provide these funct
