| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
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 dunsfell (previous).
(From meta-phosphor rev: 49b2a2c56bb774224b15f80deeffff096f59a2db)
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ie37ab65b72c2e10e0324774c56b7968db091ea5b
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>
|
|
Add machine overrides for IBM processors:
- ibm-power-cpu: for any IBM POWER processor
- ibm-power8-cpu: for IBM POWER8 processors
- ibm-power9-cpu: for IBM POWER9 processors
- ibm-power10-cpu: for IBM POWER10 processors
ibm-power-cpu is used when an override applies to any IBM POWER
processor. ibm-power<N>-cpu can be used when a specific override exists
for a specific POWER processor generation.
(From meta-phosphor rev: a59b21d85e90ba5ecfc42e22e751c9dfe6aacb0e)
Change-Id: Ie1eebb677204b9314942f414c10e5dc3134397a9
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>
|
|
OpenBMC only supported 2 layouts: static and UBI. With the
introduction of eMMC, need to change the logic so that
static images are only built if UBI or eMMC are not
specified. Add the default eMMC image types to be built.
Tested: Adding this line to a machine conf only built the
wic image and emmc tarball:
require conf/distro/include/phosphor-mmc.inc
(From meta-phosphor rev: 2f1584b1bec3047944544cfeb5c5539e307f0ecb)
Change-Id: I45569ab375221ac8b9cb7bb045ca88e71cad7286
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Create a distro feature for building images for a mmc chip. This
distro feature would allow to add/remove packages that only apply
to mmc.
(From meta-phosphor rev: 3633bca4309f6aa0417aa86e74f8b39e4d750528)
Change-Id: Icf5c39d7f66fd662dc02479263b67ef674b4b232
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.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>
|
|
(From meta-phosphor rev: 26202e3e79ec092a6af7311b962d81b0576da926)
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ib4fcc31b4d43807cb3b24cf131deca6744ed63d7
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>
|
|
(From meta-phosphor rev: de7df6ae69414c3168d968dccca08d10d10418b7)
Change-Id: Ie1c39397ef6729ef96c4378029646a6d2dac9532
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>
|
|
This is more confusing than anything, our squashfs is compressed with xz
(lzma2) and our kernel supports decompressing xz and lzma types of
initrds. Just use the same type of compression for all images.
(From meta-phosphor rev: 282c6e7254ddc4e79d3545b841c091a671d476ce)
Change-Id: I4ecd7e4d72f4a3b3839402934dad959d90d1cec8
Signed-off-by: William A. Kennington III <wak@google.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>
|
|
OE-core master will be dropping warrior soon; zeus is the next release.
(From meta-phosphor rev: 4a7eb91c9da7ce95d114b3bd435565debbc9b58a)
Change-Id: I7eb11fcf9ed431afb3b8ad5f81fcc60c8d2ec299
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>
|
|
PHOSPHORBASE is only used for pointing at licenses...point at the
licenses in oe-core in meta/files/common-licenses instead. to match the
defacto convention used in other oe layers like meta-openembedded.
(From meta-phosphor rev: a1cee09419cb1467c3d2b7bf996b40089f0d06f4)
Change-Id: If136d24638a8022671988cf0a01620e7fffc545f
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Make stronger assertions about the initramfs images and initramfs image
types to use. Upstream BSP layers may set defaults for these variables
using ?= resulting in the variable settings here being ignored.
(From meta-phosphor rev: 2f24647373e7ecee0afafdbf9e84b6e883422bfe)
Change-Id: I27c316341690ffc3b85f19978aa811ebf84293cf
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Add a distro feature to enable aspeed nic driver to enable MAC1
and MAC2.
The aspeednic patch is copied from meta-ingrasys/meta-zaius, it is
also required by fp5280g2. To avoid duplication, this distro feature
has been added.
Both meta-fp5280g2 and meta-zaius will be updated to use the distro feature.
Tested: tested on fp5280g2, and both Ethernet ports worked
(From meta-phosphor rev: 5a8e7c5a6efea492b82d710c465125fc9d0afdb9)
Signed-off-by: John Wang <wangzqbj@inspur.com>
Change-Id: Ia754595c5e3762f69397c03021ffe29ea5b9afcc
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
The existing scheme for selecting an entity configuration YAML for
building ipmid consists of a virtual (phosphor-ipmi-entity-config) with
the preferred provider set to a default recipe
(phosphor-ipmi-entity-inventory-native) in the Phosphor distro
configuration.
Instead, provide a reasonable default directly in the ipmid metadata.
This is a small step towards enabling ipmid to build without any distro
configuration and should lower the effort required (slightly) to
comprehend where the the entity YAML file is coming from.
There aren't any known clients overriding the entity YAML in the first
place, but a client could still override with an ipmid bbappend and
setting EXTRA_OECONF appropriately.
(From meta-phosphor rev: fe88ee4211c93f4ca4acba5ecec502aef17944ce)
Change-Id: Ie152c413ee6674735b6bf3192b01ec0bc5a39a29
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
All OpenBMC BSP layers have moved to target class config recipes. As
such, support for native class config recipes can be removed.
(From meta-phosphor rev: f3b437c327b94df6f22c7d821f25d76f1d1c2180)
Change-Id: I7729f7e34529a220af36b88017cb48a3ee887acb
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
There exists a number native class recipes throughout meta-phosphor that
simply provide a data (often YAML) file as input to building another
application.
Having these data file recipes implemented as native class recipes
prevents the use of machine overrides because bitbake (rightfully so)
discards machine qualifiers from native recipes. Further, data files
aren't really any different than library header files and those are
consumed by recipes as target class recipes that are DEPENDed on. Do
the same thing for data file recipes.
A number of steps (patches) are required to ensure backward
compatibility while other BSP layers make the transition to target class
recipes.
This patch is the first step in the sequence. Each native class recipe
is duplicated with (approximately) the following transformation applied:
1 - remove "inherit native"
2 - add "inherit allarch"
3 - Add appropriate files to FILES_${PN}
Also fixed a couple idiosyncrasies like SRC_URI += and LIC_FILES_CHKSUM
that are not required.
Finally, add a temporary layer of indirection around STAGING_DIR_NATIVE
and STAGING_DIR_HOST to the fan metadata until other BSP layers have
fully transitioned to target class config recipes.
(From meta-phosphor rev: 19ee51f5cdce2ff2f076a3ca9263dabc79072ba9)
Change-Id: I9671cc5343ed29a7ccfcee4cc00ebaaa9327e359
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>
|
|
Allow another distro building from OpenBMC to specify their own default
virtual/obmc-system-mgmt to allow the meta-ingrasys/meta-openpower
distro-feature virtual/obmc-system-mgmt to set within a system providing
a different default.
(From meta-phosphor rev: 9af5e6419f1cbd9d6ea130812dccb347e4e76e53)
Tested: Zaius image built with correct openpower overrides. Other
platforms built with expected value.
Signed-off-by: Patrick Venture <venture@google.com>
Change-Id: Ieee9d0b3cab9831bfe7201635bb1d79873f79e1c
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Use the immmediate expansion operator when setting BBFILE_PATTERN. This
makes meta-phosphor consistent with all the layers in meta-openembedded.
(From meta-phosphor rev: 8640c4a464677f2e446a13e67686bf1be336fbef)
Change-Id: I23f7fbbcc637e6c6e0a11956a703c0439f53ad4a
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-phosphor rev: 696da8f0734b47c07e0e5179562c24393df9a26d)
Change-Id: I18eb95b6ae926925c1ac48f5ba0d03b3b88e52b2
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
This application doesn't have any in-tree users. As such, drop the
recipe and its dependencies.
(From meta-phosphor rev: 296cc521f5a1c8c87c63a5b475b23c876241bf22)
Change-Id: Ie0ce809f84a133c023f96b4727550690583cb9df
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Point various meta-phosphor recipes to depend on phosphor-network
instead of network. Also, update the default for this feature to be
phosphor-network instead of network.
(From meta-phosphor rev: 98fa96164889d0eed896a731bcfb348d5d802bef)
Tested: Verified meta-ibm/meta-witherspoon built.
Change-Id: I1c4b8fdcb92bf216e50d9f88273a7ac7bdc20213
Signed-off-by: Patrick Venture <venture@google.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
phosphor-host-ipmid no longer does anything with the information
specified by the ipmi-channel-config, therefore drop it.
(From meta-phosphor rev: 14e259d7b53de1bae200ee5c5dbf201ffd105543)
Change-Id: I74057fd68ba7e46e5cf5850eaf6434cb6bb37ec9
Signed-off-by: Patrick Venture <venture@google.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
To provide a custom entity configuration, provide
a virtual phosphor-ipmi-entity-config. The entity.yaml file contains
metadata information for the SDR type 0x08h (Entity Association Record)
(From meta-phosphor rev: 47f26214a916246eeb52a9c2f4045e6375fa0bfe)
Change-Id: I812d5805edd547c2780604119bd6ae3f969d9886
Signed-off-by: Jaghathiswari Rankappagounder Natarajan <jaghu@google.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Allow platforms to opt into the u-boot patch disabling unnecessary
hardware features for ASPEED SoCs.
As this change touches bits that were not initialised by previous u-boot
revisions and the configuration applied prevents poweron of OpenPOWER
hosts without corresponding host firmware changes, this change is
nohwci.
(From meta-phosphor rev: 82f2db28ad8f4f0b7fbf703e8942afcaf6e70a2b)
Change-Id: I2f40a780afe539e9e4ff13983cd567e849bbed25
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Reset the following subtrees on thud HEAD:
poky: 87e3a9739d
meta-openembedded: 6094ae18c8
meta-security: 31dc4e7532
meta-raspberrypi: a48743dc36
meta-xilinx: c42016e2e6
Also re-apply backports that didn't make it into thud:
poky:
17726d0 systemd-systemctl-native: handle Install wildcards
meta-openembedded:
4321a5d libtinyxml2: update to 7.0.1
042f0a3 libcereal: Add native and nativesdk classes
e23284f libcereal: Allow empty package
030e8d4 rsyslog: curl-less build with fmhttp PACKAGECONFIG
179a1b9 gtest: update to 1.8.1
Squashed OpenBMC subtree compatibility updates:
meta-aspeed:
Brad Bishop (1):
aspeed: add yocto 2.6 compatibility
meta-ibm:
Brad Bishop (1):
ibm: prepare for yocto 2.6
meta-ingrasys:
Brad Bishop (1):
ingrasys: set layer compatibility to yocto 2.6
meta-openpower:
Brad Bishop (1):
openpower: set layer compatibility to yocto 2.6
meta-phosphor:
Brad Bishop (3):
phosphor: set layer compatibility to thud
phosphor: libgpg-error: drop patches
phosphor: react to fitimage artifact rename
Ed Tanous (4):
Dropbear: upgrade options for latest upgrade
yocto2.6: update openssl options
busybox: remove upstream watchdog patch
systemd: Rebase CONFIG_CGROUP_BPF patch
Change-Id: I7b1fe71cca880d0372a82d94b5fd785323e3a9e7
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Restrict root user password to obmc-phosphor-image image recipe.
(From meta-phosphor rev: 2ce22326700e4ea1d382081b980bd51447700de6)
Change-Id: Icaab0a1017e8abe54dce0ad5f0ac091f6e2045eb
Signed-off-by: Richard Marian Thomaiyar <richard.marian.thomaiyar@linux.intel.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Moved setting default root user password to
distro instead of applying it in every conf.
Unit-test:
Verified /etc/shadow file updated accordingly.
(From meta-phosphor rev: fd1f696f99eb61fa764d8438f635c6d6a558973d)
Change-Id: I652273b157102600c108d3a547613c11f774aad4
Signed-off-by: Richard Marian Thomaiyar <richard.marian.thomaiyar@linux.intel.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
There aren't any dependencies in meta-phosphor on anything in
meta-webserver, so drop meta-webserver from the sample configuration.
(From meta-phosphor rev: e737217a6a960df6282653dd8db45901cd5c2994)
Change-Id: Icbcd801317c7cef7c0b5e2aeca2c73e1c48e0adb
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>
|
|
Drop preferred version for phosphor-software-manager.
(From meta-phosphor rev: ff01da01dbf6d1671d61deb04be63d1c1fbefa7e)
Change-Id: Icf43892598b2be7d462504a6736bc8d1681dcf65
Signed-off-by: Patrick Venture <venture@google.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
