cederom commented on issue #19838: URL: https://github.com/apache/nuttx/issues/19838#issuecomment-5360354270
> > > [@zyy37](https://github.com/zyy37): Can you establish a continuous plan for adapting chips? (..) > > > > > > @cederom: There is no such plan and it will be hard to create one without vendors being interested in the first place, then providing resources (boards, funding) for the development to happen. > > I have contacted numerous vendors and none of them was interested :-( > > Therefore we only support chips that someone uses on their own and shares back to the upstream which is also not very common thing. > > @zyy37: Thank you. It's really difficult to coordinate. I think your operating system and chip manufacturers are upstream and downstream partners, so there should be interfaces that others can use or be used for. Actually, many manufacturers provide ready-made chip adaptation code, but they may not know the interface of your operating system and cannot use it. The force did not move in one direction. You can also refer to the manufacturer's ready-made code when porting a chip, which can help reduce your workload. It's a theory. If you work with different chips, you will notice there is no one standard, every vendor has their own preferences, and each OS/RTOS use different approach under the hood (that approach changes in time faster or slower). Each vendor may provide the SDK of some sort, we may adopt it (the interface layer slows things down and makes things bigger), but problem arises when that SDK changes, its a never ending story, like chasing a rabbit (in our free time) and this is why avoid SDKs here in NuttX in favor of in-tree drivers that are integral part of our project and do not depend on external politics. The problem here is clear: no vendor is willing to pay NuttX developers to port their devices, everyone is only happy to use results for free :-( -- 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]
