OT: [PATCH rtems-lwip v3 1/7] lwip.py: Change arch and bsp check method

Kinsey Moore kinsey.moore at oarcorp.com
Mon Sep 19 18:45:13 UTC 2022


On 9/19/2022 04:28, Cedric Berger wrote:
> Sorry for a slightly off-topic question here:
>
> [...]
>> In that case, I'll stick with the BSP management improvements once v4 
>> of this patch set goes in (probably) and skip the generic build.
>>
>> Is a generic build something that would be worth pursuing for lwIP? 
>> It would come with the core stacks, but no drivers whatsoever.
>
> I'm very exited about that stuff, and here is a project I'm entertaining:
>
> Using LWIP on the Cortex-M4 side of a stm32h747:
>
>  - Without the ethernet driver.
>
>  - With an emulated, ethernet USB driver (device-side USB, I will 
> write the driver if it does not exist yet).
>
>  - Talking to a cellular modem with PPP over USB (host-side USB, I 
> will write the driver if it does not exist yet).
>
> Can I, today, configure a basic/generic LWIP stack that would allow to 
> develop such a setup?


Currently all rtems-lwip build configurations are very BSP-specific and 
include drivers with no options to leave the drivers out of the build. 
Additionally, there is no option for a generic build for BSPs that 
aren't specifically supported.

It's possible that we could build a generic stack for BSPs that aren't 
otherwise supported with drivers, but I'm waiting on some things to 
settle out (specifically STM32F4 support) before I move forward with any 
more changes that could disrupt that.

I'm also focused elsewhere for the moment, so waiting on things to 
settle out is fine.


Kinsey



More information about the devel mailing list