Age | Commit message (Collapse) | Author | Files | Lines |
|
The witherspoon and witherspoon-128 machines are mostly the same.
Add "witherspoon" as a MACHINEOVERRIDES to witherspoon-128 so that
machine-specific features that apply only to witherspoon, including
file paths, can be added to both flavors of witherspoon automatically.
Tested: Built witherspoon and witherspoon-128, flashed images on
HW and verified witherspoon powered on.
(From meta-ibm rev: 6f44bb26247289aa46c6d21f04617838e596294a)
Change-Id: I18ce6dd799cb0ab52b37f1f1f3d64c6189af4cd8
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
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:
WARNING: No bb files matched BBFILE_PATTERN_foo-layer
(From meta-ibm rev: ef6380a81fbd701b1052c12c8163498ba4e2de89)
Change-Id: I1f4ab259befb094983df056c0f0f81cf8dc6f2e3
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
This recipe is only required by the legacy inventory manager, which
is no longer used on Witherspoon.
(From meta-ibm rev: 7f405bb87d8ce6a0bb2ac50ca56fab90c8bbddf7)
Change-Id: Ia65e74b5ced87466af076bad7ac3d10ec8dcc279
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
This recipe is only required by the legacy inventory manager, which
is no longer used on palmetto.
(From meta-ibm rev: ba9dd68aa9d524585878eee61e5bfe1bbef0a5f9)
Change-Id: Id2a4be5f97fd91c4aefeaa23f462c8b69cae5de0
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Remove the palmetto override of
PREFERRED_PROVIDER_virtual/obmc-inventory-data as nothing DEPENDS on it.
(From meta-ibm rev: 05d52d6b248c7761e08c02d18cd89c6fd304e062)
Change-Id: Ideabff50e2f492042fe4541a8641f536c14b75f8
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Swift fails to build because fan-presence is a dependency for
fan-control, and fan-monitor is a dependency for inventory.
So add them in swift with an empty yaml file. Also fix the
FILESEXTRAPATHS_append to have the colon at the beginning
(vs prepend where colon goes at the end) to be able to find
the files in the right order.
Tested: Built swift successfully.
(From meta-ibm rev: 2493fdb38e1fe8e1488ea1bcc5c723c788d92bae)
Change-Id: Ie41caf90a15c3c33ef49ce03ce1890ca9f0c7289
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
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:
WARNING: No bb files matched BBFILE_PATTERN_foo-layer
(From meta-ibm rev: 32cabcf8a5f70946d80f51ac41917987f6118031)
Change-Id: Iad810a7a9606a2aee1982337508d1be24cff79f8
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Use the immmediate expansion operator when setting BBFILE_PATTERN. This
makes meta-fsp2 consistent with all the layers in meta-openembedded.
(From meta-ibm rev: a44ea07451e667912a6d99d56d4ae61df92b282d)
Change-Id: Ib2d0daaca371b9c2a837b601a257e498d236688c
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:
WARNING: No bb files matched BBFILE_PATTERN_foo-layer
(From meta-ibm rev: 7d7f662db06cc9f8e4a5bd9d18c68c4bb05d274c)
Change-Id: I0ba9d2a6161b0da271111c710dc3267d0374b2a8
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:
WARNING: No bb files matched BBFILE_PATTERN_foo-layer
(From meta-ibm rev: 8b843642e36fc9d1ac8921a98dd2710dccf1e514)
Change-Id: I5c6102045f5aaa6146dc1902b106063896d073b8
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:
WARNING: No bb files matched BBFILE_PATTERN_foo-layer
(From meta-ibm rev: 1938f1af3bb02726f0046ed737c55a319469e21d)
Change-Id: I6ba0de9fbd44df3da726adecc94d4036b4573bbf
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Make the follow updates to the associations that PIM will create:
Make a new association iface on /system/chassis that contains every
sensor in that chassis, with some exceptions. The forward association
type is 'sensors', and the reverse type is 'chassis'.
The power supply sensors are not included in this new association list,
as the power supplies also now have a new 'sensors' <-> 'chassis'
association that associates power supplies to their sensors, as bmcweb
treats a power supply as a chassis.
Also not included in the new chassis associations are any remaining
power sensors, as bmcweb currently makes fake power supply responses out
of them and we want to avoid that.
The final change is to change the association type of the associations
that point to the sensors on their inventory item from 'sensors' to
'child_sensors', as 'sensors' is required to be used in bmcweb's chassis
handling as mentioned above.
(From meta-ibm rev: 5a4a28582beb2f854d2724e192873536363943da)
Change-Id: Iebd15c4b5a97a16bb614d757ce7621f087777622
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Tell phosphor-inventor-manager to create the
xyz.openbmc_project.Inventory.Item.Chassis interface on the
/system/chassis inventory item at startup.
(From meta-ibm rev: b6e3df22947fa563909d006afc95011a657f5383)
Change-Id: I3576bce35bb3f2687fcd135393dc9b28172dadb8
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Swift uses 2 TMP275s to monitor the PCIE inlet temp, one between
cards 0 and 1, and the other between cards 2 and 3. They are both
on I2C bus 12.
Tested: Built an image and checked rootfs for the config files.
(From meta-ibm rev: bd2a3a2a9b6bde8207f1d4f4a81ffab27f0b14b1)
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I51c449ad9c2a212693d28ed82e79f913bb096e29
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
openpower-occ-control requires a sensor header file generated from
occ_sensor.yaml. By default it uses an example yaml, which does not fit
for Romulus.
Add romulus-occ-control-config-native.bb to use its own
occ_sensor.yaml, so that the package uses the correct config.
Tested: Verify the build uses the correct config generated from
Romulus's occ_sensor.yaml.
(From meta-ibm rev: 54abf3c0be5618333cb37faebc55af48aa2a872b)
Change-Id: Iaa3adf0d20e5b6d080866dd1b19fa3ee7f4d7369
Signed-off-by: Lei YU <mine260309@gmail.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
obmc-control-fan is no longer included by the OpenPOWER layer, so there
is no longer a need to explicitly remove it here.
(From meta-ibm rev: 446d589ce72cebf974ffaca2dca61de2823a140d)
Change-Id: Iba5fc8a745ffb128b83903dc0ad3ad787ebbcd21
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
The sync_inventory_item.py script has been replaced by
first-boot-set-mac.sh. first-boot-set-mac.sh doesn't sync any uuids but
that feature is not required on witherspoon anyway. Remove the config
files for sync_inventory_item.py.
(From meta-ibm rev: e16c109bcd0d38aa5b09ad09d6d31e534f6b198b)
Change-Id: I81553ef7b5ceb13125935c3167f70606e49725b8
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
As openpower-occ-control@1d69e19 introduce the ability to rename the occ
object path, Palmeto could use "occ0" instead of "occ_3_0050" as a
better name.
Update ipmi sensor config to use the updated occ object path.
Tested: Verify occ active sensor is set on host power on, and occ hwmon
sensors are working OK.
(From meta-ibm rev: 17c4a225e74f6b093cf01ca0ecc0c32ae19bc1f8)
Signed-off-by: Lei YU <mine260309@gmail.com>
Change-Id: Iafd029cc82047e047a0dea45ace1655a5bec776d
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
openpower-occ-control requires a sensor header file generated from
occ_sensor.yaml. By default it uses an example yaml, which does not fit
for Palmetto.
Add palmetto-occ-control-config-native.bb to use its own
occ_sensor.yaml, so that the package uses the correct config.
Tested: Verify the build uses the correct config generated from
palmetto's occ_sensor.yaml.
(From meta-ibm rev: 12a660de3fff453e2f24ee2cc98b387fa7b8c541)
Signed-off-by: Lei YU <mine260309@gmail.com>
Change-Id: Ifbf6ffb0c69e6d827410b8370c6481bb953d10d0
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
To support fan control for swift system bring-up, the max31785 device
needs to be configured for hwmon to expose on dbus.
Tested:
All max31785 configs and service files exist in the image
(From meta-ibm rev: 6dec46d2e34e1db46dff141f4495a4aa665af997)
Change-Id: Ib7ebea8cc376f1fb3e2e340d56512440917f1420
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
PS0 uses the same GPIO that witherspoon uses, but PS1
uses GPIOR7 (143).
Tested: Built both images, made sure the correct conf files
showed up in rootfs.
(From meta-ibm rev: c4daa64b614ff35fcefcd6eabcc45f2ac3e54776)
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Ia89e9dbe32db84b265087b775716488da0d48b43
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
To support the swift system bring-up, install the cooling type and fan
control application with minimal configuration to run fans at full
speed(9500 RPMs).
Tested:
Cooling type included in image and configured correctly
Fan control included in image and configured correctly
(From meta-ibm rev: 2eb5a13421e2c5e5bc0a0cfac9de87f0cd8c9c59)
Change-Id: I3359cf0444c1b4af8fae1b7f51ef608e4dc2c4c2
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
In preparation for additional systems under the witherspoon layer, add
the machine name as a prefix to the phosphor-fan* configuration
directories. This allows additional machines' phosphor-fan*
configurations to be placed in this layer.
Tested:
Witherspoon phosphor-fan image still contains applications &
phosphor-fan applications are correctly configured.
(From meta-ibm rev: a63359eebc376e3340bdbc34fc4c83410172a5ae)
Change-Id: I9d711cb68e4563e5a2c6dc88d12d2071364bf8ae
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Tested: The image builds. The generated files look like a good
start at least.
(From meta-ibm rev: affeacabade12b73a4e009c7dd15d1f261db8528)
Change-Id: Id80835c09cde4e6b61d40634406c3fa0e3752097
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
In preparation for additional systems under hte witherspoon layer, add
machine overrides to the hwmon devices and service configurations. This
allows additional machines' phosphor-hwmon configurations to be placed
in this layer.
Tested:
Witherspoon phosphor-hwmon image still contains all device configs &
services to be installed.
(From meta-ibm rev: 84b1f2e70034311853f4e417b9a29687a512cc97)
Change-Id: I28685d71bb99cd23b8a0acc34bfd117dbdef8926
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Add gpio definitions for the Swift machine under a swift subdir.
Move the witherspoon gpio definitions under a witherspoon subdir.
Tested: Built swift and witherspoon and checked that the file
rootfs/etc/default/obmc/gpio/gpio_defs.json was correct
for each machine.
(From meta-ibm rev: dc61626406fc94962d31742832be83e574a28ee1)
Change-Id: I812d1c0547744967d375984552f03f4702439de3
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
The avsbus-control scripts differ between different machine
configurations. Rename the existing ones to witherspoon-* and
add the swift-* ones. Install the appropriate script depending
on the machine being built.
Tested: Built swift and witherspoon and verified that the scripts
rootfs/usr/bin/ were the ones for the machine being built.
(From meta-ibm rev: d95d6afadd61c6ab8276736d719682775d7880d0)
Change-Id: Ib2ee438a0375de0d69dec7ae005118c8fdb46845
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Witherspoon has 2-rotor fans, while Swift has single-rotor fans.
Move the sensors for the 2nd rotor to a witherspoon yaml file.
In the future, any system-specific sensors can be added to the
witherspoon/swift_hardcoded.yaml file
Tested: Built swift and witherspoon and verified only witherspoon
had the new witherspoon_hwmon_sensors.hardcoded.yaml in the
build directory.
(From meta-ibm rev: 160a82111e5ee12066204d71bdbcb6be580e897b)
Change-Id: I31d71c59abfddbc00f97212abf3c126c4ce96a75
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
There isn't an obmc-button-reset package in op-apps in the first place,
so this line is a noop. Remove.
(From meta-ibm rev: 748c1192bf2f2fa6be2cdf5e6f3b88829f28835b)
Change-Id: If34a02d6603834919ab969579c0fca0e0ab28f1a
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Add the inventory association definitions for witherspoon.
With these, phosphor-inventory will create the
org.openbmc.Associations interface on the specified
inventory paths such that the object mapper will create
the association D-Bus objects.
These associations are used to associate inventory paths
to their fans, sensors, and LEDs.
(From meta-ibm rev: 1b3a22abadee18beae8307d1b76e701733281717)
Change-Id: I63d65ce81ee9d0dabe7c2f99d919bd7b115ded66
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Create a new machine for Swift, a POWER9 system.
It is initially based on Witherspoon but with 128MB NOR
flash chips.
- To build this machine:
export MACHINE="swift"; \
export BB_ENV_EXTRAWHITE="$BB_ENV_EXTRAWHITE MACHINE"; \
bitbake obmc-phosphor-image
(From meta-ibm rev: 12b1187ecfcf7d6438cb026d09f2c1b7c6e06cbc)
Change-Id: I304ae026e1b2e027776981865b3f483d0898000f
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Create a machine/witherspoon-128.conf file to model a witherspoon
system with 128MB flash chips.
* New kernel device tree (witherspoon-128.dts).
* Bigger read-write filesystem. Remove the default from the
witherspoon layer (not needed as 6MB is the default) so that the
size value can be overwritten by the witherspoon-128.conf.
- To build this machine:
export MACHINE="witherspoon-128"; \
export BB_ENV_EXTRAWHITE="$BB_ENV_EXTRAWHITE MACHINE"; \
bitbake obmc-phosphor-image
Witherspoon-128 is a system based on Witherspoon but with 128MB
flash chips. Create a device tree for this configuration.
Since this system is just a bringup vehicle, the device tree will
be carried as a patch instead of merging it in upstream linux.
(From meta-ibm rev: 903fd3532aaa967ddc7124095304f50cd4c9557c)
Change-Id: If02e8ad32fc2bff336d16c18513f2c238b28c28a
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
This variable is set to 0x600000 by default in the phosphor layer - no
need to override it again in meta-ibm.
(From meta-ibm rev: 8e50fea4af2e4b1d542cded32a427818e6fc881c)
Change-Id: I64decb22dde26247cc2d1878ab88c3b37803bc3b
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Patrick Venture (1):
build: install into bin instead of sbin
meta-ibm: phosphor-fan: grab cooling-type from bindir
The output binaries from phosphor-fan-presence are now installed into
bin instead of sbin.
Change-Id: I2d42f62b4535775ffd0d1b9473375dd8dc66bb61
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
Signed-off-by: Patrick Venture <venture@google.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Use the new first-boot-set-mac recipe from the openpower layer for
setting the mac address on first boot. This replaces
obmc-mgr-inventory's sync_inventory_items.py script that achieves the
same - but is the last remaining requirement for python on Witherspoon
systems and first-boot-set-mac is shell!
(From meta-ibm rev: 1249fea4137fcf0107a0ad77d78039ddf87c55d4)
Tested-By: Built a witherspoon image and manually verified the root
filesystem included a symlink to first-boot-set-mac@.service
in /etc.
Change-Id: If26c6e2337ec182951a2484a09a4843418716980
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
The upstream 5.0 kernel changed the labels for power sensors. Adjust
the hwmon configuration files to account for this.
(From meta-ibm rev: 222fda96aacb1971094e742e71d6d597985fc927)
Signed-off-by: Eddie James <eajames@linux.ibm.com>
Change-Id: Ibc8921e14b3840959e0793934432ba5615d0b416
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Brandon Wyman (1):
Cleanup: Use filesystem instead of experimental
(From meta-ibm rev: bc6ebec149b2cc8ccd38ddb9775bb7da32b2670b)
Change-Id: Ie232b23cc55e42b6e24d905205255e49bc78a006
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Remove the witherspoon prefix from the witherspoon-pfault-analysis based
recipes for applications and service files to avoid confusion when these
are reused by Swift.
Point to latest commit of witherspoon-pfault-analysis.
Requires:
I4c7275c3b14b3b3724abb98b8d43610df4f9c2a3
https://gerrit.openbmc-project.xyz/c/openbmc/witherspoon-pfault-analysis/+/19399
(From meta-ibm rev: fe3a464e30811d89cad55aab795523fd6152b5a8)
Change-Id: Ic73d31809794b5033126549044d7e4ff00653118
Signed-off-by: Brandon Wyman <bjwyman@gmail.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
ibm-logging was mistakenly removed.
(From meta-ibm rev: 25b56d7eda221f445ccff3393f1be1cb1055d482)
Tested: built WS image and ibm-log-manager found in rootfs
Fixes: 4b2c10ea8e
Change-Id: I07130bfcd6a45a0c5b4a2bf4b406cf300c7bd9d3
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
The distro feature phosphor-isolation is added into openbmc-openpower
distro feature and becomes common for all openpower machines.
So remove them from meta-witherspoon and meta-romulus.
This shall be merged after the commit of adding phosphor-isolation in
openbmc-openpower is merged.
Tested: Verify the Romulus build picks phosphor-isolation distro feature
(From meta-ibm rev: 90f4ccb72200c26d13d3bbd70b6eb7cd90c3dff7)
Change-Id: I8e64bee92eaa7c69928399ceedec6f889a713156
Signed-off-by: Lei YU <mine260309@gmail.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Palmetto is going to enable phosphor-isolation, which requires to use
mbox for PNOR access instead of directly mapping on LPC to PNOR.
Tested: With Palmetto's [dts fix][1] and a PNOR build that enables
[PNORDD_IS_IPMI][2], verify Palmetto boots host successfully.
[1]: https://patchwork.ozlabs.org/patch/1042662
[2]: https://github.com/open-power/op-build/pull/2680
(From meta-ibm rev: 9ba4f883224f2c101b0d4a6df1ddb3cd787a61fa)
Change-Id: I7c225ab2f3afd4d31a217a616bfcc7412805004a
Signed-off-by: Lei YU <mine260309@gmail.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
The biggest change is some device path changes for the
5.0 Linux kernel.
(From meta-ibm rev: a17237d9b1e41d6661d4ae468a3c726b0e0c4ebb)
Change-Id: I717f1a0346f8822cbde049a24af2799a8264ed6e
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Instead of obmc-standby.target, use multi-user.target.
(From meta-ibm rev: 85cff8cc9e66049d8ac26271c13f82d894ac572f)
Change-Id: I03c3d41c031343fa584511889c70e3def92cb83d
Signed-off-by: Patrick Venture <venture@google.com>
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-ibm rev: 97893b2c0bf39cfaee58ccfc4f85249f9a1d8abf)
Change-Id: I2e772add384637011a80acf52861b88ac71be98b
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Patrick Venture (1):
build: install into bin instead of sbin
(From meta-ibm rev: f246cda8a43f2414a8782a806b8080dbf9c8362f)
Change-Id: I797fc67f2597b5187815da29f6fa5164cae649ee
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
There is now a phosphor-network package that is built by the system
instead of a network package. Rename the network bbappend to
phosphor-network to use the new package name.
(From meta-ibm rev: 23e485a291878037f373ee63fae55b1b6c8b33c2)
Change-Id: I0a62840c4fa5631179d6de9579ccd2e823c725e5
Signed-off-by: Patrick Venture <venture@google.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
phosphor-rest-server and phosphor-gevent are no longer the project
defaults so no need to expliclty remove it any longer.
(From meta-ibm rev: 4b2c10ea8e3bf957ea43ccc2957eaf3369d69f96)
Change-Id: I889e2f7bdb93aa6e0ef563263515fc276ee7cd22
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Add a symlink name phosphor-network_%.bbappend that points to the
network_%.bbappend file. This change will allow the recipe
phosphor-network_git.bb to start being used. Once that's in place, the
network_%.bbappend file will become phosphor-network_%.bbappend.
(From meta-ibm rev: 40087d3e904a813790557e0964ec2e301fd2f729)
Tested: Verified the witherspoon image built, but did not test further.
Change-Id: I73d6594c926d0bd7e9edae83bd5527e9ff08b985
Signed-off-by: Patrick Venture <venture@google.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Specify the folder for the extra files explicitly instead of by package
name, such that the package name can change and continue to use this
folder.
This is step 2 of the process to rename network to phosphor-network to
match the general naming convention for phosphor daemons.
(From meta-ibm rev: 286cf25348b68c91bd25151f083001c820bdac15)
Tested: Verified witherspoon image builds.
Change-Id: I011138f732c0a79b60dace9776e7bd6e6163c623
Signed-off-by: Patrick Venture <venture@google.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Out of the box bitbake examines built applications, automatically adds
runtime dependencies and thus ensures any library packages dependencies
are automatically added to images, sdks, etc. There is no need to list
them explicitly in a recipe.
Dependencies change over time, and listing them explicitly is likely
prone to errors - the net effect being unnecessary shared library
packages being installed into images.
Consult
https://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#var-RDEPENDS
for information on when to use explicit runtime dependencies.
(From meta-ibm rev: fa99caa61ecd28325e9070f268a51a5b52363bc4)
Change-Id: Icc97d4b33635caf127a17e70ba6c23f1367eb735
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|