acassis commented on issue #17365: URL: https://github.com/apache/nuttx/issues/17365#issuecomment-3568326590
> But that is still a problem? Now we have two different sensor driver frameworks to maintain on NuttX. Like [@raiden00pl](https://github.com/raiden00pl) mentioned, "uORB" devices can still be interacted with as character drivers. I guess the confusion here is that I am referring to the new sensor framework as uORB, even though it is technically not dependent on that (mentioned in [#10644](https://github.com/apache/nuttx/issues/10644)). I think if users want a character driver, they should interact with the sensor framework devices as character devices instead of through uORB. That way there is still only one framework. The only problem is float dependency. I am firmly against maintaining two different types of frameworks, I would rather solve the float problem. > > I guess we should stop referring to the framework as uORB, since uORB is an optional extension. In fact, there at least a few drivers I've contributed where I added `depends on UORB` where really it doesn't they can be used as char drivers. True, I think the idea of using the sensor driver that works for uORB as a char device will meet the goal of this Feature Request, we just need to fix the float issue and organize the driver to not include UORB features/functions, could depends on CONFIG_SENSORS_UORB or similar -- 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]
