archive mirror
 help / color / mirror / Atom feed
From: Patrick Williams <>
To: Patrick Venture <>
Cc: Titus Rwantare <>,
	OpenBMC Maillist <>
Subject: Re: Aspeed BMCs using KCS?
Date: Tue, 3 Aug 2021 16:37:14 -0500	[thread overview]
Message-ID: <YQm3Cgf5XrpkIwWF@heinlein> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 701 bytes --]

On Tue, Aug 03, 2021 at 01:15:20PM -0700, Patrick Venture wrote:
> Patrick et al;
> As you may know, my team is working on enabling lots of stuff with Qemu and
> we dont' have any platforms using KCS with aspeed.  However, we wanted to
> enable this testing because we have other KCS configurations.  I wanted to
> ask if you have an openbmc image that uses aspeed kcs?

I thought most x86 machines use KCS, but certainly Tiogapass does.

meta-facebook/conf/machine/include/ ?= "phosphor-ipmi-kcs"

A default build of Tiogapass should get you something that attempts to use the
KCS interface.

Patrick Williams

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-08-03 21:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-03 20:15 Aspeed BMCs using KCS? Patrick Venture
2021-08-03 21:37 ` Patrick Williams [this message]
2021-08-03 22:44   ` Patrick Venture

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YQm3Cgf5XrpkIwWF@heinlein \ \ \ \ \

* 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).