From: "Wang, Kuiying" <kuiying.wang@intel.com>
To: "zhang_cy1989@163.com" <zhang_cy1989@163.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: How to use eSPI between Host and slave BMC in openbmc project
Date: Wed, 27 May 2020 07:03:39 +0000 [thread overview]
Message-ID: <3039e8f807114ae1a0269f9723214014@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]
Hi Felix,
Both KCS and eSPI driver are ready x86 platforms.
Please refer https://github.com/Intel-BMC/
Example:
https://github.com/Intel-BMC/openbmc/blob/intel/meta-openbmc-mods/meta-ast2500/recipes-bsp/u-boot/files/0022-KCS-driver-support-in-uBoot.patch
https://github.com/Intel-BMC/openbmc/blob/intel/meta-openbmc-mods/meta-ast2600/recipes-bsp/u-boot/files/0005-Ast2600-Enable-interrupt-in-u-boot.patch
https://github.com/Intel-BMC/openbmc/blob/intel/meta-openbmc-mods/meta-common/recipes-kernel/linux/linux-aspeed/0022-Add-AST2500-eSPI-driver.patch
BTW: you could set Acute travel logic to analyze eSPI bus. There is eSPI connector on Intel CRB platform.
Thanks,
Kwin.
Dear James/andrew/Oskar
Thanks a lot.
I am studying eSPI spec. But it's hard to find any products with eSPI.
Your reply gives more understanding about eSPI.
Looking forward to more applications with eSPI in openbmc project.
Thanks again.
BR
Felix
| |
zhang_cy1989
|
|
zhang_cy1989 at 163.com<https://lists.ozlabs.org/listinfo/openbmc>
[-- Attachment #2: Type: text/html, Size: 5581 bytes --]
next reply other threads:[~2020-05-27 7:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 7:03 Wang, Kuiying [this message]
2020-06-17 22:42 ` How to use eSPI between Host and slave BMC in openbmc project zhang_cy1989
-- strict thread matches above, loose matches on Subject: below --
2020-05-10 8:27 zhang_cy1989
2020-05-11 0:13 ` Andrew Jeffery
2020-05-11 0:47 ` Jeremy Kerr
2020-05-11 13:31 ` Oskar Senft
2020-05-15 13:43 ` zhang_cy1989
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=3039e8f807114ae1a0269f9723214014@intel.com \
--to=kuiying.wang@intel.com \
--cc=openbmc@lists.ozlabs.org \
--cc=zhang_cy1989@163.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.