| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
Start fsi-disable.service to unbind the FSI Driver.
Start fsi-enable.service to bind it again and rescan.
Also added a fsi-bind@.service so we can ensure the
driver is bound each power on.
Change-Id: I5fa62b44994aea3bb645e755187f29e720bf3bce
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is the first commit in a series that will ensure
we do not run the chassis power on services when the
chassis is already on.
Specifically this is to handle the situation where the
chassis is on and the BMC is rebooted.
Change-Id: I733ca076f044731a4ba327fe2f46302dce5f4edd
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
|
|
|
|
|
|
|
|
| |
The FSI scan must be done before start_host and vcs_workaround
run in order for them to work propertly.
Change-Id: I1305a65763ba35721d5655f1f3e6c2d8af5fdc71
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
|
|
After PGOOD comes up, the FSI driver needs to do a
scan to find the FSI devices.
Change-Id: I1b4eeec191408a36b37d9044279bdf067deb2b15
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
|