All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Hanson <peterh@google.com>
To: "Anton D. Kachalov" <mouse@yandex-team.ru>
Cc: Chris Austen <austenc@us.ibm.com>,
	tomjose <tomjose@linux.vnet.ibm.com>,
	 OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Plans for BMC i2c to host bridge via IPMI
Date: Wed, 19 Apr 2017 12:32:42 -0700	[thread overview]
Message-ID: <CAPozSNp1gR1tKyz9qgX+F-wV4xftb5_WAa5tibDP8+xixf8J1w@mail.gmail.com> (raw)
In-Reply-To: <11221492599488@webcorp01f.yandex-team.ru>

Anton,

Thank you for the interesting contributions. As noted earlier, the
Master send-receive message is inadequate to describe the private bus
array in a modern Bmc. And has other senseless limitations. But using
another message seems like a small difference. So I have been studying
your design for its key ideas.

I have some basic high-level questions and/or guesses.

A higher level entity sends messages to one `adapter', which then
sends them to i2c. More-or-less separately, a slave adapter receives
replies and converts them back to messages to that entity.

I now think ipmid can act as that entity. If so, it would be useful to
understand completely how that works.

I see what looks like usable slave I2C adapter code. Is it for
multimaster I2C bus? Or do infernal messaging flows also use it?

Thanks again,
 -- peterh

      reply	other threads:[~2017-04-19 19:32 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
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 [this message]

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=CAPozSNp1gR1tKyz9qgX+F-wV4xftb5_WAa5tibDP8+xixf8J1w@mail.gmail.com \
    --to=peterh@google.com \
    --cc=austenc@us.ibm.com \
    --cc=mouse@yandex-team.ru \
    --cc=openbmc@lists.ozlabs.org \
    --cc=tomjose@linux.vnet.ibm.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.