acassis commented on issue #19838: URL: https://github.com/apache/nuttx/issues/19838#issuecomment-5359912630
> > Hi [@zyy37](https://github.com/zyy37) actually recently [@JorgeGzm](https://github.com/JorgeGzm) ported NuttX to GigaDevice gd32vw55x and the port was done in a few days (even with WiFi and BLE working), not 2 weeks as that AI told you. > > Unfortunately Apache will not send this invitation to companies to port NuttX to their chip, because they even have other RTOS under their umbrella: mynewt, it is different from Linux Foundation which has only one. > > I think a way to get NuttX ported to more devices is: 1) the own community does it, like Jorge did; 2) NuttX get critical mass, more users, and more customers requiring semiconductor companies to do the port; 3) we can create a NuttX International (like RISC-V International) to get more companies associated and get support to the project. Actually I and [@cederom](https://github.com/cederom) already discussed this ideas some days ago. > > So, if you want to help, please start with 1. > > Thank you for your reply. Perhaps you can clarify the step-by-step documentation for chip porting and simplify the porting architecture and workload, as mentioned in AI. It would be best not to use pseudo-code, and it should be something that actually works. By clarifying the documentation and teaching others, others can contribute and help you with these workloads? Currently, only those who are very experienced and familiar with embedded systems can easily get started. If it becomes easy to port, maybe many developers will be willing to contribute, just like in approach 1. There are two guides already based on real port: https://nuttx.apache.org/docs/latest/guides/port.html If you want to learn, I suggest you try to port without using AI, just to understand all the details. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
