| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
The obmc-system-mgmt feature is currently used in the image to trigger
inclusion of a virtual-provider which provides a number of packages many
systems need. Partially revert the removal of this feature so that
the outcome is:
1. The empty obmc-phosphor-sysd package is still removed.
2. By default the 'obmc-system-mgmt' feature is included, unless
specifically exempted.
3. All EVB platforms remove the 'obmc-system-mgmt' feature since
they have no system they are managing.
This partially reverts commit 060ad3ff7fcc30aff78a9e504efee9d8fa0d4526.
Tested:
* Built `bletchley` and confirmed `packagegroup-fb-apps-system` and
`entity-manager` are present.
```
entity-manager armv7ahf-vfpv4d16 0.1+git0+6bf41588ab-r0
packagegroup-fb-apps-system all 1.0-r1
```
* Built `witherspoon` and confirmed `packagegroup-op-apps-system` and
`pdbg` are present.
```
packagegroup-op-apps-system noarch 1.0
pdbg arm1176jzs 3.3
```
* Ran `bitbake -p` on `evb-ast2600` to confirm the undefined
`virtual-obmc-system-mgmt` is not being included in the image.
Change-Id: I8b7804d5101cc84a2c57473b3f85672bf7767c67
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
|
|
Every machine layer treats 'system-management' as either part of a
package-group or removes the feature. The sample implementation in
meta-phosphor is a do-nothing shell script (and up until recently was a
Python script). There appears to be no useful purpose to this feature
as a stand-alone concept, so remove it.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I20ca1fa8ff3cb01cac2d07d4ded84e0769e4514b
|
|
Modify the machine meta-layer configs to remove the use of the
OBMC_MACHINE_FEATURES indirection and favor the Yocto MACHINE_FEATURES
variable instead.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ifafb79e4e4c010e9476b9547cd4982f5b645060e
|
|
1. specify uboot dtb
2. remove unsupported image type
(From meta-quanta rev: 3d624b165aa52925b7b67506f2489bcf686ed20c)
Change-Id: I48c77859213ca37688223e23c04401e4a96619ed
Signed-off-by: Stanley Chu <yschu@nuvoton.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
specify the packages for openbmc chassis/fan/flash/system management
(From meta-quanta rev: 09e8ff20ac73bf1f62dd6d4765ff4de73f853486)
Signed-off-by: Stanley Chu <yschu@nuvoton.com>
Change-Id: I4ac45184159175b44a4e10cd60362d6fb800bbfa
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
The Olympus-nuvoton commuicated with BIOS use KCS channel 1
Setting obmc-host-ipmi-hw use kcs protocol binding KCS1 device
in Olympus-nuvoton
(From meta-quanta rev: 1d11afbf135af12fbb7dd489ed529df7f3a08e31)
Change-Id: If4701303bb2d3ddc6259ba49d905f7a6621b8812
Signed-off-by: Samuel Jiang <Samuel.Jiang@quantatw.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
This variable determines which XML image configuration files will be
used from npcm7xx-igps.
(From meta-quanta rev: 5d54cbf770d5701f0973fcfb8b49ed751532ddd0)
Change-Id: Ic269c8d44e1ea5a0d323ac66e419002307c19051
Signed-off-by: Benjamin Fair <benjaminfair@google.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
For avoid confusing this layer only with RUNBMC module
(https://www.opencompute.org/documents/ocp-runbmc-daughterboard-card-
design-specification-v1-4-1-pdf)
The meta-runbmc-nuvoton will rename meta-olympus-nuvoton.
That means the Quanta Olympus product with RUNBMC module which based on
Nuvoton SoC.
The layer configuration will binding Olympus product hardware design.
(From meta-quanta rev: f4a8e7ae48dc788fa7e52f024578c67f164c8620)
Change-Id: I6faa1bfbb3b8f033239fea3c41e8b8ed18fc492d
Signed-off-by: Samuel Jiang <Samuel.Jiang@quantatw.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
