| 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>
|
|
We want the machine layer to be guaranteed to override our top-level
layers.
Change-Id: I9737762255be61e5af2c32881d7024133f72bf1e
Signed-off-by: William A. Kennington III <wak@google.com>
|
|
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>
|
|
Remove the unneeded obmc packages and add specific ones that are used.
Signed-off-by: Vivekanand Veeracholan <vveerach@google.com>
Change-Id: I80472124ec1af684ebbd502219c8ae6d9f8fcee9
|
|
We've typically kept these LAYERSERIES_COMPAT to 2 releases: the current
and the upcoming. Remove 'gatesgarth' is it is now 2 releases back.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I5e812a94fed1738898af75c0fdee81996a5bbf20
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I569f08159a5da3d148f63a5b1ed29b5cd52181db
|
|
Cleanup with
```
convert-overrides.py meta-quanta/meta-gsj
git grep "_[a-z0-9_/-]*[ :]" -- meta-quanta/meta-gsj
git grep -l _gsj -- meta-quanta/meta-gsj \
| xargs sed -i 's/_gsj/:gsj/'
```
Note:
Need to revert the change to BBFILE_PATTERN and LAYERSERIES_COMPAT.
After cleanup
```
$ git grep "_[a-z0-9_/-]*[ :]" -- meta-quanta/meta-gsj/ | grep '.bb'
meta-quanta/meta-gsj/recipes-bsp/u-boot/u-boot-fw-utils-nuvoton_%.bbappend:do_install:append:gsj () {
meta-quanta/meta-gsj/recipes-google/ipmi/google-ipmi-sys_%.bbappend:do_install:append:gsj() {
meta-quanta/meta-gsj/recipes-gsj/detect-fan-fail/detect-fan-fail.bb:do_install:append:gsj() {
meta-quanta/meta-gsj/recipes-gsj/quanta-nvme-powerctrl/quanta-nvme-powerctrl.bb:do_install () {
meta-quanta/meta-gsj/recipes-phosphor/fans/phosphor-pid-control_%.bbappend:do_install:append:gsj() {
meta-quanta/meta-gsj/recipes-quanta/network/mac-address_%.bbappend:do_install:append:gsj() {
```
Change-Id: I058371ed32214d665aaaf616a650c2efeaf5be66
Signed-off-by: Willy Tu <wltu@google.com>
|
|
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>
|
|
The ipmi command checks the FRU device's Present property upon a
FRU device info reading request.
The fru eeprom devices is availabe in dbus, but cannot
be accessed by ipmi.
```
$ ipmitool fru
FRU Device Description : Builtin FRU Device (ID 0)
Device not present (Requested sensor, data, or record not found)
FRU Device Description : hsbp (ID 1)
Device not present (Requested sensor, data, or record not found)
```
Google-Bug-Id: 186454762
Change-Id: I173c8b3a43dc117f026908d035a00cf49a4e90f5
Signed-off-by: Willy Tu <wltu@google.com>
|
|
Latest upstream yocto has moved on to the 3.3 hardknott release
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Ieae36798d66d21c2c642931f06407d3bb2acf163
|
|
This layer provides libseccomp.
Signed-off-by: Anton D. Kachalov <gmouse@google.com>
Change-Id: I84513d56f2ed75fab49043196b98ef8b858e394f
|
|
The next release of Yocto is soon and most of the upstream
layers have switched support strings for it. Support layer
compat for gatesgarth (current) and dunfell (previous).
(From meta-quanta rev: 34f30a0dca7ab63d93d56132f93e96244b02aeff)
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I388aa5bf43235718668da109ebdb800e27b856d0
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Upstream is in the process of reworking how ldap user management is
included (or not) - moving from a distro feature to an image feature.
Opt out from the new image feature to avoid picking up the ldap user
management packages when upstream makes the switch. There is no longer
any need to remove ldap from DISTRO_FEATURES, so remove that.
(From meta-quanta rev: a6a05a72f7a39af65a5fa28c56650e774fe12e6d)
Change-Id: Ica159c232dad540246166d571e5e3e7bc1824c01
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
The obmc-host-ipmi feature pulls in phosphor-ipmi-hw-example from
skeleton which isn't needed.
Also remove obmc-control-chassis, which is another skeleton recipe that
isn't needed on gsj.
(From meta-quanta rev: 2a53c3569af7fa1b0e1736d179e8178ffecf427d)
Change-Id: If47d92c581859719de148e09127f34a3f208adf9
Signed-off-by: Benjamin Fair <benjaminfair@google.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
(From meta-quanta rev: cbd23c178e4a13d876c5f4fd0ca111f8fec43a83)
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Idd24cffd70bbb8b9cd9f11e746c0759874ed8a95
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Save room in flash by taking out some binaries that are unused.
This includes defining a new distro based on Phosphor that removes LDAP,
SLP, and Avahi as these are not used.
(From meta-quanta rev: c27ca70b613310ffc4ac41b11b361691e99fc0f3)
Change-Id: Ia22da47136c715734d2df6fb767fee2e53f9bbaf
Signed-off-by: Benjamin Fair <benjaminfair@google.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
This variable determines which XML image configuration files will be
used from npcm7xx-igps.
(From meta-quanta rev: c14953708446f32cc95f5b9a33bef6a0683b522d)
Change-Id: I86390644d88156c5afd91ecaccc8c43b2b0bd88b
Signed-off-by: Benjamin Fair <benjaminfair@google.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
OE-core master will be dropping warrior soon; zeus is the next release.
(From meta-quanta rev: bee6771b647c0da99af4d06a3f60b7445d8427aa)
Signed-off-by: Patrick Venture <venture@google.com>
Change-Id: I7c5f88138fffd3ef7649270bc2e44354450018a8
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Remove gbmc-psu-hardreset.target from google-ipmi-sys to get
DelayHardReset to return the expected unspecified error.
(From meta-quanta rev: c95abb8caea6e56de78f009338ed656518928566)
Signed-off-by: P.K. Lee <p.k.lee@quantatw.com>
Change-Id: I910d976c0b37b88523e3351ad83ce60124cd28df
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Bitbake uses this regex to associate recipes and bbappends from BBFILES
(which contains recipes and bbappends from -all- layers listed in
bblayers.conf) to this layer. The association is then used to map the
BBFILE_PRIORITY value for this layer onto the recipes provided by this
layer.
BBFILE_PRIORITY is used to determine which recipe to use when the same
recipe appears in multiple layers.
Without BBFILE_PATTERN set, recipes in this layer will get a default
priority and not the priority specified in BBFILE_PRIORITY.
This layer doesn't set a priority anyway, so functionally this patch is
a noop but it is an improvement from a correctness standpoint, and it
makes a warning go away.
(From meta-quanta rev: 029742e6738abb943ebe74681435df99f31f4e72)
Signed-off-by: Patrick Venture <venture@google.com>
Change-Id: Ia0c21a2353f7d8e60b5981691c18ededa43dc6e1
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Add the led configuration for meta-gsj
- Enabled the LED group manager
(From meta-quanta rev: 8fafb59db0a032b581c8465392577403717ac011)
Change-Id: I027ee78275a3a274462918c7c630cd6a02ab25ee
Signed-off-by: tony lee <tony.lee@quantatw.com>
Signed-off-by: Tien-hung Huang <buddy.huang@quantatw.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
A number of corequisites exist so squashing these all into one patch.
meta-ingrasys - refresh master bc513127f4..67bcaf389f
meta-hxt - refresh master 86a4df514f..8fe0d38bbb
meta-phosphor - refresh master 06c09d7cce..df6ddae3d2
meta-quanta - refresh master 4f126361a1..53f3025271
Change-Id: I3daeef2a0467d8ea4f1fd1c617e526f8b11258af
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
oe-core branched in preparation for the upcoming 2.7 Yocto release and
as of 13e45ff requires core layer compatibility to "warrior" instead of
"thud". We'll retain compatibility for both until we do our own branch
or stop testing thud.
(From meta-quanta rev: 4f126361a17e37cfc96d5f9ccd5e3b81fa8b5ae2)
Signed-off-by: Patrick Venture <venture@google.com>
Change-Id: I0a6cc767e787cef3d31d75b987b9369e44a7afc9
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Update fru information of project gsj and test on gsj board pass.
(From meta-quanta rev: 4726abcab724b6e8a5abb5dca1603857a294ea97)
Change-Id: I3efbc10722f956c7375e1513bb71a39186c12cdd
Signed-off-by: Duke Du <Duke.Du@quantatw.com>
Signed-off-by: FranHsu <Fran.Hsu@quantatw.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
The system manager (obmc-mgr-system) which provided GPIO
functionality is being deprecated and it's not in use anymore:
* GPIOs have moved out of D-Bus (see openbmc/openbmc#3332).
* Tools depending on its GPIO functions have been updated to
call local functions instead.
* The systemd service files have been updated to not depend
on system manager.
(From meta-quanta rev: 602f74d56aeabe7c30748576ad6085ed761498fe)
Change-Id: I76e683ed246bc055c54754bfc9d819f50e708eb3
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Tested: This commit included the basic machine config
and package group setting for project GSJ.
And it could build successfully with meta-nuvoton fix
(https://gerrit.openbmc-project.xyz/#/c/openbmc/openbmc/+/17719/).
But the built image cannot run on EVB now,
it is because the image generate script still not ready yet.
(From meta-quanta rev: e08538d3df34128ef92c0593c1556931e62c614a)
Change-Id: I2724915dd674bbce0db16a3714bc50cf8993f9b9
Signed-off-by: FranHsu <Fran.Hsu@quantatw.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
