linguini1 commented on PR #17363: URL: https://github.com/apache/nuttx/pull/17363#issuecomment-3567133225
> Yes, I agree that it could generate some drivers only supporting one or other implementation. Same also happens with CAN. It should be nice if uORB was just a wrapper around the char device, this way we could avoid this issue. But I don't know if it is possible. It's currently possible to interact with uORB drivers as though they are character drivers, so I think that approach can be taken. Wrapping character drivers causes more overhead in systems that use uORB. I think the biggest issue with it resource-wise is using floating point numbers, I'm not sure there are really any cases where a small MCU can't run uORB because of its size? It's possible to reduce the buffering it does, although maybe I'm misinformed on all the resources it uses. -- 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]
