2010/7/27 Arjan van de Ven <[email protected]>: > On 7/27/2010 9:31 AM, Ameya Palande wrote: >> >> Hi MeeGo Architects, >> >> I wanted to know what features are compulsory for meego kernel to >> provide to meego user space across all the meego certified devices (on >> both the IA and ARM plaforms). One such example can be IPv6. Is IPv6 >> support compulsory in meego kernel? >> >> As maintainer of Nokia N900 kernel, it will be helpful for me know all >> such requirements so that I can build N900 kernel which complies with >> meego kernel guidelines. Correct me if I am wrong but AFAIK there is no >> kernel guideline/compliance document published for meego kernel. >> > > there is... it's even codified in the config-generic config file...
This codification then states CONFIG_X86_ACPI_CPUFREQ=y is mandatory. While I know this is filtered out by kernel build system as it cannot obviously work with CONFIG_ARM=y, it does not give a clear statement what is actually required for all devices running MeeGo and hence a source of misinformation instead. It'd be more suitable to take current config-generic + config-arm, run it through kernel config, check what's common between current config-generic and config-arm (configcommon.pl anyone?), and that's then what is truely required for all devices running MeeGo (at least X86 and ARM as data set) This would be more suitable for config-generic contents to settle all disputes. All archs then inherit from that, like config-x86 which adds all things required for X86 MeeGo (extracted from old config-generic diff from new config-generic) and config-arm for all things ARM MeeGo. Then it's easier to argue about the contents of config-generic. Isn't this cleaner? Best regards, Carsten Munk _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
