6362 2014-05-21 21:42:13 +0000 Runtime machine configuration 2016-08-12 13:35:10 +0000 1 1 7 Build System, Metadata & Runtime BSPs bsps-meta-intel 1.8 x86 Multiple RESOLVED FIXED https://bugzilla.yoctoproject.org/show_bug.cgi?id=4011 work post 8761 Medium+ enhancement 2.2 M3 8761 8815 9205 5351 6619 1 dvhart jianxun.zhang alexandru.c.georgescu costin.c.constantin georgex.l.musat jessica.zhang jianxun.zhang jose.perez.carranza ross.burton sgw tom.zanussi francisco.j.pedraza.gonzalez --- --- Yes (doc changes required) oldest_to_newest 43471 0 dvhart 2014-05-21 21:42:13 +0000 In order to fully support consolidated BSPs for meta-intel with intel-core2-32 and intel-coreiy-64 machines, we need to be able to do some basic configuration at first boot, or possibly during "install", to setup various text-based machine specific configuration files. This may include things like: * alsa configuration * kernel boot parameters * network config * formfactor config * xorg.conf Resurrecting / reimagining zaurusd is a reasonable starting point here. 43505 1 ross.burton 2014-05-22 14:53:57 +0000 FWIW X can autodetect modern hardware and works out of the box without a xorg.conf file. EMGD is as ever special, but EMGD tends to need machine-specific configuration anyway. Can you give some concrete examples of what the runtime configuration needs to do? 44498 2 dvhart 2014-07-15 21:49:13 +0000 Assigning to Nitin as he is now reviewing this and will be providing a proposal. 44685 3 dvhart 2014-07-24 23:30:42 +0000 Bug 6209 contains an example asound.conf that is necessary on the MinnowBoard-Max. 45025 4 nitin.a.kamble 2014-08-07 18:46:11 +0000 I had a initial proposal, now trying an initial implementation. 45680 5 nitin.a.kamble 2014-09-18 15:19:03 +0000 This will be going in the meta-intel layer in the 1.7 release. 46548 6 nitin.a.kamble 2014-10-23 17:22:33 +0000 Moving the target milestone to 1.8.M2 47095 7 alexandru.c.georgescu 2014-11-20 09:18:47 +0000 To be discussed internally with Lucian and Costin. 49017 8 nitin.a.kamble 2015-02-24 19:28:39 +0000 The code is available at these locations: http://git.yoctoproject.org/cgit/cgit.cgi/machinesetuptool/log/ http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=nitin/machinesetuptool-20150224 http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel-contrib/log/?h=nitin/machinesetuptool_20150224 I tested the code on emenlow, fri2, crownbay, sugarbay, nuc, jasperforest BSPs, and it worked as expeted. It may need rebase to the latest oecore & meta-intel heads. 56901 9 sgw 2015-12-01 15:53:57 +0000 Moving this out further since we have additional resources now and they need to come up to speed. 62779 10 jianxun.zhang 2016-06-08 17:03:50 +0000 The original requirements that are actually cannot be handled by other scalability or auto-detection features in kernel or system. In a short, these board-spcific deltas is to SoC or a type of physical board and defined by human. RMC under development will allow system to deploy board-specific data onto target within a single image (per arch), so it will address these requirements. 64175 11 jianxun.zhang 2016-07-19 17:21:41 +0000 The latest V2 is submitted to meta-intel mailing list. I believe the original requirements are satisfied because the new RMC feature, based on RMC project, installer, bootloader and recipes, support to: () deploy any board-type-specific files during installation () support a global kernel command line fragment which is effective in any boot entry selected by user to boot a system. () support boot entries which can also have different configurations associated with types of boards. (boot option title, cmdline, etc) Refer to the README.rmc in meta-intel/documentation once patches are merged. 64178 12 jianxun.zhang 2016-07-19 17:27:41 +0000 *** Bug 8761 has been marked as a duplicate of this bug. *** 64956 13 jianxun.zhang 2016-08-08 17:40:40 +0000 RMC feature is merged but not enabled by default in meta-intel. Please refer to documentation/rmc/README as a starting point. https://bugzilla.yoctoproject.org/show_bug.cgi?id=10089 is to track new test cases for this feature, so it is also worthy to check its assignee in QA team.