All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yong Li" <yong.b.li@linux.intel.com>
To: "'Andrew Jeffery'" <andrew@aj.id.au>,
	"'AKASH G J'" <akashgj91@gmail.com>, <openbmc@lists.ozlabs.org>
Subject: RE: Enable KCS interface in zaius
Date: Fri, 30 Aug 2019 14:29:00 +0800	[thread overview]
Message-ID: <000001d55efc$36c53100$a44f9300$@linux.intel.com> (raw)
In-Reply-To: <57995e3f-ef82-49b3-909a-054b5b9bef8e@www.fastmail.com>

It seems that the kernel needs to enable KCS, and disable BT. 
CONFIG_ASPEED_KCS_IPMI_BMC=y

Suggest to check on this: https://github.com/Intel-BMC/openbmc

Thanks,
Yong
-----Original Message-----
From: openbmc <openbmc-bounces+yong.b.li=linux.intel.com@lists.ozlabs.org>
On Behalf Of Andrew Jeffery
Sent: Friday, August 30, 2019 12:42 PM
To: AKASH G J <akashgj91@gmail.com>; openbmc@lists.ozlabs.org
Subject: Re: Enable KCS interface in zaius



On Thu, 29 Aug 2019, at 09:05, AKASH G J wrote:
> Hi all,
> 
> I am using server platform with Intel processor and Aspeed AST-2500 
> BMC. OpenBMC firmware with zaius configuration is used for BMC.
> 

Zaius is an OpenPOWER platform (and our OpenPOWER platforms use the BT
interface rather than KCS). You're using an Intel-based processor for the
host, so perhaps it's better to start with an x86-based platform such as the
s2600wf. This should already have KCS IPMI enabled for you.

Andrew

  reply	other threads:[~2019-08-30  6:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-28 23:35 Enable KCS interface in zaius AKASH G J
2019-08-30  3:59 ` AKASH G J
2019-08-30  4:42 ` Andrew Jeffery
2019-08-30  6:29   ` Yong Li [this message]
2019-09-07 11:34     ` Zheng Bao
2019-09-09  8:53       ` Yong Li
2019-09-09 14:10         ` Zheng Bao
2019-09-10  1:24       ` Yong Li
2019-09-10  1:26       ` Yong Li
2019-09-12  9:08         ` Zheng Bao
2019-09-16  3:07           ` Yong Li

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='000001d55efc$36c53100$a44f9300$@linux.intel.com' \
    --to=yong.b.li@linux.intel.com \
    --cc=akashgj91@gmail.com \
    --cc=andrew@aj.id.au \
    --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 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.