| commit | 3c7037a728b7e6f6c808b5694bf8ebf14df255a7 | [log] [tgz] |
|---|---|---|
| author | Patrick Venture <venture@google.com> | Wed Nov 21 21:40:50 2018 -0800 |
| committer | Patrick Venture <venture@google.com> | Mon Dec 17 15:02:30 2018 -0800 |
| tree | 2cd20aa5623556d0bd6d750ced88b84446485fbd | |
| parent | 33deb17e43ace44d950c1df97aa0c2dafb54e617 [diff] |
build: cleanup configure script PKG_CHECK_MODULES Cleanup the configure script package include lines. There isn't a set style for this yet, but this is an attempt to improve readability whereas it's often one long line per library. The CI will fail if there aren't backslashes on lines for the AC_CHECK_HEADER. Change-Id: I6933ae13699f749a57825eb2f011e80625c5a15c Signed-off-by: Patrick Venture <venture@google.com>
There are and will be a variety of sys specific commands.
The cablecheck command checks whether the BMC is seeing traffic between itself and the host's NIC. Sys specifies which if_name is expected to be connected. The BMC presently only checks traffic on the interface specified. There are now ethernet statistics available over IPMI, which can be checked directly in lieu of this.
Request
| Byte(s) | Value | Data |
|---|---|---|
| 0x00 | 0x00 | Subcommand |
| 0x01 | If_name length | Where you expect the cable, eth0 or eth1, etc |
| 0x02 ... | The name | The string, not null-terminated |
Response
| Byte(s) | Value | Data |
|---|---|---|
| 0x00 | 0x00 | Subcommand |
| 0x01 | 0x00/0x01 | 0 for false, 1 for true |
Any CPLD on the system that can only be read directly via the BMC can have its version exported to Sys via the cpld version command.
Request
| Byte(s) | Value | Data |
|---|---|---|
| 0x00 | 0x01 | Subcommand |
| 0x01 | CPLD ID | A one-byte identifier for the CPLD file to read, unsigned byte. |
Response
| Byte(s) | Value | Data |
|---|---|---|
| 0x00 | 0x01 | Subcommand |
| 0x01 | Major | Major version |
| 0x02 | Minor | Minor Version |
| 0x03 | Sub 1 | Third version number |
| 0x04 | Sub 2 | Fourth version number |
Per the above, if the version number doesn't fit in a byte it'll be cast to size.
The BMC itself must have hard-coded into the image, which ethernet device is connected to the host NIC. This is true also in the mapping of ethernet device to channel number. The channel number is used to configure the ethernet device over IPMI, instead of the interface name. This is because we leverage the current IPMI command set to read and write the networking configuration. Sys can be programmed already to have this information in the board protobuf, however, this information -- can be read from the BMC over IPMI.
Request
| Byte(s) | Value | Data |
|---|---|---|
| 0x00 | 0x02 | Subcommand |
Response
| Byte(s) | Value | Data |
|---|---|---|
| 0x00 | 0x02 | Subcommand |
| 0x01 | Channel number | The IPMI channel number for use with the network configuration commands (such as reading the MAC or IP address of the BMC). |
| 0x02 | if_name length | The length of the if_name in bytes. |
| 0x03... | if_name | The interface name, not null-terminated |
Sys needs to be able to tell the BMC to reset the host but given a delay in seconds.
Request
| Byte(s) | Value | Data |
|---|---|---|
| 0x00 | 0x03 | Subcommand |
| 0x01..0x04 | Seconds to delay (uint32) |
Response
| Byte(s) | Value | Data |
|---|---|---|
| 0x00 | 0x03 | Subcommand |
Sys can get the total number of PCIe slots from BMC using this command. When BMC receives this command, BMC can enumerate over all the PCIe slots and create a hashmap with all the available PCIe slot name - I2C bus number mappings. BMC can then send the total number of PCIe slots as part of this command response.
Request
| Byte(s) | Value | Data |
|---|---|---|
| 0x00 | 0x04 | Subcommand |
Response
| Byte(s) | Value | Data |
|---|---|---|
| 0x00 | 0x04 | Subcommand |
| 0x01 | Total number of PCIe slots | Total number of PCIe slots |
If Sys gets N total slots as part of the above command, then Sys can send this command N times with Entry IDs ranging from 0 to N - 1. Say, Sys sends this command with Entry ID as 1, BMC can go and fetch the first PCIe slot name - I2C bus number mapping from the hashmap created above and then send the PCIe slot name and I2C bus number as part of the command response.
Request
| Byte(s) | Value | Data |
|---|---|---|
| 0x00 | 0x05 | Subcommand |
| 0x01 | Entry ID | Entry ID ranging from 0 to N - 1 |
Response
| Byte(s) | Value | Data |
|---|---|---|
| 0x00 | 0x05 | Subcommand |
| 0x01 | I2C bus number | The I2C bus number which is input to the above PCIe slot |
| 0x02 | PCIe slot name length | The PCIe slot name length |
| 0x03... | PCIe slot name | The PCIe slot name without null terminator |