Lines Matching +full:ipmi +full:- +full:bt
8 - Briefly recap OEM Extension layout as described in IPMI Specification.
9 - Enumerate Command codes allocated for use with the OpenBMC OEM Number.
10 - For each such code, describe the associated messages, including
16 [IPMI Specification](http://www.intel.com/content/www/us/en/servers/ipmi/ipmi-second-gen-interface-…
17 To keep it both simple and concrete, only BT Tansport is described. Please
22 Per section 11.1 of IPMI Spec
25 | :-----: | ---: | :------- | :---: | :---------------------------------------- |
26 | 0 | | Length\* | - | Number of bytes to follow in this request |
28 | 1 | 0:1 | LUN | - | Allow any LUN |
29 | 2 | | Seq\* | - | Per section 11.3 of IPMI Spec |
30 | 3 | | Cmd | - | Table 3 - OpenBMC Cmd Codes |
32 | 2 ~ n+6 | | Data | - | n data bytes, encoding depends on Cmd |
36 - Length and Seq are specific to BT transport - other transports may not have
39 - Serialize numbers larger than 1 byte LSB first - e.g., represent OEM
44 Per section 11.2 of IPMI Spec
47 | :-----: | ---: | :------- | :---: | :---------------------------------------------- |
48 | 0 | | Length\* | - | Number of bytes to follow in this response |
50 | 1 | 0:1 | LUN | - | LUN of request to which this is a response |
51 | 2 | | Seq\* | - | Seq of request to which this is a response |
52 | 3 | | Cmd | - | Cmd code of request to which this is a response |
53 | 4 | | CC | - | Completion code, Section 5.2 of IPMI Spec v2.0 |
55 | 8 ~ n+7 | | Data | - | n data bytes, encoding depends on Cmd |
69 | :-----: | :----------- | :------------------ |
70 | 0 | - | Reserved |
75 | 5 ~ 255 | - | Unallocated |
82 ### I2C Request Message - Overall
85 | :-----: | :--- | :------------ | :------------------------ |
88 | | 7 | I2cFlagUsePec | 1 => use PEC - see note. |
90 | 2 ~ n-1 | | | Step sequence - see next. |
94 - Total length of step sequence must exactly fill request.
96 - Intent is to handle
97 [Linux Kernel SMBus Protocol](https://www.kernel.org/doc/Documentation/i2c/smbus-protocol),
98 with com generalized to m byte sequence - e.g., at24c64 uses 2 address bytes,
102 - Goal is to support SMBus v2 32-byte data block length limit; but easily
106 - PEC refers to SMBus Packet Error Check.
108 - SMBus address resolution, alerts, and non-standard protocols not supported. So
111 - Depending on options, i2cdetect uses either quick write or 1 byte read;
112 default is 1-byte read for eeprom/spd memory ranges, else quick write.
114 ### I2C Request Message - Step Properties
117 | :---: | :--: | :------------- | :-------------------------------------------- |
119 | | 7:1 | dev | 7-bit I2C device address. |
131 | :-----: | :-----: | :-: | :--- | :-------------------------------------- |
134 | 0 | 1 | - | 3 | Reserved. |
137 | 1 | 1 | - | 3 | Read count from device. |
141 - All other combinations are reserved.
143 - RecvLen corresponds to Linux
144 …[I2C_M_RECV_LEN message flags bit](http://elixir.free-electrons.com/linux/v4.10.17/source/include/…
146 - Transfers include byte count in SMBUS block modes, and PEC byte when selected.
149 - In case of write steps, wrPayload may include:
150 - register address byte or bytes;
151 - count byte if implementing SMBUS block or call operation;
152 - up to 32 bytes of logical payload; and
153 - PEC byte.
158 | :---: | :--------- | :----: | :----------------- |
159 | 0:n-1 | rd_data | 0 ~ 34 | byte sequence read |
163 - Maximum logical payload is 32.
165 - In the unlikely event a transfer specifies multiple read steps, all bytes read
168 - However, maximum reply limit is sized for the largest single read.
170 - RecvLen case w/ PEC can return up to 34 bytes: count + payload + PEC