Age | Commit message (Collapse) | Author | Files | Lines |
|
A few recipes are specifying 'protocol=git' to the git-fetcher, which is
already the default[1]. For github URLs, upstream Yocto / OE suggest
that 'protocol=https' is used[2]. Switch any URL that has a protocol
specified to be 'https' instead of 'git'.
1. https://docs.yoctoproject.org/bitbake/bitbake-user-manual/bitbake-user-manual-fetching.html#git-fetcher-git
2. https://lists.openembedded.org/g/openembedded-devel/message/94255
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ibf1ab0fa2cb83c8cb9f4e535a0781f41e3b0dafe
|
|
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
|
|
Clean up the final part of this indirect, which is the append of the
variable to the MACHINE_FEATURES one.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I2077d7acff5602b7bf333677f5866d979bdaa07c
|
|
Commit aff0243 added seccomp to the systemd PACKAGECONFIG. The
libseccomp recipe requires seccomp be a DISTRO_FEATURE.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Iee1d5e9b2efe8284454c0b5125d9de7b43c1bdb0
|
|
The meta-security layer requires the DISTRO_FEATURE 'security' set
otherwise it gives a warning:
WARNING: You have included the meta-security layer, but 'security'
has not been enabled in your DISTRO_FEATURES. Some bbappend files
and preferred version setting may not take effect. See the
meta-security README for details on enabling security support.
This DISTRO_FEATURE doesn't really seem to do anything except enable
an additional include file in the linux-yocto recipe (which itself
then checks other features). It seems entirely safe for us to enable
this feature everywhere to avoid the warning.
$ git grep -A4 "DISTRO_FEATURES" | grep "'security'"
meta-security/README:to have 'security' in DISTRO_FEATURES to have effect.
meta-security/README: 'security' has not been enabled in your DISTRO_FEATURES. Some bbappend files
meta-security/classes/sanity-meta-security.bbclass: if 'security' not in e.data.getVar('DISTRO_FEATURES').split() and not skip_check:
meta-security/classes/sanity-meta-security.bbclass:'security' has not been enabled in your DISTRO_FEATURES. Some bbappend files \
meta-security/recipes-kernel/linux/linux-yocto_5.%.bbappend:require ${@bb.utils.contains('DISTRO_FEATURES', 'security', '${BPN}_security.inc', '', d)}
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ife1549783b356f87f429466f260f34b9a41d002c
|
|
We want to build OpenBMC on ppc64le, so add it to QEMU_TARGETS.
Signed-off-by: Anton Blanchard <anton@ozlabs.org>
Change-Id: Ice8735a105f40c938dde42061d2e33ddf55a07dc
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I588025b614416c43aa2d053765ab53bacf890cb5
|
|
Improved practice to use DISTRO_VERSION instead of the undocumented
VERSION_ID.
DISTRO_VERSION is documented in yocto
https://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html
and specified in this section about creating your own distribution.
https://docs.yoctoproject.org/dev-manual/common-tasks.html#creating-your-own-distribution
VERSION_ID is undocumented and will more likely be changed compared
to the documented DISTRO_VERSION.
The VERSION_ID is set to DISTRO_VERSION in poky/.../os-release.bb
Use weak default to DISTRO_VERSION instead of overriding VERSION_ID.
This allows other layers to override in *.bbappend or *.conf.
Tested:
```
root@romulus:~# cat /etc/os-release
ID=openbmc-openpower
NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)"
VERSION="2.11.0-dev"
VERSION_ID=2.11.0-dev-165-g20885c497
PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) 2.11.0-dev"
BUILD_ID="2.11.0-dev"
OPENBMC_TARGET_MACHINE="romulus"
```
Signed-off-by: Willy Tu <wltu@google.com>
Change-Id: I25b5a165b764e6562fa8008c9d2a75a82fb09139
|
|
Build QEMU only for relevant targets to speed up compilation process.
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: I67c86d6c8fdd2b4969c35c98bec9d5d2342bbef6
|
|
Add new QEMU targets 'riscv32' and 'riscv64' to be able to
use runqemu script on these architectures.
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: Ib4019e57a0167203fb42c2214a806709a923209a
|
|
DynamicUsers flag in systemd service configuration file required to create,
handle and recycle temporary users.
This is essential module for upcoming daemons' privilege separation work.
Reference: https://github.com/openbmc/openbmc/issues/3383
Signed-off-by: Anton D. Kachalov <gmouse@google.com>
Change-Id: Iabd709c4a20f754fc6ea505e640b2d361aba0be2
|
|
The feature was implemented as an append to the kernel (BSP) layers in
meta-phsophor. This created a three way dance between machine layers,
BSP and meta-phosphor, when it should have been the kernel layer
providing this feature and machines could then opt in.
Fixing this means we could remove the KERNEL_DANGLING_FEATURES_WARN_ONLY
workaround.
As the feature is simply turning on a pair of kernel options without any
other impact, we can implement it by adding the options to our
defconfigs. In fact, aspeed and hpe kernel configurations enable the two
kernel options:
$ git grep CONFIG_KEYBOARD_GPIO=y
meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g4/defconfig:CONFIG_KEYBOARD_GPIO=y
meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g5/defconfig:CONFIG_KEYBOARD_GPIO=y
meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g6/defconfig:CONFIG_KEYBOARD_GPIO=y
meta-hpe/meta-gxp/recipes-kernel/linux/linux-obmc/defconfig:CONFIG_KEYBOARD_GPIO=y
$ git grep CONFIG_INPUT_EVDEV
meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g4/defconfig:CONFIG_INPUT_EVDEV=y
meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g5/defconfig:CONFIG_INPUT_EVDEV=y
meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g6/defconfig:CONFIG_INPUT_EVDEV=y
meta-hpe/meta-gxp/recipes-kernel/linux/linux-obmc/defconfig:CONFIG_INPUT_EVDEV=y
Other machines that wish to enable this feature should ensure it is
added to their BSP's defconfig, or add it to their machine specific
defconfig.
Change-Id: I0726836319022f96c1d13d4a0cbd73708047302c
Signed-off-by: Joel Stanley <joel@jms.id.au>
|
|
Upstream yocto removed these parameters in this commit:
d707fa30f8a24d1e50831846330757254f245791
packagegroup-core-device-devel: remove
https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=d707fa30f8a24d1e50831846330757254f245791
and now builds against a qemu machine fail to build. This commit
removes phosphors use of these items, as it isn't clear what they were
doing for us anyway, which the aformentioned commit also asserts.
(From meta-phosphor rev: 933b75141f46cefe838f298f793f7d49c9f1f2b3)
Signed-off-by: Ed Tanous <edtanous@google.com>
Change-Id: I2c9ab4ade1ac1926094da9102ac2c047baa147e0
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Add a fru-device package, packagegroup, and image feature.
Remove the ipmi-fru distro feature, since adding it in the first place
was a mistake - no projects have conditional ipmi-fru feature flags.
(From meta-phosphor rev: 4525a9d01a5f65438342a894f27c82f0dd61642c)
Change-Id: I6928ac67d4acb4568359a308b45cb0734d116054
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
The ldap and libc-inet-anl DISTRO_FEATURES aren't used anywhere, so
don't set them.
(From meta-phosphor rev: 23140b75afb741ebcd9190efd825b7ef81576e29)
Change-Id: Iba881c25d572397b69b134174336f88b936bddd9
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
152695448 removed our openbmc-phosphor distro override. This had
minimal or no impact because distro overrides based on the DISTRO aren't
being used as they should. Add a distro override so they can be used
where appropriate (e.g. oe-core bbappends).
(From meta-phosphor rev: 1b9a74965ae664726e82ff7941b2d046392fb0f3)
Change-Id: I7ae07ac26c2ea4882d3b1b002b340f53d885c1e8
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Some packages have directory trees of YAML files arranged based on
canonical organization names. See
phosphor-logging-yaml-providers.bbclass as an example.
Add a variable that can be appended to by a layer to limit the number
of 'bbappends' that are necessary in a layer to add their
layer-specific organizations to all the YAML processing recipes.
(From meta-phosphor rev: 2f31e7a7a37f841c1b2586e92258a7759b36306f)
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ie4754ba96a4542ce813869a1384b44ab88000be0
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
We do not use pygobject any more and the PREFERRED_VERSION does
not even exist (python2-based).
(From meta-phosphor rev: 6d6e2b31f98363c39b9b94cd1bdfb518e7669382)
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I8856b0900a1cdb6140b741c3a9639099f1154102
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
DISTRO_FEATURES_LIBC was removed from upstream poky in 2.7 (see
ref-manual/migration.xml), and we use to get ipv4 and ipv6 picked
up as DISTRO_FEATURES as a side-effect of this variable. It was
reported that ipv6 tools were missing from the image, so add this
back directly as a DISTRO_FEATURE.
Also, sort DISTRO_FEATURES_DEFAULT and remove any reference to the
now-deprecated DISTRO_FEATURES_LIBC.
(From meta-phosphor rev: 4877428408c6b2937c6e75d1cdb32f12ad975acf)
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ic0d75deccf57147734849c3800b8b316a60971d0
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
This file originally was not written to be included. Once it was moved
to an include, should have removed the DISTRO override. The gsj system
recently moved to a custom distro that includes this file. Need to
ensure DISTRO is not overridden.
(From meta-phosphor rev: 15269544861c755661981d99711c120fce5410cd)
Change-Id: Iab75967dcaddf0d86b47d4339d82cce43197e73a
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Add an ipmi-fru distro feature. The ipmi-fru distro feature selects
support for the IPMI FRU format.
Initially this will be used by the entity-manager recipe to select the
fru-device meson option provided by that project for building the
fru-device application - an ipmi fru format parsing application with
dbus support.
(From meta-phosphor rev: 5a1fc9e6c9701eebd98c1ac94032206b3879aca1)
Change-Id: I86b8c5d2625b8ea856946e5e4de055bb14f8ffa7
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Remove VIRTUAL-RUNTIME_obmc-settings-mgmt. phosphor-settings-manager is
the de-facto standard for settings management in OpenBMC.
This is a minor improvement to ease of consumption and
comprehensibility. If a popular alternative to
phosphor-settings-manager emerges, revisit the need for this abstraction
then. For un-popular alternatives, bitbake still provides the means for
doing this entirely in downstream layers.
(From meta-phosphor rev: a71cf481ef2f836c839542818e03eda058bc5ef9)
Change-Id: Id563e252c14627e5842c9353e0631901be876326
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
meta-virtualization was dropped from Phosphor OpenBMC awhile back.
There isn't any reason to continue setting this variable.
(From meta-phosphor rev: 5388be3ff1475f9214ff4372acbe6a2f1831bb4d)
Change-Id: I62dc934e07983623e924b657d7373714b42c9fa4
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
There isn't any recipe metadata with any conditional logic around this
distro feature. Remove, for a small improvement to comprehensibility.
(From meta-phosphor rev: b670a101cd22746227ca3fd7ef8615f04aa97fd4)
Change-Id: Ie893015545db146512ef4cb216d94e80e8ac5050
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Remove the obmc-phosphor-user-mgmt distro feature.
It doesn't have any references in any upstream metadata.
(From meta-phosphor rev: 123e391db9b2e23082dc087ae524b2624c6b13c1)
Change-Id: I37fad05647629af78236cd9fea0d1fd4b2faa7dc
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Uninative support was completely removed with commit
70e685ef45a926064d27a2937d6274832c7608b4 but this is a useful
feature on systems that support it (specifically x86_64) because
it enables sstate sharing across various distribution types.
Add in the minimal support for uninative but do not enable it.
This allows someone to optionally enable it by adding the
following to a conf/local.conf:
INHERIT += "uninative"
(From meta-phosphor rev: ea487839ed8566a43e8f9087fba850b1702f9534)
Change-Id: Ifb5ef4aee5886da676f0748c72646a1e8b775658
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
root user account is enabled with proper privilege and group,
only if debug-tweaks or allow-root-login FEATURES is defined.
Note: This will not remove root user getting managed from
phosphor-user-manager, instead it will make sure, the privilege
and groups are empty for the root user.
Tested:
1. Verified the default build, which has debug-tweaks, allowing
root user to be with priv-admin, and enabled for all groups.
2. Verified by removing debug-tweaks from the local.conf, and
root user privilege & groups are empty.
(From meta-phosphor rev: b1b8251f4e5f19189057cdeb998cf119be1c27b8)
Change-Id: Iec2a0b1a9f84c27dd4947125903ce43f3a9c3c2c
Signed-off-by: Richard Marian Thomaiyar <richard.marian.thomaiyar@linux.intel.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Other include files may set DISTRO_FEATURES prior to including this
file. Need to honor those features.
(From meta-phosphor rev: 17801b40a7143c6b80dd4318c94143e47ef1ead3)
Change-Id: I42593e07d67416d2dbb06f3958861ed4ebe762ff
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Right now, nuvoton overrides needed for generating and applying the
bootblock are not applied to images other than obmc-phosphor-image. This
means that core-image-minimal is unbootable on nuvoton platforms.
This change makes the nuvoton overrides apply globally to all images.
(From meta-phosphor rev: 9819cb9533f430797d47dadff558cf4462670976)
Change-Id: If4bef5f8106278fa6ebeb2198bc43fdd2b70a641
Signed-off-by: William A. Kennington III <wak@google.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
All of our images should remove these features as they are unnecessary
and impractical to run on any of our boards. Leaving these enabled for
core-image-minimal made booting take ~60s in userspace and it filled up
the rwfs on my machines. There doesn't seem to be any benefit to
providing these with any of our images currently.
(From meta-phosphor rev: 563b83bf8de93017e16ca46d3013333ee840818c)
Change-Id: Id2d29d27ffba3659b15ce73714b308362d862ec3
Signed-off-by: William A. Kennington III <wak@google.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
All of our images use systemd for booting, so we should deploy
dbus-broker everywhere.
(From meta-phosphor rev: f8196005aefa15dd249ff72036f717b629c8bd4e)
Change-Id: I3010e367a79d782db31050979f5f1bdd30944a11
Signed-off-by: William A. Kennington III <wak@google.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
The kernel version string by yocto by default is <tag>-<revision>, e.g.
5.0.7-b1b37a25644213428f4bab4c427581dd923e35da
Where the revision is the version specified by SRCREV, no matter if
there are additional pathces applied or not.
This commit improves it by
* If there are no yocto patches, keep the current version but use a
shorter revision, e.g. 5.0.7-b1b37a2
* If there are yocto patches, append -dirty-<new-short-revision> to the
version string, e.g. 5.0.7-b1b37a2-dirty-84fa553
Resolves openbmc/openbmc#1289
Tested: Verify the kernel version string is changed as above depending
on if there are yocto patches.
(From meta-phosphor rev: fcfd10d7380309bc274c4f5a8355ecaeb60ce439)
Change-Id: I4210227a981721a6b322d640984ea58c57802cb1
Signed-off-by: Lei YU <mine260309@gmail.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Don't install any locales in an obmc-phosphor-image. The defaults
probably meet most requirements at present and this saves ~128K with an
xz compressed squashfs.
Remove locale setting from distro configuration. The defaults are fine
and this also allows the user to override.
(From meta-phosphor rev: c2207adeb8ecfa1add3868eafc1f0d94d2e503d7)
Change-Id: I2bd5eb4225cfd8f0024b14afc415c0c1bd166484
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Remove shared-mime-info at great flash footprint savings. Savings
is around 800K for an xz compressed squashfs.
This is somewhat of an experiment - the impact of missing
shared-mime-info on glib is unknown.
(From meta-phosphor rev: 9558cc6c1996549eac7b550327f09eff242a1851)
Change-Id: If40f1604ed233c22505d46f8d0213d977c5035c1
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
There are two items in the phosphor distro configuration that originate
in the meta-poky layer. If we can remove these there isn't any need
to include meta-poky in the build layer configuration.
poky-work-exclude: This file is empty; removing is a noop.
poky-sanity.bbclass: This is for sanity checking of the Poky reference
distro, and not the OpenBMC distro (phosphor).
(From meta-phosphor rev: e34a2bcd8a871769c64bcae4e46553103dc952c0)
Change-Id: Idd203805dd16a21314d59eedb3db91a0d193c8bf
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
At present we do not enable the uninative feature because a number of
our build systems are powerpc64le; there isn't any published
uninative tarball for powerpc64le and it isn't clear if uninative
works on non x86 platforms.
None of that changes with this patch, but the method in which it is
removed is...odd - first it is enabled in the usual way but then later
in the distro config it is turned back off.
Refactor and just don't turn it on in the first place.
Note that derivative distros can enable uninative if they don't have any
dependency on non x86 build hosts.
(From meta-phosphor rev: 70e685ef45a926064d27a2937d6274832c7608b4)
Change-Id: If2e343cb79529d1b888289feccd489e151e5a7a8
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
nss-pam-ldapd requires the name service daemon to be
running which provides the cache for the name service
request.
(From meta-phosphor rev: ccf58b533162b8bdd4b8807e549725043b2e9a39)
Change-Id: If6f68d139137b0f0d835fe491e0cd8aa8aaefea6
Signed-off-by: Ratan Gupta <ratagupt@in.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
LDAP related packages will be pulled into the
image depending on the distro feature.
Enabling this feature increases the image size by ~500KB
as it brings nss-pam-ldapd, openldap, and nscd into the image.
(From meta-phosphor rev: b40b3f9b8c9f362583a5edcb6a64f0d3304dad5b)
Change-Id: I92ec1d2c20adfa08a87265d85962cb0390e0c854
Signed-off-by: Ratan Gupta <ratagupt@in.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Spelling errors found using github.com/lucasdemarchi/codespell
A tool to fix common misspellings.
This tool is licensed under GNU General Public License, version 2.
(From meta-phosphor rev: 38f27112a9bc38337d8f4c63c333d2a1f28945fa)
Change-Id: I834b99d63a260f21c60b58c91ec328cf04b683fe
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
This fix allows others consuming the meta-phosphor layer to update
bblayers conf independent of the upstream layer.
Change-Id: I8e170da62d260bbad175ed0fd13407886cb77e7f
Signed-off-by: Dave Cobbley <david.j.cobbley@linux.intel.com>
|
|
The new subtree model brings the subtrees up from the openbmc-machines
layer.
Change-Id: I58a03ae1be374bc79ae1438e65e888375d12d0c0
Signed-off-by: Dave Cobbley <david.j.cobbley@linux.intel.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Since the OpenBMC is it's own distribution, we should not be strictly
dependent upon poky.
Using require poky.conf breaks our ability to update the
variable LOCALCONF_VERSION since it is set to 1 by poky.conf. If we want
to continue getting updates as poky changes, they should be brought over
manually.
Change-Id: I1e098d0e884640f3e0dbb242753656c01f6c1b79
Signed-off-by: David Cobbley <david.j.cobbley@linux.intel.com>
|
|
Yocto 2.5 will bring us a systemd built with meson, so we will no longer
be able to use EXTRA_OECONF to prevent inclusion of the udev database
in images.
Disable it via BAD_RECOMMENDATIONS in the distro configuration instead.
Tested: Built a witherspoon image
Change-Id: I5eb9239a0f41f65df1823bc4ab6f593a31d2f4ec
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
We don't need a distro feature for net IPMI at this point, so
simplify things a bit.
Additionally, remove the net-ipmi virtual since we don't have
any alternative implementations today and it just adds unnecessary
complexity.
Tested: Built a witherspoon image and validated manifest
Change-Id: I2784f13b3e8897e855ac128422081ec3ee207bf1
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Drop support for RHEL6 which has been unsupported by Poky
since 2.1.
This reverts commit c83cf1ce570d4771b1e42ded308bf4110e70408b.
Tested: Built a witherspoon image
Change-Id: Idd8dda940c72a69a7a228733c34018f906ec9b8f
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
There were a number of places that inherited this class but did not
use it. A number of classes that did use it did not inherit it.
This was possible because the class was pulled in by the distro
configuration but that has been removed here as well.
Tested: Built and verified a witherspoon image
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Change-Id: I73511cdcc609875b4fe016967c1b84c5200fb703
|
|
Consider (this is a Yocto verb) a number of backfilled features:
pulseaudio
bluez5
ldconfig
gobject-introspection-data
Put OpenBMC specific distro features in their own variable
DISTRO_FEATURES_OBMC. This has no functional impact but does
make looking at DISTRO_FEATURES with bitbake -e a little easier
on the eyes.
Change-Id: I78a9e2f0807cac41bc119b04b42f32db5d1b9dbf
Tested: Build and verified witherspoon and palmetto images
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Using MRW or not is distro policy. As such remove the obmc-mrw
machine feature.
Do not enable the remaining obmc-mrw distro feature in the base
phosphor distro configuration.
Create new distro configs for the systems that use MRW today
(i.e. Witherspoon) that enables the obmc-mrw distro feature and point
the local.conf.sample at the new distro configuration.
Change-Id: If4cedc745b3ee942518fbfd4d5cf2cd5b60f346d
Tested: Built a Witherspoon image and validate the manifest
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Enable other distro config files to require/include a proper include
rather than directly including openbmc-phosphor.conf
Tested: Built a Witherspoon image
Change-Id: I2e94c9a7f9ecc1527ece86099407cdc4f34a5e36
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|