3 ms·

Do you have a link to this assumption? I would really like to know.

by prg318 14y ago

shmerl 14y ago
I found these: * https://wiki.ubuntu.com/MirSpec#Mir_on_the_Free_Graphics_Driver_Stack https://wiki.ubuntu.com/MirSpec#Mir_on_the_Free_Graphics_Dri... * https://wiki.ubuntu.com/MirSpec#Mir_on_HW_Supported_By_Closed_Source_Drivers https://wiki.ubuntu.com/MirSpec#Mir_on_HW_Supported_By_Close... we are in contact with GPU vendors and are working closely together with them to support Mir and to distill a reusable and unified EGL-centric driver model that further eases display server development in general and keeps cross-platform use-cases in mind. I hope the later means Wayland compatible drivers, because if not - it's going to be bad.
- noahl 14y ago
  My interpretation (and apologies if this is obvious to you) is that they will define certain interfaces between the driver and the outside world, and any manufacturer will be able to provide something (a library or a daemon, I guess) that implements those libraries. When they say "cross-platform use-cases", I think it means they want to make it easy to build the Mir driver and Android driver from the same source tree - and quite possibly the Windows and OS X driver too. So hopefully they will have some quite general interfaces. I think the ideal scenario is that the driver interface they define has a very general interface, and then there's a wrapper that turns that interface into an Android driver, another that turns it into a Wayland driver, another that turns it into an OS X driver, and so on. But I don't know if graphics drivers would accept the performance penalty of even a very thin wrapper.
  - shmerl 14y ago
    I see all this as a huge waste of effort, unnecessary complications and increasing confusion. The main drive behind this seems to be desire of Canonical to control the development (they can't do that with Wayland), rather than any valid technical reason. Quite disappointing. Here is what Wayland / X.org / Mesa developers have to say on this: http://www.phoronix.com/scan.php?page=news_item&px=MTMxNzY http://www.phoronix.com/scan.php?page=news_item&px=MTMxN...

Do you have a link to this assumption? I would really like to know.

by prg318 14y ago

Do you have a link to this assumption? I would really like to know.

I found these: * https://wiki.ubuntu.com/MirSpec#Mir_on_the_Free_Graphics_Driver_Stack https://wiki.ubuntu.com/MirSpec#Mir_on_the_Free_Graphics_Dri... * https://wiki.ubuntu.com/MirSpec#Mir_on_HW_Supported_By_Closed_Source_Drivers https://wiki.ubuntu.com/MirSpec#Mir_on_HW_Supported_By_Close... we are in contact with GPU vendors and are working closely together with them to support Mir and to distill a reusable and unified EGL-centric driver model that further eases display server development in general and keeps cross-platform use-cases in mind. I hope the later means Wayland compatible drivers, because if not - it's going to be bad.

noahl 14y ago
My interpretation (and apologies if this is obvious to you) is that they will define certain interfaces between the driver and the outside world, and any manufacturer will be able to provide something (a library or a daemon, I guess) that implements those libraries. When they say "cross-platform use-cases", I think it means they want to make it easy to build the Mir driver and Android driver from the same source tree - and quite possibly the Windows and OS X driver too. So hopefully they will have some quite general interfaces. I think the ideal scenario is that the driver interface they define has a very general interface, and then there's a wrapper that turns that interface into an Android driver, another that turns it into a Wayland driver, another that turns it into an OS X driver, and so on. But I don't know if graphics drivers would accept the performance penalty of even a very thin wrapper.
- shmerl 14y ago
  I see all this as a huge waste of effort, unnecessary complications and increasing confusion. The main drive behind this seems to be desire of Canonical to control the development (they can't do that with Wayland), rather than any valid technical reason. Quite disappointing. Here is what Wayland / X.org / Mesa developers have to say on this: http://www.phoronix.com/scan.php?page=news_item&px=MTMxNzY http://www.phoronix.com/scan.php?page=news_item&px=MTMxN...