Graphics drivers are apparently enumerated twice

[Daniel van Vugt]

Graphics drivers are apparently enumerated twice. You see "Found graphics driver ..." twice for each driver on startup:

[1431414947.491685] mirplatform: Found graphics driver: dummy
[1431414947.491780] mirplatform: Found graphics driver: android
[1431414947.492154] mirplatform: Found graphics driver: mesa
[1431414947.493288] mirserver: Starting
[1431414947.493648] mircommon: Loading modules from: bin/../lib/server-modules/
[1431414947.493720] mircommon: Loading module: bin/../lib/server-modules/graphics-dummy.so
[1431414947.496745] mircommon: Loading module: bin/../lib/server-modules/graphics-android.so.2
[1431414947.497768] mircommon: Loading module: bin/../lib/server-modules/graphics-mesa.so.2
[1431414947.497816] mircommon: Loading module: bin/../lib/server-modules/input-stub.so
[1431414947.498892] mirplatform: Found graphics driver: dummy
[1431414947.498932] mirplatform: Found graphics driver: android
[1431414947.499124] mirplatform: Found graphics driver: mesa
[1431414947.499329] mirserver: Selected driver: mesa (version 0.14.0)

It's not a regression either. The duplication also occurred with the old warning message that the "Found graphics driver" message replaced (LP: #1438536).

[Alan Griffiths (alan-griffiths)]

AIUI that's "as designed".

/1/ the platform is loaded to query its configuration options and unloaded; then,
/2/ the command line, environment and config file are parsed; and finally,
/3/ the platform is loaded using the configuration options.

I guess it ought to be possible to remember the platform chosen in step /1/ and avoid re-scanning the available platform modules.

[Michał Sawicz (saviq)]

Syncing task from Mir.