Re: Zynq driver development strategy

2019-12-05 Thread Mathew Benson
I saw that. I already started with that. On Thu, Dec 5, 2019 at 12:32 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 05/12/2019 01:22, Chris Johns wrote: > > Is there SPI code in FreeBSD that can be used? That would be my > preferred path > > if it is available because it i

Re: Zynq driver development strategy

2019-12-04 Thread Sebastian Huber
On 05/12/2019 01:22, Chris Johns wrote: Is there SPI code in FreeBSD that can be used? That would be my preferred path if it is available because it integrates vertically. New SPI drivers should use this framework: https://git.rtems.org/rtems/tree/cpukit/include/dev/spi/spi.h It is compatible

Re: Zynq driver development strategy

2019-12-04 Thread Chris Johns
On 5/12/19 3:45 am, Mathew Benson wrote: > Is there any technical or legal (licensing) reason why I can't just integrate > the driver code generated by the Xilinx XSDK tool when building a standalone > or > FreeRTOS project?  It's the same code for both.  I did a dependency check and, > assuming I

Zynq driver development strategy

2019-12-04 Thread Mathew Benson
Is there any technical or legal (licensing) reason why I can't just integrate the driver code generated by the Xilinx XSDK tool when building a standalone or FreeRTOS project? It's the same code for both. I did a dependency check and, assuming I didn't miss any externs or implicit declarations, t