> On Jul 13, 2016, at 7:38 AM, Tom Zanussi <[email protected]> wrote: > > On 07/12/2016 06:06 PM, Saul Wold wrote: >> On Tue, 2016-07-12 at 10:59 -0700, Jianxun Zhang wrote: >>> This patch seriese introduces new RMC project and RMC distro that's >>> developped based on RMC. >>> >>> The test is done on several boards, including boards checked in >>> examples. (poky:6bb3069; meta-intel: 9bb4622) >>> >>> Some people may have checked implementation before, but I have done >>> a lot refactoring since this week. Now RMC project and RMC distro >>> are splitted and bbclasses are provided for reuse in other clients. >>> These should be the biggest change you didn't see in old code. >>> >>> The last patch in the series adds examples and a new document >>> README.rmc.distro in meta-intel. I think it could make original >>> README too lengthy if we put everyting in README, but let me know >>> if a single readme is still preferred. >>> >> I strongly urge you not to use the word "distro" here or in the recipe >> name. >> >>> README.rmc.distro is designed to be the interfce to new users (and >>> myself). Information of RMC project can be obtained from rmc >>> recipes, bbclass and RMC project's README. I should have left traces >>> to these information in code. >>> >>> Known issues: >>> RMC tool crashes on a NUC gen 4 but doesn't on another sample. Other >>> boards work as expected (nuc gen 6, minnowmax, T100,). >>> >>> Default "install" boot option could be seen although RMC distro >>> always has its own installer effective. This could confuse users when >>> both of install and "RMC install" options show up on the board. >>> >>> >>> Jianxun Zhang (6): >>> rmc: Add Runtime Machine Configuration (RMC) project >>> gnu-efi: Add GUID for SMBIOS 3 entry point structure >>> systemd-boot: load board-specific entry and kernel cmdline >>> EFI installer: deploy board-specific data and kernel cmdline >>> rmc: add recipe and bbclass for feature "rmc distro" >>> rmc: document and examples for rmc distro feature >>> >>> README.rmc.distro | 261 >>> +++++++++++++++++ >> Let's not have the README.rmc.distro in the top level, maybe we need to >> have a documentation directory and we can move this file there. >> > > That would make sense, if it looks like we're going to have more > stand-alone documentation - do you foresee that? > > I guess I don't have a problem with a separate README like this because > meta-intel is supposedly just a temporary stopover for this since it's > ultimately destined for oe-core. Where would this go in oe-core? Tom, I think this feature is generic because it based on EFI and SMBIOS, so most of cases, I assume, targets are X86 arch. That’s why I think some day it should be in OE (as a distro or combined feature?)
However, let’s don’t have such assumption when you review this work because we don’t have a solid plan and more talk with OE people. Just treat this alien as a permanent resident and let me know the best way to put it. I am okay with a doc dir or a single README in meta-intel. I just feel the single text file could be hard to read once more new stuff is in. I will take this chance to add a dir /meta-intel/documentation in V2. Thanks > > Tom -- _______________________________________________ meta-intel mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-intel
