Age | Commit message (Collapse) | Author | Files | Lines |
|
The silkscreen labels were incorrect.
Tested: Verified in the lab physically by changing the PWM and see that
the reported RPMs are correct and matches what the silkscreen report.
Signed-off-by: Brandon Kim <brandonkim@google.com>
Change-Id: I6170f2ebbdbb3d61b3cbc9935e2af02e7abb1a4b
|
|
Since Linux 5.6, the entropy generation provided by rng-tools is now
in the kernel directly. Yocto has removed all dependencies on rng-tools
for packages that use to use it, such as ssh[1]. There isn't any reason
for us to explicitly include rng-tools any longer. Remove the feature
and package group that we had that included it.
[1]: https://lore.kernel.org/openembedded-core/20221209070538.72901-1-xiangyu.chen@eng.windriver.com/
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I85cbe7f30bb41045b7fd1170391a083db9e378b7
|
|
This is required to pick up the glome recipe that was moved from
meta-google to meta-security.
Change-Id: I52790cd2b792ed208498715748e5bed6fb120d20
Signed-off-by: Willy Tu <wltu@google.com>
|
|
bmcweb is not used in gbs anymore and can be removed to avoid building
the recipe.
Change-Id: I23dd4f0d656bb4472d97b8cc2d0053fa31e6d5dc
Signed-off-by: Willy Tu <wltu@google.com>
|
|
The meta-phosphor recipe now includes a variable for setting the cap
on info logs. Leverage that rather than an explicit EXTRA_OEMESON
extension.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ib0bc935691f4e1acb8fb667dffd60df8ce4d8118
|
|
Removing obmc-dmtf-pmci to remove packagegroup-obmc-apps entirely.
Without doing so the gbs image will try to build the
packagegroup-obmc-apps packages.
Change-Id: I3e710cc904344fb86761f5ea5794ef94a506607c
Signed-off-by: Willy Tu <wltu@google.com>
|
|
Patrick Williams (6):
clang-format: copy latest and re-format
writefrudata: remove vla
strgfnhandler: suppress unused parameter warnings
frup: suppress stringop-truncation warning
scripts: accept absolute paths to YAML
build: enable meson builds
build: install strgfnhandler into ipmi-providers dir
Vernon Mauery (1):
Set new maintainer as Patrick Williams
Willy Tu (1):
fru-parser: Remove the use of mktime
Switch to Meson.
Change-Id: Iec9c41cc17a72f84248b8cd75f70353e053f17e2
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
|
|
The latest yocto update is flagging an error on machines using this
recipe. The reason appears to be because the templated services are
added to the SYSTEMD_SERVICE variable but they are not properly
installed into the filesystem.
Install the templated service file utilizing a more direct and tested
method.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I8f856e43244cc766fcec92ba9e21a6b98c9dbd03
|
|
Use the libhoth recipe in meta-security instead of openbmc one. Set the
source rev override until that bump is submitted and subtree updated.
libhoth source bump in
- https://lore.kernel.org/yocto/20230517172730.3837643-1-jebr@google.com/T/#u
Change-Id: I6099d6351417dcef9eb3b4d297de43a5e229d7dd
Signed-off-by: Willy Tu <wltu@google.com>
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I189baf142cc86d44ebbf615edd3bb0ec1785be8d
|
|
The latest version of shellcheck is stricter. Fix a few warnings.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I7f94205aef6d348e9c53dca261ea996dd4f84a6a
|
|
Mapper ships with systemd unit and dbus configuration files now, so
remove unnecessary bitbake classes.
Mapper is dbus-activated, so obmc-mapper.target dependencies are
redundant and no longer necessary.
obmc-mapper.target is the last target in obmc-targets, so remove that
recipe and any dependencies on it.
Change-Id: I59ff8dcd480b4449d0ef59422ba80c12848dade9
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I8e54833ac78e540e9dd5011533d53ff9a3af6763
|
|
The nic-ethtool option was removed from phosphor-network, so we also
need to remove the PACKAGECONFIG option to build the phosphor-network
bump.
Tested:
Confirmed that the latest phosphor-network builds successfully.
Signed-off-by: Jason M. Bills <jason.m.bills@linux.intel.com>
Change-Id: Id1e12f3f2af2450500ec6c0b2acef284cb69d0a7
|
|
This enables timesync support for the gbmc distro.
Change-Id: Idb653e6b98a347b5d8c3a0b3a16c6a4abbe268ac
Signed-off-by: William A. Kennington III <wak@google.com>
|
|
obmc-host-ctl is defined as a MACHINE, DISTRO, and IMAGE feature.
The IMAGE feature pulls in a virtual provider only if the COMBINED
feature (MACHINE + DISTRO) is enabled. This is only done on openpower
machines. There are a lot of other places where machines are half-way
disabling this feature and/or changing variables which have zero effect
anyhow. Clean up almost all references to `obmc-host-ctl`.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I090d782bb6a34dc4e3c43df97e8ccf6e1812fed5
|
|
All of these abstractions have exactly one implementation. Remove the
indirection to improve at a glance comprehension.
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Change-Id: I5d701aff6d0876fa3b2d16c841cbdcb0433b221f
|
|
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I65febeeec11e6e5b40ee728f42cfbe77023dae1e
|
|
We also need to move the conf-notes.txt files.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ic44e015c0216b526de4fec277ad42f162bca1f33
|
|
The latest poky commit is requiring us to have all of
our template configs in a subdirectory instead of directly in
the `conf` directory. Without this we end up with errors during
setup like:
```
Error: TEMPLATECONF value (which is .../openbmc/meta-facebook/meta-bletchley/conf) must point to meta-some-layer/conf/templates/template-name
```
Fix this by moving all of our template files into the 'default'
template subdirectory (following the pattern of poky) and modifying
`setup` as necessary to follow.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Iecefde73d55acbb6bc63ae3d68c4311adaf327ae
|
|
Harvey.Wu (2):
dbus-sdr: fix SEL record Generator ID to fit SPEC
dbus-sdr: fix the vector size in sdrWriteTable and sdrStatsTable
Jian Zhang (1):
Add data types to Value to extend setDbusProperty
Vernon Mauery (1):
fix header install
Willy Tu (4):
cleanup: Remove all warning errors for the Meson build support
build: Add meson build for phosphor-host-ipmi
build: move all shared_library/module to library with version suffix
build: Remove dynamicsensor library if it is not enabled
Change-Id: I92503c6625d1ec2bf88c0a28afac9b4eeb8fbd75
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
Signed-off-by: Willy Tu <wltu@google.com>
|
|
The only recipes which use content from meta-perl are openpower
machines:
```
meta-openpower/recipes-bsp/pdata/pdata_git.bb: libxml-libxml-perl-native \
meta-yadro/meta-nicole/recipes-phosphor/logging/openpower-esel-parser_git.bb: libxml-libxml-perl-native \
```
Remove meta-perl from the bblayers of every layer except openpower
machines.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I51f1a8fbfbe879295c64d2339fc115dbd8823681
|
|
This was added with cde0f094f for libseccomp, but shortly after that
upstream moved libseccomp from meta-security to core (241c7d2e6). As
such, meta-security is no longer used or required.
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Change-Id: I371e54b11f6336720dfc6edf0ef733d22b7fb4f2
|
|
phosphor-dbus-monitor still uses autoconf and has a hard dependency on
phosphor-snmp, causing phosphor-snmp to be brought in on systems that
have no interest in using SNMP. The vast majority of systems do not
supply any config for phosphor-dbus-monitor, so the usage of it does not
seem wide enough to enable the IMAGE_FEATURE by default.
- Remove 'obmc-dbus-monitor' from IMAGE_FEATURE by default.
- Clean up all systems that manually remove the dbus-monitor feature or
package.
- Explicitly add the 'obmc-dbus-monitor' to the following systems:
- meta-ibm: all
- meta-inspur: fp5280g2
- meta-quanta: s6q
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Iad6c4104466e21d1b9843dac964a634019eb6935
|
|
We want it to be possible to order units prior to the powercycle event
if state needs to be persisted prior to a powercycle.
We can also remove the time_delay functionality as this is now provided
globally by the gbmc-psu-hardreset.target.
Change-Id: I15b33e120be0246dd821d0dfe9d61b5aae7d1492
Signed-off-by: William A. Kennington III <wak@google.com>
|
|
Per [1][2], Yocto is starting to deprecate ABORT and has replaced
the "ABORT" action in BB_DISKMON_DIRS entries with "HALT".
1. https://wiki.yoctoproject.org/wiki/Inclusive_language
2. https://git.yoctoproject.org/poky/commit/?id=4f77505d94a8f6260933f457e9848d1d2fa98ce5
Tested:
Built obmc-phosphor-image successfully and eliminate the following
warnings:
```
WARNING: The BB_DISKMON_DIRS "ABORT" action has been renamed to
"HALT", update configuration
```
Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: If57d0ded9fac41e23b31b01e2a0e309ac7388148
|
|
* Deprecate N-1 release (hardknott).
* Enable N+1 release (kirkstone).
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I39e027e02dab64b4390b46ffbd9c299c858f403e
|
|
Noticed that the " were right next to = sign with no spaces. Added
a space between =" in the bbappend file.
Signed-off-by: Brandon Kim <brandonkim@google.com>
Change-Id: I957610d65d1465f268b3b93b4ff565d36020f09f
|
|
As mentioned by I970e06ca6f9d0a9792af122eb25da1bb9a06f058, append and
remove directives with '+=' are no longer valid Yocto syntax and raise a
warning.
See https://git.yoctoproject.org/poky/tree/documentation/migration-guides/migration-3.5.rst#n40
One interesting caveat has to do with the difference between "append"
and "+=".
foo:append = "a"
foo:append = "b"
Results in `foo = "ab"`, but
foo += "a"
foo += "b"
Results in `foo = "a b"`. When `:append +=` is used it has behavior
like the `+=` operator. Therefore, in some cases we need to insert
additional whitespace after the `:append = "` to ensure concatenation
behaves as expected. I've manually reviewed the results to ensure there
is no ill side-effects from an additional space potentially being added.
Fix up the entire tree with the following one-liner (and similar for
`remove`):
git ls-files -- ':!:poky/**' ':!:meta-security/**' \
':!:meta-raspberrypi/**' ':!:meta-openembedded/**' \
| grep "\.bb" | xargs grep -l ":append.*+=" \
| xargs sed -i 's/:append\(.*\)+=\([^"]*\)" */:append\1=\2" /'
or ...
| xargs grep -l ":remove.*+=" \
| xargs sed -i "s/:remove\(.*\)+=/:remove\1=/"
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Iea6235e7c76e252f4d473652957c2925f6b8845a
|
|
Set the max size to 512 since 0x300 is used for something else.
Change-Id: Ic7772247cb3cbcff4a27a12a4f85be97fd6b0b4d
Signed-off-by: Willy Tu <wltu@google.com>
|
|
OperatingSystemState property of
xyz.openbmc_project.State.OperatingSystem.Status should be PDI enum of
type OSStatus.
This commit fixes values to be compatible with PDI.
Signed-off-by: Andrei Kartashev <a.kartashev@yadro.com>
Change-Id: I3e0af91f5ec8f0d9e5f6f722f8161386b9c7b430
|
|
Standard output/error type syslog is obsolete.
Update all unit files, and remove the setting altogether.
Signed-off-by: David Wang <davidwang@quantatw.com>
Change-Id: I9d38713dadd5cca85f0b96f8c217df8afa145add
|
|
`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>
|
|
Change the BIOS main flash label to 'bios-primary' from 'pnor'
for the bios-update.sh
ref: https://github.com/openbmc/linux/commit/2eea476
Signed-off-by: GeorgeHuang <george.hung@quantatw.com>
Change-Id: I208a24cd5f7956cc3461986eb0aed0348c186ebf
|
|
We want the machine layer to be guaranteed to override our top-level
layers.
Change-Id: Ib071dad5b43c112d729bf7f85f36a9f6bd571b31
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
|
|
Kernel crypto/hash API
CONFIG_CRYPTO_HMAC
CONFIG_CRYPTO_SHA256
CONFIG_CRYPTO_USER_API_HASH
The requirement can be found at
https://github.com/systemd/systemd/blob/master/README
This API is necessary for the UUID feature that you can
find the implementation in the bmcweb.
https://github.com/openbmc/bmcweb/blob/master/redfish-core/include/utils/systemd_utils.hpp
Refer https://gerrit.openbmc-project.xyz/c/openbmc/openbmc/+/31523
but these were removed in https://gerrit.openbmc-project.xyz/c/openbmc/openbmc/+/41257
Signed-off-by: JunLin Chen <Jun-Lin.Chen@quantatw.com>
Change-Id: If2dcc552198da05837659a560871db9084e3da37
|
|
This change is a part of the privilege seperation work
which is tracked in:
https://github.com/openbmc/openbmc/issues/3383
This change should be merged after individual repo change:
https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-certificate-manager/+/41166
Signed-off-by: Anton D. Kachalov <gmouse@google.com>
Change-Id: I72e4842e7aa6de2ae4bcbdbf00953b7a79a0f414
|
|
With a recent x86-power-control update, the json file to be parsed is
expected to have a "Polarity" field.
Add the same "Polarity" values for the existing fields.
Reference: https://github.com/openbmc/x86-power-control/commit/50937e7339db744f765efdc3cc58f3d0c5976601
Signed-off-by: Brandon Kim <brandonkim@google.com>
Change-Id: Ia60a87de0d9e3e97dbb03b1f8fb4e9fba32f87a6
|
|
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>
|
|
CONFIG_IPMI_KCS_BMC_CDEV_IPMI=y needs to be added to ensure that KCS
works with the newer KCS driver in OpenBMC kernel.
Signed-off-by: Brandon Kim <brandonkim@google.com>
Change-Id: I12e97559562916acfd64adafbd9e61fe8fb5e672
|
|
Upstream bbclasses changed to typically use the `:${PN}` override
syntax, including the SYSTEMD_ variables. Change our systemd.bbclass
to do the same for consistency and perform a tree-wide variable
replacement.
Spot checked by building bletchley and witherspoon and checking
some of the SYSTEMD_LINK directives on installed packages under qemu.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I20a9dd809bff8af8759488734f80486c7228c6eb
|
|
Some services need obmc-mapper.target to start in correct
order, such as phosphor-virtual-sensors.
ref:
https://gerrit.openbmc-project.xyz/43952
https://gerrit.openbmc-project.xyz/43535
Signed-off-by: George Hung <george.hung@quantatw.com>
Change-Id: Ia463c9f189d715336626ce9e46cad0a370e9b8dd
|
|
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
|
|
This reverts commit 97466ae307a67c30d592c9d97a1e9d6e458e0e5b.
Reason for revert: x86-power-control supports DBUS service name
numbering for single and multi hosts now.
ref: https://gerrit.openbmc-project.xyz/45004
Change-Id: Id1fb9e61a10a457158c52990fe6c196d6fc44708
Signed-off-by: George Hung <george.hung@quantatw.com>
|
|
'SYSTEMD_ENVIRONMENT_FILE', 'SYSTEMD_LINK', 'SYSTEMD_OVERRIDE'
should stay underscore
Signed-off-by: David Wang <davidwang@quantatw.com>
Change-Id: Ia30f306857d1552b19ff5ed06664c8bd5360cb4c
|
|
This is dependent on https://gerrit.openbmc-project.xyz/45865
Signed-off-by: Brandon Kim <brandonkim@google.com>
Change-Id: Ia78c0a9f4bf4b2f97685e187acfeed90d1e0d126
|
|
This reverts commit cf7bc62babb57ea27e7a00cd6271ca53579281fe.
Reason for revert:
Enable fallback watchdog since it is possible that host fails to boot
before enabling the watchdog timer at all.
It was thought that DC cycle may be needed for fallback watchdog but it
is not required.
Signed-off-by: Brandon Kim <brandonkim@google.com>
Change-Id: I8b0f2677f078a091b626536a7ca474afa6ce77d9
|
|
- Cleanup subtree meta-f0b, meta-olympus-nuvoton, meta-q71l with
convert-overrides.py meta-quanta/meta-f0b
convert-overrides.py meta-quanta/meta-olympus-nuvoton
convert-overrides.py meta-quanta/meta-q71l
git grep "_[a-z0-9_/-]*[ :]" -- meta-quanta/meta-f0b
git grep "_[a-z0-9_/-]*[ :]" -- meta-quanta/meta-olympus-nuvoton
git grep "_[a-z0-9_/-]*[ :]" -- meta-quanta/meta-q71l
git grep -l _f0b -- meta-quanta/meta-f0b | xargs sed -i 's/_f0b/:f0b/'
git grep -l _olympus-nuvoton -- meta-quanta/meta-olympus-nuvoton | xargs sed -i 's/_olympus-nuvoton/:olympus-nuvoton/'
git grep -l _quanta-q71l -- meta-quanta/meta-q71l | xargs sed -i 's/_quanta-q71l/:quanta-q71l/'
- Fix up a few by hand
- Revert 'BBFILE_PATTERN' and 'LAYERSERIES_COMPAT'
- Add honister to 'LAYERSERIES_COMPAT'
- Update 'CONF_VERSION'
- Fix up 'SYSTEMD_ENVIRONMENT_FILE', 'SYSTEMD_LINK' and 'SYSTEMD_OVERRIDE' in all subtree
Signed-off-by: David Wang <davidwang@quantatw.com>
Change-Id: Ic431624d09dc5899b1d84439559bea9efca08ad8
|