On Thu, Sep 24, 2026 at 1:59 PM Tomek CEDRO <[email protected]> wrote: > > On Wed, Sep 23, 2026 at 8:39 AM Binh Nguyen <[email protected]> > wrote: > > > > Hi all, > > > > I would like to get some early feedback on the RZ/V2H port. > > > > We are porting NuttX to the Renesas RZ/V2H Cortex-R8 and currently reuse > > the vendor-maintained FSP HAL for the low-level peripheral drivers. > > NuttX still owns the driver interfaces, architecture integration, board > > support, Kconfig and build integration. A thin adaptation layer connects > > the NuttX drivers to the FSP HAL. > > > > Before we prepare the upstream patches, would using RZ FSP as a third-party > > HAL dependency be acceptable to the NuttX community? > > I have also followed the recent esp-hal-3rdparty discussion. I understand > > that external HAL dependencies raise concerns about governance, maintenance > > and community control, so I would like to clarify the expected approach > > early. > > > > FSP HAL is maintained by Renesas, and our team intends to maintain the > > NuttX RZ/V2H integration and support future FSP updates. > > > > Would this approach be feasible, and what requirements should we satisfy > > regarding licensing, version pinning, CI and long-term maintenance? > > > > Thanks in advance. > > Binh Nguyen > > Renesas Electronics > > BIG NO to external vendor HAL, all driver should be in-tree and part > of the NuttX RTOS, thank you :-) > > -- > CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
I am happy to bring Renesas attention to NuttX RTOS. I am not happy that I did not get the contract to do the job, that's life. If anyone else is about to do the job please please make it right from start. Any external HAL only makes things worse in the long run and we avoid that in NuttX. Thank you and have fun! :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
