Hi MeeGo compliance specification doesn't list any mandatory kernel parameters but mentions that might be the case in a later specification version. Currently there is config-generic that is added on top of adaptation config, possibly enabling some things but not disabling anything that was set in adaptation config. Sounds great.
The problem with this is that adaptation config can set a parameter set in config-generic to a different value. Just changing a parameter from built-in (=y) to module (=m) can break things. Policy framework listens for process events through Netlink Connector. For this it needs CONFIG_CONNECTOR=y and CONFIG_PROC_EVENTS=y. On ARM CONFIG_CONNECTOR was changed to =m at some point causing CONFIG_PROC_EVENTS=y line to be ignored and our daemon to hang. Correction for the daemon is ready: now it will silently work but without process events. Not really an improvement. I started looking at merge.pl and was going to suggest adding a third config file containing minimal mandatory parameters that shouldn't be touched but perhaps it's better to have a separate check_mandatory.pl script that will make kernel build fail if some setting is changed by mistake. Any thoughts on this? _______________________________________________ MeeGo-kernel mailing list [email protected] http://lists.meego.com/listinfo/meego-kernel
