Greys Baseline
Overview
Kernel Branch: Mainline
Cygwin: cygwin-20140401
Compiler Version: GCC 4.6.1
Expected cert: May of 2017
Using Customers:
- Caseys_Program: Could move to Handies_Baseline
- Cava_Program: Could move to Handies_Baseline
- Dosa_Program
- Lefse_Program: Could move to Handies_Baseline
- Louie_Program
- Surcouf_Program
- YahMon_Program: Could move to Handies_Baseline
This baseline and distrobution is intended for single-core Kernel users who wish to have a Verified set of components and tools for PowerPC platforms.
Notes
OpenArbor
OpenArbor is being locked to the 8.7.2+ release. Future versions support Sybil for IOI and IST. This requires ioi_init calls to be updated to not assume ioiConfig.cfg but instead to generate a matching filename to pass to ioi_init based on the active registry name. The examples are already locked for dist-greys due to the examples moving forward with type updates to support multi-core versions of the kernel.
If we receive a future greys customer we may want to do the work to branch the examples and move to the latest OpenArbor. Until then Surcouf_Program is the only active customer and is moving into the verification phase, where a locked development environment is ok.
Symbolic Links
| Link | Assignee | Rationale |
|---|---|---|
| deos-products/video/system-video-stream/dist-greys -> 6.6.1 | RLF | See #cd.xml |
| deos-products/video/video-lib/dist-greys -> 7.3.1 | BC | readme.txt See #cd.xml |
| deos-products/debugger/gdbserver/dist-greys -> 8.1.2 | BC | readme.txt See #cd.xml |
| deos-products/math/ppc/dist-greys -> 0.0.0 | AL | removed (most) dist-* links, added stable link and readme. |
| deos-products/inetd/dist-greys -> 7.0.0 | BC | readme.txt See #cd.xml |
| deos-products/gnu/gcc/dist-greys -> 4.6.1 | RLF | Decision was for greys to stay with GCC 4.6.1 toolset |
| deos-products/status-monitor/status-monitor/dist-greys -> 8.12.0 | RLF | See #cd.xml |
| deos-products/mtl/library/dist-greys -> 2.2.2 | RLF | See #cd.xml (verified) |
| deos-products/dart/dart/dist-greys -> 1.2.1 | BC | Grey's needs latest-verified |
| deos-products/arinc653/cvt/dist-greys -> 1.2.4 | GK | Grey's needs latest-verified |
| deos-products/arinc653/cvt/dist-greys-unreleased -> 1.2.4 | GK | Grey's needs latest-verified |
| deos-products/compiler-support/gcc/dist-greys -> 7.3.0 | JON | Greys needs latest-verified |
| deos-products/ioi/buffering/ring/dist-greys -> 4.0.3 | GK | Grey's needs latest-verified |
| deos-products/ioi/buffering/ring/dist-greys-unreleased -> 4.0.3 | GK | Grey's needs latest-verified |
| deos-products/ioi/api/dist-greys -> 4.0.2 | GK | Grey's needs latest-verified |
| deos-products/ioi/api/dist-greys-unreleased -> 4.0.2 | GK | Grey's needs latest-verified |
| deos-products/network/network-drivers/rtl-bouton/dist-greys -> 0.3.0 | RLF | See #cd.xml |
| deos-products/network/network-drivers/rtl-bouton/dist-greys-unreleased -> 0.3.0 | RLF | See #cd.xml |
| deos-products/network/network-drivers/rtl81xx/dist-greys -> 2.1.0 | RLF | See #cd.xml |
| deos-products/network/lwip/dist-greys -> 3.11.0 | GK | Was locked for compatibility with louie driver mpc5676resci. That driver will be updated and then link removed. greys unreleased will pick up lwip 3.14.0 |
| deos-products/kernel/hyperstart/dist-greys -> 8.7.0 | RLR | Removed. |
| deos-products/kernel/kernel/dist-greys -> 8.4.0 | RLF | Renamed to stable so applies to handies as well. Once latest-verified link added greys should be frozen. |
| deos-products/kernel/kernel/dist-greys-unreleased -> 8.4.1 | RLF | Renamed to unreleased so applies to handies as well. Once latest-verified link added greys should be frozen. |
| deos-products/socket/sal/dist-greys -> 2.3.2 | RLF | See #cd.xml (verified) |
| deos-products/dev-flash-c90/dist-greys -> 1.0.0 | MH | With development of differing memory map options, this one was missed. Good news, no one is using this or likely to use it directly. Good/Bad news, the unreleased version 1.0.1 which supports the hyperstart load features on the Louie target is in the delivered Image 0 and works properly, but if the user attempts to rebuild and load a new Image 0, the 1.0.0 version of the library would be be loaded and fail to load hyperstart images properly. Changes to the library were prompted by investigation into kernel test failures on this target. Recommend getting 1.0.1 to stable for consistent distribution. |
| openarbor-products/component-descriptors/dist-greys -> 2.3.0 | RLF | See #cd.xml |
| openarbor-products/component-descriptors/dist-greys-unreleased -> 2.4.0 | RLF | See #cd.xml |
cd.xml
cd.xml files can come from two places, the component-descriptors package (old style), and from each individual component (new style). Mostly greys is using "old style". More specifically:
The generic component-descriptors package 2.4.0 provides the following cd files:
- Unverified Components
- gdb-server
- image-api
- inetd
- network
- rtl81xx
- rtl-bouton
- status-monitor
- video
- Verified Components
- dart
- deos-653-p1
- ioi-api
- mtl
- ring-buffer
- sal
- Obsolete Components
- emac[-prl]
- etsec
- marvell-egiga
- tsec-durant
Since kernel, ANSI and math are undergoing verf in greys, the decision was to pull these verified components out of the generic package so they would use the new style of delivering .cd.xml content for all post fourpeaks work. We could have also pulled out the unverified components listed above. However, in addition to cd files some of these components come with fp files which could potentially change the RAM usage from what was previously used. Without looking into any impacts for small RAM targets (greys primary focus) we locked greys and ensured that multi-core and any future uni-core distributions would get the updates. A closer inspection for greys could result in a new component-descriptors that only includes the verified components to avoid capsule releases, and then remove the corresponding dist-greys links.
If any of the network drivers under obsolete components are used by a platform in a going forward distribution (multi-core/handies) then those drivers will need to be updated to release their cd.xml.
