On Mon, Aug 14, 2017 at 7:03 PM, Patrick Williams wrote:
> On Mon, Aug 07, 2017 at 08:52:57PM -0700, Brendan Higgins wrote:
>> Currently, OpenBMC handles all IPMI message routing and handling in userland;
>> the existing drivers simply provide a file interface for the hardware
On Wed, Aug 9, 2017 at 7:26 PM, Corey Minyard wrote:
> On 08/09/2017 08:04 PM, Brendan Higgins wrote:
>>>
>>> Perhaps that is some level of abuse, but it's pretty common. I'm not
>>> against it.
>>>
>>> There is standard IPMI firmware NetFN (though no commands defined) that
On Thu, Aug 10, 2017 at 6:58 AM, Corey Minyard wrote:
> On 08/07/2017 10:52 PM, Brendan Higgins wrote:
>>
>> From: Benjamin Fair
>>
>> This patch introduces a framework for writing IPMI drivers which run on
>> a Board Management Controller. It is similar
The IPMI definition of the Block Transfer protocol defines the hardware
registers and behavior in addition to the message format and messaging
semantics. This implements a new protocol that uses IPMI Block Transfer
messages and semantics on top of a standard I2C interface.
Signed-off-by: Brendan
The IPMI definition of the Block Transfer protocol defines the hardware
registers and behavior in addition to the message format and messaging
semantics. This implements a new protocol that uses IPMI Block Transfer
messages and semantics on top of a standard I2C interface. This protocol
has the
Added device tree binding documentation for ipmi-bt-i2c (host) and
ipmi-bmc-bt-i2c (BMC) and documentation for the Block Transfer over I2C
(bt-i2c) protocol.
Signed-off-by: Brendan Higgins
---
Documentation/bt-i2c.txt | 121
The IPMI definition of the Block Transfer protocol defines the hardware
registers and behavior in addition to the message format and messaging
semantics. This implements a new protocol that uses IPMI Block Transfer
messages and semantics on top of a standard I2C interface. This protocol
has the
From: Benjamin Fair
The ipmi_bmc folder contains drivers for a BMC to communicate using
IPMI. The ipmi folder is only for drivers on the host side using the
OpenIPMI framework.
Signed-off-by: Benjamin Fair
Signed-off-by: Brendan Higgins
Added device tree binding documentation for ipmi-bt-i2c (host) and
ipmi-bmc-bt-i2c (BMC) and documentation for the Block Transfer over I2C
(bt-i2c) protocol.
Signed-off-by: Brendan Higgins
---
Changes for v2:
- Fixed a typo
- Reworded a sentence to make it clear
This patchset introduces IPMI Block Transfer over I2C (BT-I2C), which has the
same semantics as IPMI Block Transfer except it done over I2C.
For the OpenBMC people, this is based on an RFC:
https://lists.ozlabs.org/pipermail/openbmc/2016-September/004505.html
The documentation discusses the
On Fri, Aug 4, 2017 at 4:18 PM, Brendan Higgins
wrote:
> This patchset introduces IPMI Block Transfer over I2C (BT-I2C), which has the
> same semantics as IPMI Block Transfer except it done over I2C.
>
> The documentation discusses the reason for this in greater detail,
On Sat, Aug 5, 2017 at 3:23 PM, Corey Minyard wrote:
> On 08/04/2017 08:18 PM, Brendan Higgins wrote:
>>
>> This patchset introduces IPMI Block Transfer over I2C (BT-I2C), which has
>> the
>> same semantics as IPMI Block Transfer except it done over I2C.
>>
>> For the OpenBMC
From: Benjamin Fair
This patch introduces a framework for writing IPMI drivers which run on
a Board Management Controller. It is similar in function to OpenIPMI.
The framework handles registering devices and routing messages.
Signed-off-by: Benjamin Fair
From: Benjamin Fair
Instead of handling interaction with userspace and providing a file
interface, rely on the IPMI BMC framework to do this. This simplifies
the logic and eliminates duplicate code.
Signed-off-by: Benjamin Fair
Signed-off-by:
> Perhaps that is some level of abuse, but it's pretty common. I'm not
> against it.
>
> There is standard IPMI firmware NetFN (though no commands defined) that if
> you use
> the driver automatically goes into "Maintenance mode" and modified the
> timeouts
> and handling to some extent to help
On Wed, Aug 9, 2017 at 3:56 AM, Anton D. Kachalov wrote:
> Hello,
>
> I would like to mention one of the our related work for IPMI and I2C.
>
> We use OpenIPMI stack to connect to the computing nodes through the I2C
> using IPMB (BT is not supported by nodes):
>
>
Sorry for the delayed response.
>>> This piece of code takes a communication interface, called a bus, and
>>> muxes/demuxes
>>> messages on that bus to various users, called devices. The name
>>> "devices"
>>> confused
>>> me for a bit, because I was thinking they were physical devices, what
>>>
On Mon, Aug 14, 2017 at 3:28 PM, Brendan Higgins
wrote:
> On Mon, Aug 14, 2017 at 7:03 PM, Patrick Williams wrote:
>> On Mon, Aug 07, 2017 at 08:52:57PM -0700, Brendan Higgins wrote:
>>> Currently, OpenBMC handles all IPMI message routing and
On Thu, Aug 24, 2017 at 6:01 AM, Corey Minyard wrote:
> On 08/23/2017 01:03 AM, Brendan Higgins wrote:
>
>
>>
>> ...
As far as this being a complete design; I do not consider what I have
presented as being complete. I mentioned some things above that I would
19 matches
Mail list logo