All of lore.kernel.org
 help / color / mirror / Atom feed
From: tomjose <tomjose@linux.vnet.ibm.com>
To: Peter Hanson <peterh@google.com>,
	OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Plans for BMC i2c to host bridge via IPMI
Date: Thu, 13 Apr 2017 01:21:10 +0530	[thread overview]
Message-ID: <58EE852E.8010005@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAPozSNp_S_-N8YV=ruAzYVxWy4FgcJvyK27HFb0YL-mNYP22xA@mail.gmail.com>

Hello Peter,

As i understand you would be leveraging the BT(Block Transfer) interface 
to route commands from host to BMC.

 From the IPMI specification it looks like this can be a generic one 
implementation instead of implementing
OEM commands.

Implementing the IPMB interface (Section 7) in the IPMI specification 
would probably suit your requirement.
The following commands should help us achieve the goal: Master 
Write-Read command, Get Message command
and Send message command.

I am thinking that IPMB interface could be a dbus service which parses 
host IPMI commands and maps to an I2C read/write.

Let me know your thoughts.

Regards,
Tom


On Thursday 06 April 2017 07:10 AM, Peter Hanson wrote:
> Ave!
>
> This email captures proposed actions from an exchange earlier today on
> the #openbmc IRC channel.
>
> Basic goal is to reach devices on a BMC I2C bus from IPMI commandline at host.
>
> I2C commands and responses to be carried as OEM extension messages,
> i.e., Network Function Codes 2Eh / 2Fh in the Intel specification.
> Those message forms require a three byte IANA Enterprise Number, and
> our original plan used Google's code.
>
> We would like to carry the feature in OpenBmc, so I wanted to confirm
> if this is acceptable, and/or what modifications would be needed.
>
> Decisions:
>
> 1. Ok to use OEM extensions. Patrick noted that OpenBmc already uses
> some, albeit under the IBM IANA Enterprise Number.
>
> 2. Switch to OpenBmc IANA Enterprise Number when available.
>
> 3. Patrick proposed to create a new phosphor-ipmi-oemproviders repo to
> hold the code, message documentation, etc.
>
> 4. All uses of the OpenBmc IANA shall be enumerated in place - almost
> certainly an include file in the new repo - so we don't end up with
> conflicting uses.
>
> Actions:
>
> A1. peterh: send this email to the mailing list.
> A2. stwcx: request IANA Enterprise Number.
> A3. stwcx: create new phosphor-ipmi-oemproviders repo.
> A4. peterh+brendanhiggins: propose detailed message designs.
> A5. peterh: {net-ipmid,host-ipmi} += support for these commands.
>
> A key point of this email is to reap your collective wisdom, so please
> if you have something to contribute, please do. In particular,
> Patrick, please correct anything I misunderstood or incorrectly
> extrapolated from the chat.
>
>    -- peterh
>

  reply	other threads:[~2017-04-12 19:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-06  1:40 Plans for BMC i2c to host bridge via IPMI Peter Hanson
2017-04-12 19:51 ` tomjose [this message]
2017-04-13  0:54   ` Peter Hanson
2017-04-17  9:31   ` Anton D. Kachalov
2017-04-18 19:17     ` Chris Austen
2017-04-19 10:58       ` Anton D. Kachalov
2017-04-19 19:32         ` Peter Hanson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=58EE852E.8010005@linux.vnet.ibm.com \
    --to=tomjose@linux.vnet.ibm.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=peterh@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.