This issue is related to the discussion in #346.
The template machine is defined by cmake/platforms/template-generic.cmake and cmake/platforms/template-freertos.cmake.
In lib/system/freertos/template and lib/system/generic/template, we define some default functions needed for the porting layer. This template can be used as a reference.
On the other hand, we expect SoC vendors to implement their porting layer downstream or within their projects. An example is the AMD/xilinx porting.
We need to clarify how we can make it easier for Libmetal users to port the library to their targets.
Keeping a template implementation
Relying only on documentation
Other approaches?
This issue is related to the discussion in #346.
The template machine is defined by cmake/platforms/template-generic.cmake and cmake/platforms/template-freertos.cmake.
In lib/system/freertos/template and lib/system/generic/template, we define some default functions needed for the porting layer. This template can be used as a reference.
On the other hand, we expect SoC vendors to implement their porting layer downstream or within their projects. An example is the AMD/xilinx porting.
We need to clarify how we can make it easier for Libmetal users to port the library to their targets.
Keeping a template implementation
Relying only on documentation
Other approaches?