> For the start, I'd probably pick route (1). Once the new version of
> Sculpt is ready, you could give route (2) a try. Route (3) would make
> sense if you aspire to foster the interoperability between your system
> and Sculpt OS.
Thank you Norman, it all makes sense to me. I'll indeed start w
Hi Cedric,
thank you for sharing your concerns and consulting us for the best
course of action.
I'm in the process of integrating driver_manager into my h/o/g project, to give
it basic dynamic drivers ability (it previously hardcoded Vesa video etc).
After peeking at ticket 5150, I looked in
Fellow Genodians, regarding ticket 5150 : Consolidation of the driver manager
into the sculpt manager ( https://github.com/genodelabs/genode/issues/5150 )
I'm in the process of integrating driver_manager into my h/o/g project, to give
it basic dynamic drivers ability (it previously hardcoded Ves