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.
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?
Assigning to Nitin as he is now reviewing this and will be providing a proposal.
Bug 6209 contains an example asound.conf that is necessary on the MinnowBoard-Max.
I had a initial proposal, now trying an initial implementation.
This will be going in the meta-intel layer in the 1.7 release.
Moving the target milestone to 1.8.M2
To be discussed internally with Lucian and Costin.
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.
Moving this out further since we have additional resources now and they need to come up to speed.
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.
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.
*** Bug 8761 has been marked as a duplicate of this bug. ***
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.