| 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
|
|
The `PREFERRED_PROVIDER` still uses `_` instead of `:`, fix it.
Signed-off-by: Lei YU <yulei.sh@bytedance.com>
Change-Id: I34f27870ff35de8b14a8a546d42ab4a1fb5f30d1
|
|
convert-overrides.py meta-bytedance
git grep -l _g220a -- meta-bytedance | grep ".bb" | \
xargs sed -i 's/_g220a/:g220a/'
git grep -l _u-boot -- meta-bytedance | xargs sed -i \
's/_u-boot/:u-boot/'
Tested:
$ git grep "_[a-z0-9_/-]*[ :]" -- meta-bytedance | grep ".bb"
meta-bytedance/meta-g220a/recipes-phosphor/chassis/x86-power-control_%.bbappend:do_install:append() {
meta-bytedance/meta-g220a/recipes-phosphor/configuration/entity-manager_%.bbappend:do_install:append() {
meta-bytedance/meta-g220a/recipes-phosphor/console/obmc-console_%.bbappend:do_install:append() {
meta-bytedance/meta-g220a/recipes-phosphor/ipmi/phosphor-ipmi-ipmb_%.bbappend:do_install:append(){
meta-bytedance/meta-g220a/recipes-phosphor/ipmi/phosphor-ipmi-kcs_%.bbappend:do_install:append() {
meta-bytedance/recipes-core/systemd/systemd-conf_%.bbappend:do_install:append() {
meta-bytedance/recipes-core/systemd/systemd_%.bbappend:do_install:append () {
Signed-off-by: Lei YU <yulei.sh@bytedance.com>
Change-Id: I26fb4c52012ee407ceb26c5a4120bf7b0b7a165a
|
|
The upstream has defined the 64MiB layout, use the upstream one.
Tested: Verify g220a's image boots fine in QEMU.
Signed-off-by: Lei YU <yulei.sh@bytedance.com>
Change-Id: Id69df5796c11f1d86bc1340fdb7127f0eb3f3e18
|
|
Use the new u-boot-aspeed-sdk as the uboot.
Tested: Verify the image boots u-boot in g220a QEMU, and boots the
OpenBMC if bootcmd is modified to fit the image.
Signed-off-by: Lei YU <yulei.sh@bytedance.com>
Change-Id: I93c3a083a81f09d37627749c8d0692ae9a75466a
|
|
G220a is an x86 server platform with an ast2500 BMC
(From meta-bytedance rev: f6d9fbafdfa3e5b0088f4d72792f2f3a031009a6)
Signed-off-by: John Wang <wangzhiqiang.bj@bytedance.com>
Change-Id: Ie0851a3e689fa7348cbb812e9ff51ea570632123
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
