RTEMS lwIP porting
ragunath3252 at gmail.com
Mon Aug 10 17:25:07 UTC 2015
Most of the work comes from your/marcos port. The aim was to
integrate a working lwIP port to RTEMS Source Builder.
I took the port & understood what has been done. Then I wrote an
application that uses lwip stack on RTEMS.
I ran into some issues and fixed them. Now with the changes, the
I discussed with chris on how to integrate the changes to RSB. As per
his suggestion, the idea is to separate lwip base and drivers. The
lwip base is compiled as a library using RSB and driver will be
compiled as a separate library . The application can then link to it.
The driver is also from your port with some fixes.
I am not aware of the issue with POSIX API. Once we get this working,
I am ready to implement with native api in the future.
On Mon, Aug 10, 2015 at 9:50 PM, Daniel Gutson
<daniel.gutson at tallertechnologies.com> wrote:
> On Mon, Aug 10, 2015 at 10:48 AM, Joel Sherrill
> <joel.sherrill at oarcorp.com> wrote:
>> On 8/9/2015 4:57 AM, ragu nath wrote:
>>> Hi All,
>>> I have sent the patches for building lwIP from RSB. First patch
>>> contains changes for RTEMS Resource Builder. The second patch is RTEMS
>>> specific changes that will be applied to lwIP base.This patch contains
>>> only lwIP sources. I will be sending another patch for the driver to
>>> be used with lwIP. The application can then link to both of the
>>> libararies (lwip & driver).
>> Has the LWIP patch been submitted upstream to the LWIP maintainers?
>> And where do drivers come from? From what I have seen, LWIP seems
>> to not have a unified base of device drivers. Would this just be to
>> build the basic stack and then it is the users responsibility to
>> find and compile a driver?
> Also, what from these comes from our work? Sorry that I'm a little bit
> confused and arrived late to the
> subject. BTW, there is still work to do, since the state we left
> working LWIP is using the posix layer,
> which we observed introduces important overhead, so a further step is
> to reimplement the LWIP's HAL
> using the RTEMS native API instead. Any plan for that?
>> What is your RTEMS configuration so I can try it?
>> I will try to build it today.
>> Joel Sherrill, Ph.D. Director of Research & Development
>> joel.sherrill at OARcorp.com On-Line Applications Research
>> Ask me about RTEMS: a free RTOS Huntsville AL 35805
>> Support Available (256) 722-9985
>> devel mailing list
>> devel at rtems.org
> Daniel F. Gutson
> Chief Engineering Officer, SPD
> San Lorenzo 47, 3rd Floor, Office 5
> Córdoba, Argentina
> Phone: +54 351 4217888 / +54 351 4218211
> Skype: dgutson
> LinkedIn: http://ar.linkedin.com/in/danielgutson
More information about the devel