From: James Feist <james.feist@linux.intel.com>
To: Vijay Khemka <vijaykhemka@fb.com>, Oskar Senft <osk@google.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Access Intel ME IPMB from BMC
Date: Thu, 23 Apr 2020 14:00:02 -0700 [thread overview]
Message-ID: <aa5912c6-de60-f965-368f-1864a521c4d8@linux.intel.com> (raw)
In-Reply-To: <403834AD-B194-44E8-8904-21610A30D727@fb.com>
On 4/23/2020 11:59 AM, Vijay Khemka wrote:
> As i2c slave mqueue driver is not upstreamed and with already having
> same functionality in ipmb-dev driver which is already in uostream
> kernel, I don’t see any reason to use i2c slave mqueue driver. I highly
> incourage people to use ipmb-dev driver with latest ipmbbridge. If there
> are any issues, please let us know.
One issue we ran into is having MCTP and IPMB on the same bus. IPMB
driver can't handle MCTP traffic, where the mqueue could handle both.
Kernel also doesn't allow multiple slave addresses on one bus. Haven't
found a good solution to this one yet.
>
> Regards
>
> -Vijay
>
next prev parent reply other threads:[~2020-04-23 21:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-19 1:45 Access Intel ME IPMB from BMC Oskar Senft
2020-04-20 2:07 ` CS20 CHMa0
2020-04-20 18:12 ` Vijay Khemka
2020-04-20 18:34 ` Oskar Senft
2020-04-20 19:12 ` Anton Kachalov
2020-04-20 20:34 ` Vijay Khemka
2020-04-23 15:31 ` Oskar Senft
2020-04-23 15:34 ` Oskar Senft
2020-04-23 18:59 ` Vijay Khemka
2020-04-23 20:50 ` Oskar Senft
2020-04-23 21:00 ` James Feist [this message]
2020-04-23 23:10 ` Vijay Khemka
2020-04-24 18:49 ` James Feist
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=aa5912c6-de60-f965-368f-1864a521c4d8@linux.intel.com \
--to=james.feist@linux.intel.com \
--cc=openbmc@lists.ozlabs.org \
--cc=osk@google.com \
--cc=vijaykhemka@fb.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.