Luca Ottaviano wrote:
I have only one remark: I guess that since you're developing a stack for
embedded systems you have a working port done on your reference
platform, don't you? Is it possible to include an 'official' working
port with the source code releases? That's because contributed ports
On lun, 2011-05-23 at 18:16 +0200, Simon Goldschmidt wrote:
> Luca Ottaviano wrote:
> > Ah, maybe that's the misunderstanding; I'm initializing the interface
> > using:
> > netif_add(&netif, &ipaddr, &netmask, &gw, NULL, ethernetif_init, ip_input)
> >
> > So my ethernet thread is calling ip_input
Luca Ottaviano wrote:
> Ah, maybe that's the misunderstanding; I'm initializing the interface
> using:
> netif_add(&netif, &ipaddr, &netmask, &gw, NULL, ethernetif_init, ip_input)
>
> So my ethernet thread is calling ip_input() directly instead of
> tcpip_input().
Well, that's a bug in your por
On ven, 2011-05-20 at 12:07 +0200, Simon Goldschmidt wrote:
> > > From what I understand, you implemented your driver in the tcpip_thread
> > and are blocking on a semaphore. This is not a good idea.
> >
> > The EMAC driver is plugged into the ethernet thread using
> > low_level_input() and someti
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
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
