I guess I should clarify the above comments: they reflect concern about trying to document a moving target, not a reluctance to provide documentation.
At present there is no bright line in the Mir code that separates driver related code from the rest of Mir. The closest approximation that exists is libmirplatformgraphics.so - which is GPL code and consumes some C++ interfaces from libmirserver.so while implementing other C++ interfaces. Nothing is currently in place to ensure these interfaces remain stable.
Work has yet to be completed confirming the required licence, API and ABI stability requrements for driver support, then we need to implement and document a solution to these concerns.
I guess I should clarify the above comments: they reflect concern about trying to document a moving target, not a reluctance to provide documentation.
At present there is no bright line in the Mir code that separates driver related code from the rest of Mir. The closest approximation that exists is libmirplatformg raphics. so - which is GPL code and consumes some C++ interfaces from libmirserver.so while implementing other C++ interfaces. Nothing is currently in place to ensure these interfaces remain stable.
Work has yet to be completed confirming the required licence, API and ABI stability requrements for driver support, then we need to implement and document a solution to these concerns.