Hi,
i’m currently working on a project using lwip 1.4.1 stack (raw api with tcpip),
and since i’m still in development anyways i thought i might use the newest
lwip 2.0 stack instead. Can i just swap them out or how do i “upgrade” to 2.0?
Are there any major “bugs” open, since i’ve read that it
Hi Sandra,
I wrote a driver following the ethernetif skeleton and a NO_SYS=1 port
for Cortex-M3.
Can you please compare that with what you have and mark the conceptual
differences where you are in doubt ? I'm too busy/lazy to look at the
entire port, and those functions you mention do not belon
In short, the latest git head will give you many bug fixes, a working
PPP, IPv6, beter SNMP, and maybe some yet-to-be-found new bugs.
The UPGRADING file is yet to be updated, and I didn't upgrade myself to
comment on that. As I've been following the posts in the devel list, I
expect differences
pischin...@lunatone.com:
i’m currently working on a project using lwip 1.4.1 stack (raw api
with tcpip), and since i’m still in development anyways i thought i
might use the newest lwip 2.0 stack instead. Can i just swap them out
or how do i “upgrade” to 2.0?
Unless you enable IPv6, you shoul
Jeff Barlow wrote:
[..] It seems fairly
obvious to me though that inserting extra code in the ISR path that
inspect some globals only to figure out that it is indeed in an ISR will
have an adverse effect on latency.
I might be picky here, but using C instead of assembler tends o have an
advers
On pon, 2016-07-11 at 21:09 +0200, goldsi...@gmx.de wrote:
> What I mean is personally, I don' think it's good design to expose
> the
> ISR/non-ISR fact accross layers of the code that possibly have
> nothing
> to do with that knowledge.
>
> Keeping my private view aside, is there a requirement
Thanks, that was very helpful. I’ll try upgrading as soon as i’ve got time :)
Markus
From: goldsi...@gmx.de
Sent: Monday, July 11, 2016 8:47 PM
To: Mailing list for lwIP users
Subject: Re: [lwip-users] lwip 2.0 upgrading
pischin...@lunatone.com:
i’m currently working on a project using lw
