#
043af59f |
| 23-Nov-2023 |
Tom Tung <shes050117@gmail.com> |
Get eraseMaxGeometry and eraseMinGeometry from dbus
Also, make findDevice return output parameters based on RVO.
With the change like in EntityManager JSON: ``` { "Name": "example_emmc", "T
Get eraseMaxGeometry and eraseMinGeometry from dbus
Also, make findDevice return output parameters based on RVO.
With the change like in EntityManager JSON: ``` { "Name": "example_emmc", "Type": "EmmcDevice", "LocationCode": "location" "EraseMaxGeometry": 10000000000, "EraseMinGeometry": 5000000000, } ``` and geometry values will be set to estoraged.
Tested: - unit test pass: ``` 5/7 util_test OK 0.05s ```
Change-Id: Ia8499af2168c7e740558978273fc80456eb29282 Signed-off-by: Tom Tung <shes050117@gmail.com>
show more ...
|
#
d3bfa7bb |
| 13-Jan-2022 |
John Edward Broadbent <jebr@google.com> |
Add namespaces to erase methods
Some erase objects did not have the required namespace. This change adds the estoraged and estoraged_testing namespace where it is needed.
Testing: Not tested Change
Add namespaces to erase methods
Some erase objects did not have the required namespace. This change adds the estoraged and estoraged_testing namespace where it is needed.
Testing: Not tested Change-Id: I63757ea4d3672659f21108e5e65fd09aa1c03406 Signed-off-by: John Edward Broadbent <jebr@google.com>
show more ...
|
#
972c3faa |
| 29-Dec-2021 |
John Wedig <johnwedig@google.com> |
Switch to new D-Bus interface
Now that the eStoraged interface is in phosphor-dbus-interfaces, we can remove the yaml files from this repo and switch to the new interface in phosphor-dbus-interfaces
Switch to new D-Bus interface
Now that the eStoraged interface is in phosphor-dbus-interfaces, we can remove the yaml files from this repo and switch to the new interface in phosphor-dbus-interfaces. Note that the new interface is slightly different. Some functions have different arguments, and the eStoraged-specific errors were removed.
Also, the new interface allows for the caller to specify the filesystem type, but for now, only ext4 is supported.
Tested: $ /usr/bin/eStoraged -b /dev/mmcblk0 & $ busctl call xyz.openbmc_project.eStoraged.mmcblk0 \ /xyz/openbmc_project/storage/mmcblk0 \ xyz.openbmc_project.Inventory.Item.Volume FormatLuks ays 3 1 2 3 \ xyz.openbmc_project.Inventory.Item.Volume.FilesystemType.ext4 $ busctl call xyz.openbmc_project.eStoraged.mmcblk0 \ /xyz/openbmc_project/storage/mmcblk0 \ xyz.openbmc_project.Inventory.Item.Volume Lock $ busctl call xyz.openbmc_project.eStoraged.mmcblk0 \ /xyz/openbmc_project/storage/mmcblk0 \ xyz.openbmc_project.Inventory.Item.Volume Unlock ay 3 1 2 3 $ busctl call xyz.openbmc_project.eStoraged.mmcblk0 \ /xyz/openbmc_project/storage/mmcblk0 \ xyz.openbmc_project.Inventory.Item.Volume Erase s \ xyz.openbmc_project.Inventory.Item.Volume.EraseMethod.VerifyGeometry
Signed-off-by: John Wedig <johnwedig@google.com> Change-Id: I5477b313ac5342409e2cf53ca70259c17da6269c
show more ...
|
#
e6ffe704 |
| 14-Oct-2021 |
John Edward Broadbent <jebr@google.com> |
Add Erase verifyGeometry
This confirms specified amount of the drive is accessible. The min and max expected drive size are set as a build configuration, and compared against the drive size (found b
Add Erase verifyGeometry
This confirms specified amount of the drive is accessible. The min and max expected drive size are set as a build configuration, and compared against the drive size (found by using the linux ioctl). Also adds testing build files, testing options, and verifyGeometry test.
Tested: Ran eStoraged on a machine with an eMMC, using the following $ ./eStoraged -b /dev/mmcblk0 & $ busctl call xyz.openbmc_project.eStoraged.mmcblk0 \ /xyz/openbmc_project/storage/mmcblk0 \ xyz.openbmc_project.eStoraged Erase ays 1 1 \ xyz.openbmc_project.eStoraged.EraseMethod.VerifyGeometry
Signed-off-by: John Edward Broadbent <jebr@google.com> Change-Id: Ie47f8666996a6085a115d1b86f2643bc278638c5
show more ...
|