[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lwip-users] 1.4.0 -> 1.4.1 or 2.0.0
From: |
Sylvain Rochet |
Subject: |
Re: [lwip-users] 1.4.0 -> 1.4.1 or 2.0.0 |
Date: |
Mon, 8 Aug 2016 19:32:16 +0200 |
User-agent: |
Mutt/1.5.23 (2014-03-12) |
Hi Sergio,
On Mon, Aug 08, 2016 at 02:23:13PM -0300, Sergio R. Caprile wrote:
> Hi there,
> here I am with this chinese module having linkable libraries for the link
> layer driver (no source) and an (I think) netconn-like layer over RAW API
> (yes source), developed for lwIP 1.4.0RC2. Introducing ESP8266.
> Let's say I want to move to 1.4.1 or even 2.0.0
> For 2.0.0, I think that (at least) I'll have to provide a stub so it can
> link the calls to tcp_accepted().
> Starting my migration with 1.4.1, any look ahead on my possible nightmares ?
> Desired target is 2.0.0 of course, but law of minimum effort still applies.
> I haven't been brave enough to even try compiling, I will if your responses
> are encouraging or I find myself bored enough and there's no beer.
> Cheers.
Humm, the raw API didn't change much, so it should be fine.
However, the netif API changed… especially if you want IPv6. If you
stick to IPv4 you will probably trip over the administrative state and
link state rework as well as some other flags, the netif struct changed
as well IIRC so it's not ABI compatible at all. But what you could do is
to rename all netif calls and netif struct in lwIP and write a shim
layer between the symbols used in your blob and the renamed lwIP calls.
Good luck, by the way :-)
Sylvain
signature.asc
Description: Digital signature
Re: [lwip-users] 1.4.0 -> 1.4.1 or 2.0.0, Sergio R. Caprile, 2016/08/09