RTEMS lwIP porting
Joel Sherrill
joel.sherrill at oarcorp.com
Mon Aug 10 17:20:21 UTC 2015
On 8/10/2015 11:53 AM, Gedare Bloom wrote:
> On Mon, Aug 10, 2015 at 12:20 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?
>>
> I think that would be outside the scope of the student's GSoC effort.
Agreed. This just sets up a repeatable baseline that we won't slip
back from. There have been ports in the past which didn't get to this
public point and were lost to history.
> I don't know of any work ongoing to optimize the LWIP port for RTEMS.
> We appear to have a wiki page that may be relevant to update with
> pertinent details: https://devel.rtems.org/wiki/Packages/LWIP
https://ftp.rtems.org/pub/rtems/people/joel/rtems-lwip/ has what is
now a 10 year old port. It may have been done against the Classic API.
I don't recall but it is there as a reference.
>> Thanks!
>>
>> Daniel.
>>
>>>
>>> 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
>>> http://lists.rtems.org/mailman/listinfo/devel
>>
>>
>>
>> --
>>
>> 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
>> _______________________________________________
>> devel mailing list
>> devel at rtems.org
>> http://lists.rtems.org/mailman/listinfo/devel
--
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
More information about the devel
mailing list