Maybe the previous post meant that the drivers should/could provide both
interfaces, ie. both the old and the new one?
As in:
Hardware lower-half -> uORB upper half -> chardev
\----> (device-specific) chardev
I think I already saw similar suggestion somewhere and for example
BMP180 driver is implemented that way.
On 2025-12-04 03:59, Matteo Golin wrote:
I believe that is the current implementation:
Hardware lower-half -> uORB upper half -> chardev
On Wed, Dec 3, 2025, 8:21 PM spudaneco <[email protected]> wrote:
What is needed is to be able to share common logic between character
and
uORB drivers. In NuttX this is normally done with an upper half/lower
half
driver architecture. In this case the common, low level, hardware
specific
lower half would be shared by a character driver and a uORB upper
half.
