[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lwip-devel] [task #14314] Implement interface name/index APIs

From: Joel Cunningham
Subject: [lwip-devel] [task #14314] Implement interface name/index APIs
Date: Thu, 9 Feb 2017 16:24:41 -0500 (EST)
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0

Follow-up Comment #56, task #14314 (project lwip):


I could take that approach, it would mean defining a new API msg structure
(struct if_apimsg?) with a memory pool (because of MPU support) so I can use
tcpip_api_call() and also a new set of macros maping to API_VAR and such.  Is
that preferable to leveraging netifapi?


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]