| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Change to use phosphor-multi-gpio-monitor to handle all GPIO events from
Altra Host.
Tested:
1. Run reboot command from Host OS and check if Host can reboot and then
boot to OS.
2. Run shutdown command from Host OS and check if PowerState change to
Off after complete.
3. Check SCP failover handling.
4. Check PSU Hotswap workaround is applied when hot plugging/unplugging
PSUs
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: I9797b51facf31672a6d2c9bc7ab7add24d8e06b8
|
|
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I65febeeec11e6e5b40ee728f42cfbe77023dae1e
|
|
Enable phosphor-ipmi-blobs and phosphor-ipmi-blobs-binarystore so that
SMBIOS MDR data can be sent from Host.
Tested:
1. Run BmcBlobGetCount command
$ ipmitool raw 46 128 0xcf 0xc2 0x0 0
cf c2 00 a4 78 01 00 00 00
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: Ib8fe4f92d6e27d0c620aeb301b1dc63901720c9b
|
|
Replace Ampere implementation for UID button by the use of
phosphor-button.
Tested:
1. By default, the UID LED status is OFF.
- Press UID button and check if the UID LED is ON
- Press UID button again and check if the UID LED is OFF
2. Turn on the UID LED via ipmi command
$ ipmitool chassis identify
3. Turn Lit/Blinking/Off UID LED via Redfish:
$ curl -X PATCH --user root:0penBmc -H "Content-Type: application/json"
-H "If-Match: *" --insecure https://<bmc_ip>/redfish/v1/Systems/system
-d '{"IndicatorLED": "Lit|Blinking|Off"}'
--> check if the UID LED is ON, blinking or OFF, respectively
Signed-off-by: HuyLe <hule@amperecomputing.com>
Change-Id: I912e26be827167a201dad5d81be6728101405521
|
|
We also need to move the conf-notes.txt files.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ic44e015c0216b526de4fec277ad42f162bca1f33
|
|
The latest poky commit is requiring us to have all of
our template configs in a subdirectory instead of directly in
the `conf` directory. Without this we end up with errors during
setup like:
```
Error: TEMPLATECONF value (which is .../openbmc/meta-facebook/meta-bletchley/conf) must point to meta-some-layer/conf/templates/template-name
```
Fix this by moving all of our template files into the 'default'
template subdirectory (following the pattern of poky) and modifying
`setup` as necessary to follow.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Iecefde73d55acbb6bc63ae3d68c4311adaf327ae
|
|
Currently, the uboot can not jump to Linux kernel due to the watchdog
timeout. This commit enables dcache in uboot to speed up jumping from
uboot to kernel, it made the kernel is booted successfully.
Tested:
1. Linux kernel is booted successfully.
2. User can flash new BMC software in u-boot.
Signed-off-by: Thang Tran <thuutran@amperecomputing.com>
Change-Id: I17bce6bdea5168e5c261b44df6ccb16e0ef8a3c1
|
|
The build option of Intel cpu sensor service in dbus-sensors
repository is changed from "cpusensor" to "intelcpusensor". Update the
build option in openbmc source to match with that change.
dbus-sensors: srcrev bump 0fe0229497..255da6b419
Thu Nguyen (1):
cpusensor: Change cpusensor to intelcpusensor
Tested:
1. No build errors.
Signed-off-by: Thu Nguyen <thu@os.amperecomputing.com>
Change-Id: Ib31f7ce3dd7d5ed1bb226eb991459ec0bf233973
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
|
|
Set PSON to default value in AC power will prevent the Host ON
accidentally. This commit also configures some important GPIOs to
default value when A/C.
Tested:
1. Do A/C power and check if power and host state from "obmcutil status"
not Running.
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: Iba99a2dbef3b48a5d110e92c9167a69a603a8e54
|
|
"BMC_I2C_BACKUP_SEL" was not defined anywhere, so script
"ampere_scp_failover.sh" fails to execute and SCP can't
switch to the secondary EEPROM to boot in case of failed
primary EEPROM firmware.
This commit defines BMC_I2C_BACKUP_SEL to 8 in "gpio-defs.sh"
, which is gpio B0
Tested:
1. BMC on, Host on, flash good SCP firmware to secondary EEPROM,
flash bad SCP firmware to primary EEPROM that simulate SCP
authentication failure
=> Host boots OK with secondary EEPROM
Check gpio BMC_I2C_BACKUP_SEL
=> it will be set to 0
Signed-off-by: chaul.ampere <chaul@amperecomputing.com>
Change-Id: Ibb891042deb051f8100f9a88dd3619bce12c181f
|
|
All Ampere developed platforms have BMC MAC Address specified in the FRU
EEPROM at Board Extra.
This commit moves the script to get MAC Address from FRU EEPROM to
common folder so that later platforms can use it. It also adds checking
for valid MAC Address before using.
Tested:
1. Update BMC MAC Address using IPMI OEM Write BMC MAC Address command.
Reboot BMC and ensure the new MAC is used.
2. Write the FRU with invalid value at Board Extra. Reboot BMC and check
for BMC still uses old MAC Address
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: I29a44a9b4965bea1b6d8d7d55536d25bb0dd924c
|
|
When executing Host UEFI firmware update, the ampere_flash_bios.sh check
for pnor partition available. If not, it binds the driver so that can
access the device to flash.
There is a case that the driver is already bound but no pnor device
available. This makes the Host firmware flash fail.
This commit adds codes to check for this case and unbind the driver so
that the next binding success.
Tested:
1. Flash UEFI firmware successful in above case
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: I410621cf916d9ae139f420469357e4687ae138ab
|
|
When running "ipmitool fru print" command, the output shows
dimm0/1, cpu0/1 without data. This is from the host-ipmid which uses
default configuration file to handle "Get SDR"/"Get Device SDR" command,
including DIMM0/1, CPU0/1.
This commit configures to use mtjade-ipmi-fru.yaml file so that correct
FRU information is displayed, preventing the DIMM0/1, CPU0/1 to be
reported.
Tested:
- Check fru information.
$ ipmitool fru print
--> Console does not display DIMM0/1, CPU0/1 data. FRU data is displayed.
Signed-off-by: Thang Tran <thuutran@amperecomputing.com>a
Change-Id: Ibd18bfd5656676ccef70608dd5f78b93ab8432fc
|
|
With new SPI driver, the path to bind SMC SPI-NOR is changed. Update the
path for correctness.
Tested:
1. Flash BIOS firmware via Redfish succesfully
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: Ia9cf47f059ef928ec7049a535c668689f3df5cab
|
|
Harvey.Wu (2):
dbus-sdr: fix SEL record Generator ID to fit SPEC
dbus-sdr: fix the vector size in sdrWriteTable and sdrStatsTable
Jian Zhang (1):
Add data types to Value to extend setDbusProperty
Vernon Mauery (1):
fix header install
Willy Tu (4):
cleanup: Remove all warning errors for the Meson build support
build: Add meson build for phosphor-host-ipmi
build: move all shared_library/module to library with version suffix
build: Remove dynamicsensor library if it is not enabled
Change-Id: I92503c6625d1ec2bf88c0a28afac9b4eeb8fbd75
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
Signed-off-by: Willy Tu <wltu@google.com>
|
|
Enable Power and Reset button support with configuring long press time
for Power button is 5s.
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: I940f4549b9a1c50ebc96dc6a063cea3bad95daa8
|
|
Restructure Ampere recipes to better reuse existing resource for
multiple platforms later.
Tested:
1. Compile without error.
2. Run regression test for related features without error.
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: I5d034d21273b99be651f20dc2eb5549c1092f079
|
|
Update equation for total_power to fix the issue not calculated
correctly when 1 PSU device is not plugged.
This change also updates the NVMe virtual sensors that needs for FAN
control.
Tested:
1. Unplug 1 of PSU and check if total_power has correct value.
2. Check NVMe virtual sensors
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: I7e3021b9e6462da5dba55a28951b5c9ddb128de6
|
|
As mtjade uses the newer u-boot tree based on v2019.04, the
phosphor-isolation distro feature does not do anything.
The backdoors closed by the distro feature are now closed by default, so
no opt-in is required.
Change-Id: I779caf74f138715e0a49febbdb09d4ef78e33e0c
Signed-off-by: Joel Stanley <joel@jms.id.au>
|
|
The only recipes which use content from meta-perl are openpower
machines:
```
meta-openpower/recipes-bsp/pdata/pdata_git.bb: libxml-libxml-perl-native \
meta-yadro/meta-nicole/recipes-phosphor/logging/openpower-esel-parser_git.bb: libxml-libxml-perl-native \
```
Remove meta-perl from the bblayers of every layer except openpower
machines.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I51f1a8fbfbe879295c64d2339fc115dbd8823681
|
|
This was added with cde0f094f for libseccomp, but shortly after that
upstream moved libseccomp from meta-security to core (241c7d2e6). As
such, meta-security is no longer used or required.
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Change-Id: I371e54b11f6336720dfc6edf0ef733d22b7fb4f2
|
|
Per [1][2], Yocto is starting to deprecate ABORT and has replaced
the "ABORT" action in BB_DISKMON_DIRS entries with "HALT".
1. https://wiki.yoctoproject.org/wiki/Inclusive_language
2. https://git.yoctoproject.org/poky/commit/?id=4f77505d94a8f6260933f457e9848d1d2fa98ce5
Tested:
Built obmc-phosphor-image successfully and eliminate the following
warnings:
```
WARNING: The BB_DISKMON_DIRS "ABORT" action has been renamed to
"HALT", update configuration
```
Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: If57d0ded9fac41e23b31b01e2a0e309ac7388148
|
|
The /run/openbmc/host@0-on file is created/removed by
phosphor-state-manager, platform should not touch to this file.
Host-on-host-check service is called by obmc-host-startmin target, it is
not depended on the /run/openbmc/host@0-on file. This file is only used
during BMC booting phase.
Tested:
1. Turn off/on the host 100 times.
2. Check the sel log.
ipmitool sel list
3. BMC does not display any log relate to over threshold.
4. Check the host-on-check service is called before host'state is
running
Signed-off-by: Thang Tran <thuutran@amperecomputing.com>
Change-Id: I1ec90a00a7685007e31b89876ff2a5d57191fc53
|
|
Ampere processor uses ACPI graceful shutdown which is triggered from BMC
via a GPIO pin named SHD_REQ. This feature is common for all Ampere
platforms.
This commit moves the configuration for IPMI power soft to
meta-ampere/meta-common so other platforms can use without changes
Tested:
1. Do A/C power the system and boot the Host to OS.
2. Run ipmitool chassis power soft
3. Check if the Host is graceful shutdown.
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: I8a3425c859c4be077075e6a51f12d50283eacdf7
|
|
When HOST is turned on/off, ampere-gpio-poweroff/on@.service is called.
They should not call op-wait-power-off/on@.service, just wait for them.
Remove redundant "Requires" and "Wants" in service files.
Add timeout to obmc-flash-host-bios@.service to avoid blocking power
control.
Tested:
1. Turn on/off the HOST power.
2. Check journalctl log to ensure that op-wait-power-off/on@.service
are not called by ampere-gpio-poweroff/on@.service.
Signed-off-by: Thang Tran <thuutran@amperecomputing.com>
Change-Id: If9403891b2e57c73c4fd8e0ea1b24314b7b0c3f8
|
|
Switch OCP power source from 3V3 to standby too early causes PCIE AER
error on the OCP adapter.
This commit changes to switch the OCP power source via OCP_MAIN_PWREN in
power control application to avoid the issue.
Tested:
1. Run IPMI chassis power soft command and check if no PCIE AER error
generated.
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: I9dbc621390fb04fa818a04aeaac53b6b729e9e75
|
|
With the removal of u-boot patch that adds resetreason to /proc/cmdline
no information to check if the BMC is booted from A/C power or cold reboot.
This commit removes the dependency of resetreason on the
phosphor-discover-system-state application and updates the A/C power
check in the ampere_platform_init.sh script to use information from
/sys/class/watchdog/watchdog0/bootstatus.
Tested:
1. Check power restore policy feature work well.
2. Check ampere_platform_init.sh works properly in both A/C and D/C
power.
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: I4f2e7a241f9ddebf21b2b8c021b9ce87a1c8b26c
|
|
Upstream has removed the image-prelink bbclass[1], so remove it from any
local.conf.sample that still has it enabled.
1. https://git.openembedded.org/openembedded-core/commit/?id=857baaf9e3d181ca18264e85d90b899fd94acff9
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I70f42f8816f5dea207fcf5c34837d6796b3f6bb6
|
|
* Deprecate N-1 release (hardknott).
* Enable N+1 release (kirkstone).
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I39e027e02dab64b4390b46ffbd9c299c858f403e
|
|
Enable host-gpios option in phosphor-state-manager to support Host state
checking when BMC reboots. Also updateampere_host_check.sh to check Host
State via GPIO interface
Tested:
1. Define host0-ready into device tree.
2. Power On the Host. Reboot BMC, then check if CurrentHostState shows
Running.
3. Power OFF the Host. Reboot BMC, then check if CurrentHostState shows
Off.
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Signed-off-by: Thang Tran <thuutran@amperecomputing.com>
Change-Id: I0331dfa340eb5bba201475ab9cada42e0946c8f8
|
|
As mentioned by I970e06ca6f9d0a9792af122eb25da1bb9a06f058, append and
remove directives with '+=' are no longer valid Yocto syntax and raise a
warning.
See https://git.yoctoproject.org/poky/tree/documentation/migration-guides/migration-3.5.rst#n40
One interesting caveat has to do with the difference between "append"
and "+=".
foo:append = "a"
foo:append = "b"
Results in `foo = "ab"`, but
foo += "a"
foo += "b"
Results in `foo = "a b"`. When `:append +=` is used it has behavior
like the `+=` operator. Therefore, in some cases we need to insert
additional whitespace after the `:append = "` to ensure concatenation
behaves as expected. I've manually reviewed the results to ensure there
is no ill side-effects from an additional space potentially being added.
Fix up the entire tree with the following one-liner (and similar for
`remove`):
git ls-files -- ':!:poky/**' ':!:meta-security/**' \
':!:meta-raspberrypi/**' ':!:meta-openembedded/**' \
| grep "\.bb" | xargs grep -l ":append.*+=" \
| xargs sed -i 's/:append\(.*\)+=\([^"]*\)" */:append\1=\2" /'
or ...
| xargs grep -l ":remove.*+=" \
| xargs sed -i "s/:remove\(.*\)+=/:remove\1=/"
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Iea6235e7c76e252f4d473652957c2925f6b8845a
|
|
Fix ampere-mac-update and ampere-gpio-handling starts failure,
including:
- Update ampere_update_mac.sh to recheck if the first MAC Address
reading fail. Also fix incorrect checking if setting new MAC Address
success or not.
- Fix typo in SCP failover service.
Tested:
1. Check if the ampere_update_mac.service starts succesfully.
2. Check if no error report from iS0_scp_auth_failure
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: I6c03e352d8d51030d04cd303e438835e5b724afe
|
|
u-boot 2016.07 does not work well with 64MB SPI-NOR layout, which has
the following issues:
- Incorrect environment variable configuration which makes fail to boot
to kernel and has fw_setenv/fw_getenv commands not work.
- Even update the patch in meta-phosphor to fix above issue, still has
issue with setting environment variable in Linux which makes factory
reset failure each 2 times.
This commit changes to use u-boot 2019.04 to fix above issue.
Tested:
1. Do factory reset and check if the BMC can boot to kernel.
2. Trigger factory reset via Redfish multiple times (6 times) and verify
if the factory reset action can be executed at all times.
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: Ibb269d96a2e2b509aeccbeeaa130aad57093d139
|
|
This sets u-boot to the package containing the v2016.07-aspeed-openbmc
branch. This ensures there will be no change if the default changes in
the future.
Change-Id: Iea12e1691dbdda34a3f95d6d0862add0b15bcf37
Signed-off-by: Joel Stanley <joel@jms.id.au>
|
|
Instead of having many bitbake recipes for Altra GPIO handling,
combining them into a single recipe so that the code look cleaner.
Tested:
1. Check ID button still works.
2. Check hightemp and overtemp handing still works.
3. Check Fault LED works correctly.
4. Check graceful shutdown and Host reboot still work.
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: Ic6eef75702cf0353ae2d84a3cda0ffb84d10f4cc
|
|
Handle S0/1 OVERTEMP and S0/1 HIGHTEMP GPIO signals from Host CPU that turn off the Host to
prevent hardware damage and log an event.
Tested:
1. Assert OVERTEMP event by running below command from SCP console:
S0-cli> mww 0x10000f0112d0 0x2
Check if the Host is turned OFF and event is logged
2. Assert and deassert HIGHTEMP event on Socket 0 and check if new
events are logged.
3. Repeat steps 1 and 2 on Socket 1
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: I16c9676be379ac5d21849c591fbdadda4a6951ef
|
|
By replacing phosphor-hwmon by dbus-sensor, PSU presence detection via
GPIO does not work anymore and it causes confiction with dbus-sensor's
PSUSensor.
Revert the commit to avoid the confliction
Change-Id: Idfd54325c122921a3c5df062bce1b6909b643999
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
|
|
The chassis instance when implementing sensor monitor using
dbus-sensor/entity-manager is /redfish/v1/Chassis/<name> where <name> is
defined from entity-manager configuration.
This commit removes /redfish/v1/Chassis/chassis which is redundant and
make incorrect link from other schema like ComputerSystem and BMC
Manager.
Tested:
1. Check no /redfish/v1/Chassis/chassis available.
2. Check all sensors are available in /redfish/v1/Chassis/Mt_Jade.
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: I334a94bb65c3caa49d0bcb6ab03a42f7999728d5
|
|
Disable phosphor-hwmon from compilation and clean up sensor inventory
which added before for phosphor-hwmon.
Tested:
1. Check if no phosphor-hwmon compiled and run
2. Check all S0 and S1 ADC sensors are still available in Redfish.
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: Ic6ac13963e755e6ef0d93b3f6486546c61b1abe0
|
|
Enable phosphor-nvme with configuration for nvme_max sensor for FAN
control support later.
Tested:
1. Check NVME Temp:
$ busctl get-property xyz.openbmc_project.nvme.manager \
/xyz/openbmc_project/sensors/temperature/nvme20 \
xyz.openbmc_project.Sensor.Value Value
d 22
2. Check nvme_max has valid value
$ busctl introspect xyz.openbmc_project.VirtualSensor \
/xyz/openbmc_project/sensors/temperature/nvme_max
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: Ied609ba5b5d39877c09ed04faff5063c7882a689
|
|
Replace sensor monitoring in phosphor-hwmon by
dbus-sensor/entity-manager.
Tested:
1. Check IPMI sensor report for Temp and ADC sensors with correct
threshold
$ ipmitool sdr list
$ ipmitool sensor list all
2. Check Redfish Thermal and Power schema for Temperature and ADC
sensors
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: Idbb719ed01a28892bce32adce062c56dd51d3088
|
|
Add support SCP firmware update with checking if the ampere_fru_upgrade
available to execute the update.
This commit also supports 2nd Host SPI-NOR update ability.
Tested:
1. Manually copy ampere_fru_upgrade to the /usr/sbin folder and run SCP
firmware update via Redfish.
2. Flash UEFI firmware update on the secondary Host SPI-NOR.
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: Ic335ee2d21625239c3df1937ed5333708233845b
|
|
Change to use dynamic sensors for FRU support to take advantage of IPMI
fru read/write commands.
Tested:
1. Check FRU reading
$ ipmitool fru print
2. Write fru.bin into FRU EEPROM
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Signed-off-by: Thang Tran <thuutran@amperecomputing.com>
Change-Id: I0d0b52ae7b0fd301a14d0d2894268637d867a5b8
|
|
Configure OCP_AUX_PWREN and/or OCP_MAIN_PWREN GPIOs, even without
changing their values, make the OCP power glitched which consequently
makes the Host OS generates many calltrace message.
When BMC is rebooted, the ampere-gpio-poweron@service service is
triggered that reconfigure these GPIOs.
This comit prevents this case by checking if the Host is currently ON to
skip the reconfiguration.
Tested:
1. Boot the BMC and Host CPU.
2. Reboot BMC. Ensure no call trace for OCP
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: I621e025adf72baf84bffd011ea0e04229f739755
|
|
`BBLAYERS_NON_REMOVABLE` is obsolete and no longer required.
As it said by Yocto documentation it can be used by `Hob`
https://www.yoctoproject.org/docs/1.5.2/ref-manual/ref-manual.html#var-BBLAYERS_NON_REMOVABLE
that already removed since Yocto-2.1
https://www.yoctoproject.org/tools-resources/projects/hob
Change-Id: Ibc2d8268a9d837a81e9cf6b0131dba8d0a030a3f
Signed-off-by: Alexander Filippov <a.filippov@yadro.com>
|
|
Remove Mt.Jade u-boot patches as we have other approach for them:
1. Patch 0001 is to set FANs to maximum speed in u-boot to avoid
hardware damage in case of Host ON with high CPU usage. This can be
resolved by setting FAN to maximum speed when the FAN service stop.
2. Patch 0002 is to enable I2C4 device access. With commit
0b32c1b40@linux, I2C4 enable is set via gpio-hog
3. Patch 0003 will be resolved later by supporting Aspeed watchdog with
boot status.
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: I247f99ebac7c3ca10a2dc77f1909f5c0c519401d
|
|
Change to implement virtual USB Ethernet using phosphor-misc's usb-ctrl.
Tested:
1. Boot BMC to Linux. Login and check if usb0 ethernet interface exists.
2. Power ON the Host. Check if usb0 automatically sets its IP to
192.168.0.10
3. Restart the ampere-usbnet.service service. Check if no error happens.
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: I4de722a691a112db851b6dda0a7821b9f78b4d72
|
|
Fix all issues from the shellcheck checked on bash shells under
meta-ampere.
Tested: Verify the following features:
1. Power control (on,off, cycle, graceful shutdown, hard reset).
2. UART switching.
3. UEFI firmware update.
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: Idabf839b7521ecadb642230cc8bb3472c787002e
|
|
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
|
