Age | Commit message (Collapse) | Author | Files | Lines |
|
`BBLAYERS_NON_REMOVABLE` is obsolete and no longer required.
As it said by Yocto documentation it can be used by `Hob`
https://www.yoctoproject.org/docs/1.5.2/ref-manual/ref-manual.html#var-BBLAYERS_NON_REMOVABLE
that already removed since Yocto-2.1
https://www.yoctoproject.org/tools-resources/projects/hob
Change-Id: Ibc2d8268a9d837a81e9cf6b0131dba8d0a030a3f
Signed-off-by: Alexander Filippov <a.filippov@yadro.com>
|
|
The phosphor-pid-control package will be provided through
obmc-fan-mgmt, so it does not need to be provided through
obmc-fan-control as well.
Signed-off-by: Charles Boyer <Charles.Boyer@fii-usa.com>
Change-Id: I29ac8363056db866d6181d958d8a86e53605400d
|
|
Change-Id: I8711fa16a624c9f132310357f973cebd25f9b1d3
Signed-off-by: William A. Kennington III <wak@google.com>
|
|
Summary of changes:
1. Adjust start time of xyz.openbmc_project.State.Chassis.service
to fix initial chassis state
2. Add shutdown ack service
3. Remove reset ack service
4. Remove heartbeat mode
5. Remove sysreset pin control from power_control.exe
6. Remove all phosphor-fan services that caused power off during
a system reset
7. Adjustments to ampere_power_util.sh (See below)
ampere_power_util.sh:
1. Use GPIO instead of dbus for host state
2. Wait 3 seconds before checking power status for power on
3. Wait 6 seconds before checking power status for power off
4. Have force_off act GPIO while power_off sets Chassis state
5. Graceful shutdown acts GPIO
6. Check host status before issuing system reset
7. Set Watchdog Expire Action to None before power off and reset
Signed-off-by: Charles Boyer <Charles.Boyer@fii-usa.com>
Change-Id: Ie2720ee60d489c4160165c6827a78a400ae4d30b
|
|
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
|
|
bitbake offers a choice of DEB, RPM or IPK packaging. To a degree the
choice is functionally arbitrary for image generation but control over
the package format becomes important if we want to:
1. Include runtime package management functionality in the firmware image
2. Mess about with the packages on the build system
With respect to 1 the IPK format and opkg (an ipk package manager) are
designed for embedded systems[1] - by contrast to RPMs have heavier
dependencies and a greater impact on the size and complexity of the
firmware image.
Regarding 2, the embedded nature and the need for opkg to work without
much fuss leads to a lower configuration barrier by comparison to RPMs.
With ipk it becomes possible to reuse the packages built during image
preparation for core analysis without needing to generate an SDK:
```
$ export LD_LIBRARY_PATH=./tmp/work/x86_64-linux/opkg-native/*/recipe-sysroot-native/usr/lib
$ MY_DEBUG_ROOT=tmp/rootfs-debug
$ ./tmp/sysroots-components/x86_64/opkg-native/usr/bin/opkg \
-f ./tmp/work/p10bmc-openbmc-linux-gnueabi/obmc-phosphor-image/*/opkg.conf \
-o $MY_DEBUG_ROOT \
update
$ fakeroot ./tmp/sysroots-components/x86_64/opkg-native/usr/bin/opkg \
-f ./tmp/work/p10bmc-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/opkg.conf \
-o $MY_DEBUG_ROOT \
install dbus-sensors dbus-sensors-dbg
$ gdb-multiarch
(gdb) set solib-absolute-prefix .../tmp/rootfs-debug
(gdb) add-auto-load-safe-path .../tmp/rootfs-debug
(gdb) file tmp/rootfs-debug/usr/bin/nvmesensor
(gdb) core-file obmcdump_17_9597/core.nvmesensor.0.aae91b519d0e4e0e8bbe746e3f6cd25f.2779.9594000000
Core was generated by `/usr/bin/nvmesensor'.
Program terminated with signal SIGABRT, Aborted.
pthread_kill.c:45
45 pthread_kill.c: No such file or directory.
(gdb) bt
pthread_kill.c:45
../sysdeps/posix/raise.c:26
/home/andrew/src/openbmc/openbmc/build/p10bmc/tmp/rootfs-debug/usr/lib/libstdc++.so.6
/home/andrew/src/openbmc/openbmc/build/p10bmc/tmp/rootfs-debug/usr/lib/libstdc++.so.6
/home/andrew/src/openbmc/openbmc/build/p10bmc/tmp/rootfs-debug/usr/lib/libstdc++.so.6
/home/andrew/src/openbmc/openbmc/build/p10bmc/tmp/rootfs-debug/usr/lib/libstdc++.so.6
"xyz.openbmc_project.NVMeSensor", this=0x488f04) at
/usr/include/sdbusplus/bus.hpp:234
../../../../../../workspace/sources/dbus-sensors/src/NVMeSensorMain.cpp:159
(gdb)
```
This approach documented in the Poky Reference Manual:
https://www.yoctoproject.org/docs/1.0/poky-ref-manual/poky-ref-manual.html#platdev-gdb-remotedebug-launch-gdb-inferiorbins
Switch all machines to IPK to align the debugging experience with
upstream's documentation and to facilitate efficient use of packaged
software at runtime.
[1] https://openwrt.org/docs/guide-user/additional-software/opkg
Change-Id: I8ef526add2d7a6790de1b3eb3fb85cd39b864f23
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
|
|
Signed-off-by: XP Chen <xiao-peng.chen@fii-na.com>
Change-Id: I276c7333f9f01949db2387735edb5d9a97c4fa1d
|
|
Add PREFERRED_PROVIDER_virtual/bmc-update in kudo.conf to fix
bmc_update build conflict with gbmc's bmc_update.
Signed-off-by: Mustafa Shehabi <mustafa.shehabi@fii-na.com>
Change-Id: Ideb5cbde0f4c94c7197984c1641223da1583111d
|
|
Adding chassis management packages
Signed-off-by: Mohaimen Alsamarai <mohaimen.alsamarai@fii-na.com>
Change-Id: I334f925414815961fd9e6dcb309a52c14d670f03
|
|
Changing the syntax for various yocto files ie. (_ to :) changes to
bb, bbappend and conf files.
Signed-off-by: Mohaimen Alsamarai <mohaimen.alsamarai@fii-na.com>
Change-Id: If25577ee9d98398c1a1ab7f85a0373c46af70245
|
|
add BMC version in distro/openbmc-kudo.conf
add Gbmc.conf
add dev_id.json
Signed-off-by: Lancelot Kao <lancelot.kao@fii-usa.com>
Change-Id: I84c6d735cfad55abaa272edab1d10b4b9d4b0d99
|
|
1. Fix kernel_partiton offset after changes to upstream
2. Fix mac address settings for eth1
Signed-off-by: XP Chen <xiao-peng.chen@fii-na.com>
Change-Id: Ia959dadce1c3336e4860c205d5702b186d11beff
|
|
This is apparently not actually working anymore and is removed in the
next poky update.
Change-Id: Ia1c6a258d124a4a30a14fc42e8e0bba95e64faeb
Signed-off-by: William A. Kennington III <wak@google.com>
|
|
Remove obmc-health-monitor
Signed-off-by: Mohaimen Alsamarai <mohaimen.alsamarai@fii-na.com>
Change-Id: I3a842f4a16212d143c8feb6b06ace1f7e074cb1c
|
|
Change the provider(kudo-fw) from virtual-obmc-system-mgmt
to virtual-obmc-flash-mgmt to avoid overwrite by
other package
Signed-off-by: Mohaimen Alsamarai <mohaimen.alsamarai@fii-na.com>
Change-Id: I55fad7c3a778ce9478313cd5303137622ea6741c
|
|
Using phosphor-pid-control
Signed-off-by: Mohaimen Alsamarai <mohaimen.alsamarai@fii-na.com>
Change-Id: Iea73a96bf4d8921d717fcf335ec463d0054089a5
|
|
Setting compatibility to the hardknott openbmc version
Signed-off-by: Mohaimen Alsamarai <mohaimen.alsamarai@fii-na.com>
Change-Id: I86786013fcb3ed8614ab0f101ad21a3b1f16f456
|
|
1. support the Ampere host and SCP
Signed-off-by: Lancelot Kao <lancelot.kao@fii-usa.com>
Change-Id: Ifb07bac01264c8d04741e6996f421ab457291d39
Signed-off-by: Mohaimen Alsamarai <mohaimen.alsamarai@fii-na.com>
|
|
1. support the NCSI interface
Signed-off-by: Lancelot Kao <lancelot.kao@fii-usa.com>
Change-Id: I345d59e5ea527be344b5e53b64d62ef54f72c868
Signed-off-by: Mohaimen Alsamarai <Mohaimen.alsamarai@fii-na.com>
|
|
1. Uses gbmc mac configure
Signed-off-by: Lancelot Kao <lancelot.kao@fii-usa.com>
Change-Id: I5be8c415152983d9d6792d38ed42fe3ae0de9017
Signed-off-by: Mohaimen Alsamarai <Mohaimen.alsamarai@fii-na.com>
|
|
1. add kudo-bios-update package to support bios update
Signed-off-by: Lancelot Kao <lancelot.kao@fii-usa.com>
Change-Id: Ic245828ed3bb0ddf6d7363e7c2c4d3b8b538aa88
Signed-off-by: XP Chen <xiao-peng.chen@fii-na.com>
Signed-off-by: Mohaimen Alsamarai <Mohaimen.alsamarai@fii-na.com>
|
|
1. use the SSIF bridge interface
Signed-off-by: Lancelot Kao <lancelot.kao@fii-usa.com>
Change-Id: I5a6116a975e536b6180a692392cef4c58ebed7b8
|
|
1. update the flash layout
Signed-off-by: Lancelot Kao <lancelot.kao@fii-usa.com>
Change-Id: Ie4d8589ebb96696ac0840a8cca286456a5bef2eb
|
|
This layer provides libseccomp.
Signed-off-by: Anton D. Kachalov <gmouse@google.com>
Change-Id: I84513d56f2ed75fab49043196b98ef8b858e394f
|
|
Most openbmc machines use DISTRO="openbmc-phosphor" but
Kudo has a "openbmc-kudo" distro config file. This config
file has nothing except an inclusion of the phosphor one, so
remove this useless indirection.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I0b973cc5aaa4af97fcfd6bd14ed12f70fd2e540f
|
|
First drop for the meta-kudo layer, initial machine configuration
to supports Nuvoton npcm730 chip and the Ampere ARM system
Tested-by:
1. Load image on the Nuvoton RunBMC CRB
2. Use ipmitool to test the command under BMC console
a. ipmitool mc info
b. ipmitool sdr
c. ipmitool lan print
d. ipmitool channel info 1
e. ipmitool user list 1
f. ipmitool chassis status
g. ipmitool raw 0x06 0x01
h. ipmitool power status
Signed-off-by: Lancelot Kao <lancelot.kao@fii-usa.com>
Change-Id: Ic34b77affe0c08e84762ef795f9f06011bd269ce
|