Age | Commit message (Collapse) | Author | Files | Lines |
|
ssh://git-amr-1.devtools.intel.com:29418/openbmc-openbmc into HEAD
|
|
Mihawk can use GPU, so fan control must support GPU thermal sensor.
Tested: Fan speed is automatically controlled when using GPU
(From meta-ibm rev: 2ecdfbd9911c5df8909089d87774a768cfb06716)
Change-Id: I7a62dd349a72c1c3fb6dc314e7a011afb51e75b1
Signed-off-by: Ben Pai <Ben_Pai@wistron.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
To allow thermal modes to be selected at BMC standby, the fan control
application must be running. The phosphor-fan-control@.service file is
needed to start fan control at BMC standby and the
phosphor-fan-control-init@.service is no longer required.
Tested:
Witherspoon phosphor-fan-control@.service replaced in image
phosphor-fan-control-init@.service removed from image
fan watchdog configs appended to fan control service still
phosphor-fan-control@.service started at BMC standby
fan control thermal modes presented/changeable at BMC standby
no function change in configured thermal modes
(From meta-ibm rev: f59761e1af85b3ae6432bf0297f5cfe5be71e557)
Change-Id: I4a946f58b6f0c22ebd402304ae9d8fd17a197571
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Per review comments, change device paths to symlinks thought to be more
stable.
(From meta-ibm rev: ad75a64d9b120f9b9ed0453acca1da2bf119e78e)
Signed-off-by: Jim Wright <jlwright@us.ibm.com>
Change-Id: I925dac346368a0a40fa64948ac7f640c33f15019
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
On witherspoon-tacoma the GPIO that specifies if the system is water
cooled is Q7 (135). Update phosphor-cooling-type's config file
appropriately.
(From meta-ibm rev: 5d62a1c264bd72d9070e046a5ec10ad9b8715392)
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I63131a81ecb984e7746e54a98c539a52d887e155
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
The check_pnor_format checks if the PNOR is formatted as UBI,
so it should only be added if the UBI feature is enabled.
(From meta-ibm rev: 091f26661b09c9d0a6f6b632b40cc8a84eac25c3)
Change-Id: Ief252652cd347a0bf4a8f8eb592672d0e9740514
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
It is not yet supported in the kernel.
(From meta-ibm rev: 37b0344925323c3de0bd86fd00ea075e383153da)
Signed-off-by: Joel Stanley <joel@jms.id.au>
Change-Id: Ie09afb9a4ee1d96d7b2a70fe79ef9a85d8971ea2
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Utilize the pgood property as a precondition to loading fan control
events based on property states other than the OCC active events. Since
the OCCs are not active when powered off (pgood = 0) those events having
OCCs active as a precondition are not necessary to be added.
This is the first step to enabling fan control to run at BMC standby.
When the default phosphor-fan-control@.service starts after power on,
the pgood property value is already set to 1. Therefore this produces no
change in fan control activity.
Tested:
No change in fan speed control
(From meta-ibm rev: dadf39cdbb093e0c2566189f3e876dd3c01e13d0)
Change-Id: Ieb010804d59ed318463fca1fcbdce5b5123b81df
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
ipkvm is not needed for the witherspoon-tacoma system. May bring this
back in some day for testing purposes but there are no near term plans
to use or support this.
(From meta-ibm rev: 3e11092404f8512241209c4ea26988171cf35263)
Change-Id: Ibb0bc351504070661179491d07f3af144cc97602
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Add Rainer power-on configuration support and remove unused GPIOs.
(From meta-ibm rev: 114bd7308d03fe7949517cd939b6dd9f575d59cb)
Signed-off-by: Jim Wright <jlwright@us.ibm.com>
Change-Id: I29df80c5d446ebcba929cef334f06969c258f5d9
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Add Rainier system power sequencer configuration file.
(From meta-ibm rev: 65ba7af3ef1f36b4b77c5776478b59d1a7bf2334)
Signed-off-by: Jim Wright <jlwright@us.ibm.com>
Change-Id: Ia55257b24e1e5095bbd9db24fbf67e5968c4f9cc
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
ipkvm is not needed for the rainier system
(From meta-ibm rev: 556f78bc1a4c0d02496e79754fa6fa7147c98e02)
Change-Id: I79f19dca7024025efcbe25ac3a55df9bf047bcbb
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
This system's GPIO layout is different than witherspoon's.
(From meta-ibm rev: e401c9560f4f7d85952d1630095df9ad784de0b2)
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I4ed9f1de4b25258e791a514643863494a99fde3d
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
witherspoon-pfault-analysis is promoted to phosphor-power:
https://lists.ozlabs.org/pipermail/openbmc/2019-August/017729.html
This patch does the first migration step which is to point this recipe
at the canonical repository.
A subsequent step could be adding a phosphor-power recipe in OpenBMC's
meta-phosphor.
(From meta-ibm rev: de9a39f0a56410de046a260b51ca7ff9f162b12c)
Change-Id: Ib6af976ac3b82d37f96dea4b45bba730ca98753d
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
IBMBASE 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-ibm rev: 9585e66aba26c0c0c7b10ed2552f3e42aaae078c)
Change-Id: Iec1fe1ed7cd96615c51d5e81be60f4189c8e970c
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Brad Bishop (3):
build: fix some warnings
build: add support for building with meson
build: drop autotools
(From meta-ibm rev: 23d2feff13ee457a36f13bb6d615d0a11cc2428b)
Change-Id: Icb648c74c18d203318692cfb5febc8672a437b95
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Get total power from occ.
(From meta-ibm rev: 5f74841d980f274383dd0bf1c16b1c3df18142e2)
Signed-off-by: Ben Pai <Ben_Pai@wistron.com>
Change-Id: I97bf6b2229890dca1a0bda421b85b10392c2a814
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
IBMBASE 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-ibm rev: cbbb0e5b4e44d831fce5daafd13272d401440f40)
Change-Id: Ib214f92b2c384e3eb2a1f53ecf4b21034438d001
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
(From meta-ibm rev: effd83bdc65d9ae8f9d000205f8d55e0c29557e4)
Change-Id: I5d8fb1cd15e0b0bf2c2360631be8f259f42be98f
Signed-off-by: Alvin Wang <alvinwang@msn.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Now the mihawk fan event will build error on openbmc master.
So I made some changes in order to solve the problem.
Tested: Verify fan control functionality of mihawk image
(From meta-ibm rev: 3e3ec10428cabe6917ea982159565024fcd21f9b)
Signed-off-by: Ben Pai <Ben_Pai@wistron.com>
Change-Id: I84aa7e8fd85dba15a5a84bbf7944bb286e5ba9ae
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Add mihawk's ipmi sensor and fru yaml.
Tested: Use ipmi command to get the sensor list and fru data.
(From meta-ibm rev: 05c9a2734de75271837313f0e1794c58df50e990)
Signed-off-by: Ben Pai <Ben_Pai@wistron.com>
Change-Id: Ic85af9b0cc1b44a3377fa919e63ab04dbff7a31c
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Witherspoon has only one LAN interface which is channel number 1.
The json file provided by the phosphor layer has channel information
for two LAN interfaces. The phosphor layer config file is modified to
mark the channel number 2 as reserved.
(From meta-ibm rev: 48dc78b5e8b6deba59e4aa200b8d88f10e277b69)
Change-Id: I4af0b7e682d2ec266831c7053926d1515f62c726
Signed-off-by: Tom Joseph <tomjoseph@in.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Enable this config for mihawk so the fan sensors are working, otherwise
hwmon will fail and exit when fans are not working.
Tested: Verify that the fan_tach sensors return -ETIMEOUT when host is
powered off and do not exit with failure.
(From meta-ibm rev: 2e39633c12f7914b1a4a398bbff9b467930bb731)
Signed-off-by: Ben Pai <Ben_Pai@wistron.com>
Change-Id: I0a7e881de5d5baa8d4db3cac9ca3cb46ec08faf4
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Most of mihawk's sensors are different from witherspoon, so I temporarily
added the mihawk part and did not change the witherspoon.
Add mihawk version of fan control and d-bus monitor.
Mihawk does not have a water cooled mode, so another independent folder is added.
Tested: 1.Shut down the system if more than three cores
have a temperature greater than 100 degrees Celcius.
2.Fan control support cpu core, dimm, Onboard.
3.Confirm that sensor is able to return normally via REST.
(From meta-ibm rev: 949f91431bba2f0139cc823d674a741f9590c885)
Signed-off-by: Ben Pai <Ben_Pai@wistron.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Change-Id: Icc401f32c67b622f0f1448e1166112e02c135a8f
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
BMCWeb uses ObjectMapper associations to find sensor information for
Redfish. Due to BMCWeb enhancements for the Power and SensorCollection
schemas, the following Witherspoon association changes are required:
* Remove the "chassis" <-> "all_sensors" association for power supplies.
Power supplies were considered chassis by BMCWeb as a short-term
solution, but they have been moved to the Power schema.
* Add the power supply sensors to the "chassis" <-> "all_sensors"
association for the top level chassis.
* Add other missing power sensors to the "chassis" <->
"all_sensors" association for the top level chassis. These
associations were temporarily removed due to limitations in the BMCWeb
support for power sensors. These limitations have been addressed.
See https://github.com/openbmc/docs/blob/master/sensor-architecture.md
for more information on sensor associations used by BMCWeb.
(From meta-ibm rev: a1c35f612f58e5453fe988d59db21a8673fdcfa4)
Change-Id: Ibea5bdea58711e96faff4937ecccedcc695d9ba4
Signed-off-by: Shawn McCarney <shawnmm@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
As on Witherspoon, some VRMs on Swift need their AVS buses enabled
as part of the power on sequence. The AVS bus connects those VRMs
to the processors so the processors can set voltages.
On Witherspoon, the sequence was
1. Disable the AVS bus
2. Manually set VRM voltages
3. Enable AVS bus
Currently on Swift there is no need to manually set voltages, so
the AVS bus disable service and script isn't required.
Tested: Tested on swift, and ensured both witherspoon and
witherspoon-128 still have all avs scripts and
services installed.
(From meta-ibm rev: f1ceece0b75a4522ef3089319b12d22fd83ed9ef)
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Ifd7ebdd5ec3dcdfef97c04e666d83fcb4991b452
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
This extension will (when it's complete) create IBM's Platform Event
Logs (PELs) for every OpenBMC event log, as well as provide features
to exchange them with the host, package them for Redfish, etc.
(From meta-ibm rev: 625fc419ae882dd572a1045bdca3286b896a69fe)
Change-Id: Ia215ce221ac58037c0f8029362181dde8a94d42e
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
The contents of this up-stream include the following items
1.Basic function
2.Led settings
3.GPIO monitor (id button and power supply)
4.Linux dts patch.
(From meta-ibm rev: c53430a2234917b71f29d7e61d6aea749c45a2fc)
Change-Id: Id0e47fd9197c8b2a70cbc94888bd572255664cdd
Signed-off-by: Ben Pai <Ben_Pai@wistron.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
A recent kernel update added a second input current/voltage/power
reading to the hwmon sysfs attributes for the ir35221 VRMs, and it threw
off the labels in the config files since they were hardcoded for the
specific previous numbers. For example, curr2_input previously
represented an output current but now represents an input current.
Fix this by using the LABEL mode in hwmon to find which sysfs file to
use for a particular sensor by the contents of its corresponding label
file. For example, the p0_vdd_current sensor should look at the sysfs
file that has a corresponding 'iout1' value in the currX_label file.
Tested: Test that the voltages are back within thresholds again and not
showing values around 12V.
(From meta-ibm rev: bca7ed0127f9e82895fb60b66b325347970f0860)
Change-Id: I9f28c9445daf9ce6206ff9e38e271ac805768fae
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Aatir Manzur (1):
Power supply input faults resolution
(From meta-ibm rev: bc9be1c977fcea7543aab6f2ffd51372bb3e805f)
Change-Id: I46d82875b474abe1af478e8bbfd7d1141d2d5c3d
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
BMCWeb uses ObjectMapper associations to find sensor information for
Redfish. Due to BMCWeb enhancements for the Power and SensorCollection
schemas, the following Witherspoon association changes are required:
* Remove the "chassis" <-> "all_sensors" association for power supplies.
Power supplies were considered chassis by BMCWeb as a short-term
solution, but they have been moved to the Power schema.
* Add the power supply sensors to the "chassis" <-> "all_sensors"
association for the top level chassis.
* Add other missing power sensors to the "chassis" <->
"all_sensors" association for the top level chassis. These
associations were temporarily removed due to limitations in the BMCWeb
support for power sensors. These limitations have been addressed.
See https://github.com/openbmc/docs/blob/master/sensor-architecture.md
for more information on sensor associations used by BMCWeb.
(From meta-ibm rev: a1c35f612f58e5453fe988d59db21a8673fdcfa4)
Change-Id: Ibea5bdea58711e96faff4937ecccedcc695d9ba4
Signed-off-by: Shawn McCarney <shawnmm@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
As on Witherspoon, some VRMs on Swift need their AVS buses enabled
as part of the power on sequence. The AVS bus connects those VRMs
to the processors so the processors can set voltages.
On Witherspoon, the sequence was
1. Disable the AVS bus
2. Manually set VRM voltages
3. Enable AVS bus
Currently on Swift there is no need to manually set voltages, so
the AVS bus disable service and script isn't required.
Tested: Tested on swift, and ensured both witherspoon and
witherspoon-128 still have all avs scripts and
services installed.
(From meta-ibm rev: f1ceece0b75a4522ef3089319b12d22fd83ed9ef)
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Ifd7ebdd5ec3dcdfef97c04e666d83fcb4991b452
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Matt Spinler (1):
Fix association path when resolving input faults
(From meta-ibm rev: aa31db48bd98f4d22b8b0b6a6316aefcd4bc5daa)
Change-Id: I3813ee4174d6aeebc6c7014d4b7d059e65b9ad99
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
The Swift MRW has been updated and this commit utilizes some unused
sensors for Swift starting at 0xFE and counting backwards
(From meta-ibm rev: df212c93689bd73f0e760ed3cfffada6fa6b9ffa)
Change-Id: Ica981d322f51fec94c0db94884938a60b637eb73
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Matt Spinler (2):
Update .gitignore
Don't try to read GPIOs when no device path
(From meta-ibm rev: adf123779de48ee17f2d8c53f4e3d865e575c2f9)
Change-Id: Ia97046f0d856266907831be9fc552d6d750d14f9
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Use an override in bbappends in meta-witherspoon as described and
recommended in the "following best practices when creating layers"
section of the the Yocto development tasks manual.
ibm-ac-server represents common machine configuration shared by all of
IBMs "Accelerated Compute" class of servers. Apply it wherever any
variables are un-bounded by any override.
This enables more flexible use of meta-witherspoon in build
configurations, and easy addition of machines to the layer.
(From meta-ibm rev: bb0e1d0699a4b9905c053c94af7d882cd71779fc)
Change-Id: I82f7338b0d7a64b5e7a67e19bcdff07f48a332d4
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
(From meta-ibm rev: 8f7ff601395419a933eb0506d5cc07fd805f7708)
Change-Id: Iffb2c550511b4024b721c2ba81aec1f909ce7703
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Using a distro feature here might be a case of too much abstraction.
Instead, just enable them because that is what is desired for those
systems. This is slightly easier to comprehend.
Revisit, if at a later time, several phosphor-software-manager users
enable signature verification and file syncing when using UBI (making
the abstraction useful). If/when that occurs, those configure options
and packages should be enabled via the distro feature in the base
recipe and not in a bbappend.
(From meta-ibm rev: 50eebe208babfe35ccd5a3ed8d560669381e82a5)
Change-Id: Ic4ac7f89eeb4575e6dabb68bb61aa55835316864
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
This commit adds the xyz.openbmc_project.Inventory.Item.Accelerator
interface to IPMI GPU functional sensors.
This was something done earlier by commit
f510f7b6b708b22db1f08faf369994f01edd0ddc.
The same is being ported now to the new sensor config YAML.
Tested:
Loaded this change up on a witherspoon. Verified that the
inventory objects created by host-ipmid now implement the
xyz.openbmc_project.Inventory.Item.Accelerator interface.
busctl call xyz.openbmc_project.ObjectMapper /xyz/openbmc_project/object_mapper
xyz.openbmc_project.ObjectMapper GetSubTree sias
"/xyz/openbmc_project/inventory" 0 1
"xyz.openbmc_project.Inventory.Item.Accelerator"
a{sa{sas}} 6
"/xyz/openbmc_project/inventory/system/chassis/motherboard/gv100card0"
....
....
(From meta-ibm rev: 2b99559bff775f719fb79a5a770b5267bbbd6dcc)
Signed-off-by: Santosh Puranik <santosh.puranik@in.ibm.com>
Change-Id: Ic132c417aca171e23f5d72705461fe3378e194b0
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
There are two directory names in the path that are different based
on the I2C bus.
(From meta-ibm rev: d4f13c672063f32ce6aafdaaf63ce34e79f7a4b5)
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I37288264ff5098f75780c243b47f46f312f98854
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Use typical bitbake metadata style and use double instead of single
quotes, and put the append operator prior to the override.
(From meta-ibm rev: 5670481726ee9e986090498e921f446ed61f1b84)
Change-Id: I744a54540b671b534f1eb1cac0a87e1891c782be
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Set the correct (noarch) package arch on a couple of
shell-script-providing packages.
(From meta-ibm rev: d2cb8b6c5c50794cdd97435d01fe9147010f89cd)
Change-Id: I5de4911460c141fef2200efa1f80c3f0b3a6c3dd
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Hard-coded values for fan tach sensor thresholds don't work because
these values vary. For accurate reporting, Redfish sensor output looks
at the functional status on the fan inventory.
Tested:
Same config files changed under /etc and change verified in the webUI
(From meta-ibm rev: 13ed7b8ed73d71206f6992a4c71294280c451446)
Signed-off-by: Aatir Manzur <aatrapps@gmail.com>
Change-Id: I80df620662d16cb677acbfe311bd2e709ae5976f
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Configure fan monitor to monitor the 4 single rotor chassis fans using
the same config parameters as witherspoon. These parameters will likely
change once complete hardware arrives and is thermally characterized.
Tested:
Built swift fan monitor with correctly generated config
Built witherspoon fan monitor resulting in no config change
(From meta-ibm rev: a7f9cd542edc7f09192ebe30ba6c286b1a01f578)
Change-Id: Iee6eccd75ead287db159b52c7f87a0d3a89e8c99
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Configure fan presence for the 4 single rotor chassis fans to use gpio
or tach feedback presence detection. For the internal boost fan,
currently only configure the use of gpio for presence detection. The
requirement of the boost fan is to assist in cooling specific card
locations when necessary and may be updated later to include presence
detection by tach feedback.
Tested:
Built swift fan presence with correctly generated config
Built witherspoon fan presence resulting in no config change
(From meta-ibm rev: 62395b7eb55fd36aa05bc8ed4593aea78c2e2dea)
Change-Id: I10d0bcf9311926cacb1c5310b80a3bc0f00ed782
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
first-boot-set-hostname service will set a unique hostname
to the machine on the very first boot. The idea of this
commit is to enable this service as a part of witherspoon
image.
Tested by:
1. Enable first-boot-set-hostname.service
- systemctl enable first-boot-set-hostname.service
2. Reboot the machine
- reboot
Post reboot, hostname will be changed to hostname-serialno
(From meta-ibm rev: 6c8fb8fd38fd7f627657268d64967474cdd27653)
Signed-off-by: asmithakarun <asmithkr@in.ibm.com>
Change-Id: I77ea7c8ddd8f0e0ce425f77262aea22712761769
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Refactor the config yaml to be machine specific
The only rule is the values in this file not conflict with the FRU_ID
fields in the Swift MRW. Swift MRU has FRU_ID values that go into the
50s so just add 10 to all values in this file.
(From meta-ibm rev: 89af26a2ca92f79493a652ae279a6c48a67d1f7f)
Change-Id: I4a2e3ca95791d0ec2201b027894833a7ef7b4cfb
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
The Swift MRW does a few things different here:
- Renames these from gv100 to ga100
- Starts their FRU_ID at 15
- Only has 4 vs. 6 of them
(From meta-ibm rev: 91a87c8b0288f235452b3073e24a5519020553e8)
Change-Id: I0af55e2d0bf5e317dfae45b4e53810d3b6d8897c
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
With updates from openbmc/openbmc#2911, event actions are now able to be
configured with groups subsets and event timers are now included in the
available event triggers. Actions with group subsets allow a single
event's set of triggers to run actions against a given group subset
instead of the entire event groups. Also, with timers being included as
a trigger, events can be configured with or without a timer instead of a
disabled timer being created for events that previously did not require
a timer.
Tested:
Generated code is functionally equivalent to previous yaml
Verified fan control functionality of wspoon image
(From meta-ibm rev: 1a43941fb100db7c46430f0dbbc82799276e9c13)
Change-Id: Ide4167ef1a202381b702b7f6fe58b7f30501ecb3
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
This allows upstream to drop some backward-incompatible changes while
the yaml in meta-ibm gets updated to the new format coming in from
upstream.
(From meta-ibm rev: 81ca4572471629b5114a52afb50a84d9e2cc92d1)
Change-Id: Ia554f14c624d236e02d7898d2f95e7a90384dadf
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|