| Summary: | Default module selections need attention | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] BSPs | Reporter: | Paul Eggleton <bluelightning> |
| Component: | bsps-configuration | Assignee: | Bruce Ashfield <bruce.ashfield> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | minor | ||
| Priority: | Medium+ | CC: | alexandru.c.georgescu, dvhart, jessica.zhang, richard.purdie, sgw, yp.bsp.watcher, yp.watcher |
| Version: | unspecified | ||
| Target Milestone: | 2.2 M4 | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | Unknown (Hard to categorize) |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Paul Eggleton
2012-02-16 02:26:42 UTC
post 1.2 seems appropriate for this. I'll be looking into this anyway for activities that happen in the future. For 1.2, we will be tuning the configs for the base/standard/default path, which means that you will get fewer modules in general. I'd prefer to not control this (completely) via the board configs in the kernel itself, since driving packaging issues/concerns into the tree isn't quite where we want them. Since we re-use the tree in several places and ways. Using the MACHINES variables seems reasonable to me. sized. This can be a sub task of the configuration policy audit for 1.3 Moving to M4, where we'll introduce the release candiate kernel version. Bumping the milestone to reflect reality. This work will happen on the 3.10+ kernel. Moving to 1.6, this was partially done in 1.5, but not enough to close the bug in good faith. Logging more items (we'll call these phase2): LTP tests, IO tests Concurrency tests RT jitter and latency tests Fault injection test drivers IP block PnP tests Power management tests, RTPM and Legacy PM Platform "ABI" tests (DMI, SMBios, AML correctness and introspection) Pretty much any burn in or Power On test case and common performance KPI. (In reply to comment #6) > Logging more items (we'll call these phase2): > > LTP tests, > IO tests > Concurrency tests > RT jitter and latency tests > Fault injection test drivers > IP block PnP tests > Power management tests, RTPM and Legacy PM > Platform "ABI" tests (DMI, SMBios, AML correctness and introspection) > Pretty much any burn in or Power On test case and common performance KPI. Maybe you intended this for Bug 5569? Argh. Yes, fixing the case. (In reply to comment #7) > (In reply to comment #6) > > Logging more items (we'll call these phase2): > > > > LTP tests, > > IO tests > > Concurrency tests > > RT jitter and latency tests > > Fault injection test drivers > > IP block PnP tests > > Power management tests, RTPM and Legacy PM > > Platform "ABI" tests (DMI, SMBios, AML correctness and introspection) > > Pretty much any burn in or Power On test case and common performance KPI. > > Maybe you intended this for Bug 5569? Moving this to 1.7, since we'll be doing this as part of "developer experience" I was surprised to see minix.ko even getting built for qemuppc... (In reply to comment #10) > I was surprised to see minix.ko even getting built for qemuppc... Indeed. There's a wholesale purge and changing of the default configuration that is being scripted as the first pass in cleaning up the options. Only the hardcore minix users need to turn that back on ;) This is dependent on the linux-yocto re-factoring that is currently on review on the mailing list. When that merges, this can complete. The timeline is still TBD for that, since the patches are only in review. We've done all the factoring that is intended for the 2.1 release, moving this to 2.2 where we'll continue to work on this and have more incremental updates under this bug number. I'll do one more quick pass on this, and if nothing obvious jumps out, I'll close this and re-open more specific ones for future releases. putting the milestone where it was supposed to be :D We've gone as far as planned for this in the 2.2 cycle. New bugs will be opened to track meta data updates in the future. |