Re: RFC on STM32 Ethernet driver
toggle quoted messageShow quoted text
This is a question of trade-off. Using HAL has some drawbacks (some might
Thanks for proposing this driver, I think it will interest a lot of people.
About your last point, let me mention ST view on this:
be objectives like footprint or more subjective like CamelCase), but it's
definitely possible in Zephyr.
Main interest is that it will help having a reliable driver working on all STM32
SoCs supporting ethernet (today in zephyr: stm32f407, stm32f429, stm32f469,
stm32f7xx under review) faster. More supported SoCs also means more
interested people, which will help in getting the driver mature.
In the end, it should save time to work on end applications rather than porting.
A native driver, specific to the IP (which might also be used on other SoCs),
might be more optimized, but this might also take you some time before
having it mature for complex IPs such as ethernet (or USB..).
In any case, I think it would be great to have your driver upstreamed in
a first time. Then, time will tell if a native driver is nice to have or required.
On 3 June 2017 at 15:17, Erwin Rol <mailinglists@...> wrote: