All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yong Li" <yong.b.li@linux.intel.com>
To: "'Milton Miller II'" <miltonm@us.ibm.com>,
	"'Zheng Bao'" <fishbaoz@hotmail.com>
Cc: "'OpenBMC Maillist'" <openbmc@lists.ozlabs.org>
Subject: RE: KCS ipmi interface doesnt work
Date: Wed, 28 Aug 2019 15:58:12 +0800	[thread overview]
Message-ID: <000001d55d76$57d41aa0$077c4fe0$@linux.intel.com> (raw)
In-Reply-To: <OF57E3A1EC.B5D71CB2-ON00258463.005F98C0-00258463.005F98C9@notes.na.collabserv.com>

Intel platforms are using the KCS interface for BIOS/BMC communication.

Notice there is a known issue about the dbus name, need to convert the dash to underscore

Ipmi-kcs3 needs to change to ipmi_kcs3

kcsbridged -c ipmi_kcs3
kcsbridged -c ipmi_kcs4

https://gerrit.openbmc-project.xyz/#/c/openbmc/meta-phosphor/+/23001/

Thanks,
Yong
-----Original Message-----
From: openbmc <openbmc-bounces+yong.b.li=linux.intel.com@lists.ozlabs.org> On Behalf Of Milton Miller II
Sent: Wednesday, August 28, 2019 1:24 AM
To: Zheng Bao <fishbaoz@hotmail.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: KCS ipmi interface doesnt work

On August 27, 2019 around 5AM in some timezone, Zheng Bao wrote:

>      
> Hi, All,
> My server BIOS tries to send ipmi command "self test", but openbmc( I 
>tried Zaius)  doesn't response.
> 
>  
> Is this right? Or how can I debug this? Thanks. 
> 

Zaius is an OpenPower machine.  OpenPower is using the bt (block
transfer) device on the lpc bus to comunicate with the host for IPMI and does not use the KCS protocol or the keyboard device.

Someone else can suggest a better platform to copy the IPMI configuration to use KCS.

milton

      reply	other threads:[~2019-08-28  7:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-27  9:59 KCS ipmi interface doesnt work Zheng Bao
2019-08-27 17:24 ` Milton Miller II
2019-08-28  7:58   ` Yong Li [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='000001d55d76$57d41aa0$077c4fe0$@linux.intel.com' \
    --to=yong.b.li@linux.intel.com \
    --cc=fishbaoz@hotmail.com \
    --cc=miltonm@us.ibm.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 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.