From: Rick Altherr <raltherr@google.com>
To: David Thompson <dthompson@mellanox.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: MCTP protocol support in OpenBMC?
Date: Thu, 30 Mar 2017 16:04:17 -0700 [thread overview]
Message-ID: <CAPLgG==+vcFHfjT1ZMrokYgnVdP13n-iNA30iqdocNRSF-C1Pw@mail.gmail.com> (raw)
In-Reply-To: <HE1PR0501MB2666721F6FF033CA4B94D754DD340@HE1PR0501MB2666.eurprd05.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 950 bytes --]
I know the Aspeed parts have hardware to support MCTP. Neither mainline
Linux or OpenBMC have drivers for that hardware yet. I'm interested in what
can be done with MCTP but I'm not aware of any plans from IBM or Google to
implement support. That said, if you'd like to work on a device driver,
I'll gladly review patches and assist with upstreaming.
Rick
On Mar 30, 2017 3:09 PM, "David Thompson" <dthompson@mellanox.com> wrote:
> Hello folks,
>
>
>
> Does OpenBMC currently have any support for MCTP protocol layer,
>
> or is there a plan to deliver something like this in the future? I’d be
>
> very interested to hear about any future plans related to MCTP stack.
>
>
>
> Thanks in advance,
>
> Dave
>
>
>
> David Thompson
>
> Sr. Staff Engineer, System SW
>
> Mellanox Technologies
>
> 1900 West Park Drive, Suite 290
>
> Westborough MA USA 01581
>
> Direct: 508-983-6439 <(508)%20983-6439>
>
>
>
[-- Attachment #2: Type: text/html, Size: 2026 bytes --]
next prev parent reply other threads:[~2017-03-30 23:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 22:09 MCTP protocol support in OpenBMC? David Thompson
2017-03-30 23:04 ` Rick Altherr [this message]
2018-11-14 13:59 ` Jeremy Kerr
2018-11-14 16:13 ` Supreeth Venkatesh
2018-11-14 19:02 ` Emily Shaffer
2018-11-15 15:47 ` Supreeth Venkatesh
2018-11-15 16:24 ` Rapkiewicz, Pawel
2018-11-15 16:26 ` David Thompson
2018-11-15 16:59 ` Supreeth Venkatesh
2018-11-15 1:44 ` Jeremy Kerr
2018-11-15 3:34 ` Khetan, Sharad
2018-11-15 13:34 ` Andrew Geissler
2018-11-15 15:57 ` Supreeth Venkatesh
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='CAPLgG==+vcFHfjT1ZMrokYgnVdP13n-iNA30iqdocNRSF-C1Pw@mail.gmail.com' \
--to=raltherr@google.com \
--cc=dthompson@mellanox.com \
--cc=openbmc@lists.ozlabs.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).