From: Patrick Venture <venture@google.com>
To: Patrick Williams <patrick@stwcx.xyz>
Cc: Titus Rwantare <titusr@google.com>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Aspeed BMCs using KCS?
Date: Tue, 3 Aug 2021 15:44:34 -0700 [thread overview]
Message-ID: <CAO=notx3M3VXv_U062_2zK+jvnKO4KRsJWMK70cwkqTDRof89g@mail.gmail.com> (raw)
In-Reply-To: <YQm3Cgf5XrpkIwWF@heinlein>
[-- Attachment #1: Type: text/plain, Size: 911 bytes --]
On Tue, Aug 3, 2021 at 2:37 PM Patrick Williams <patrick@stwcx.xyz> wrote:
> 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.
>
>
Yeah - I feel like with most Aspeed set-ups people use BT. At least all
the ones I've touched.
> meta-facebook/conf/machine/include/facebook-withhost.inc:PREFERRED_PROVIDER_virtual/obmc-host-ipmi-hw
> ?= "phosphor-ipmi-kcs"
>
> A default build of Tiogapass should get you something that attempts to use
> the
> KCS interface.
>
Thanks!
>
> --
> Patrick Williams
>
[-- Attachment #2: Type: text/html, Size: 1636 bytes --]
prev parent reply other threads:[~2021-08-03 22:45 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
2021-08-03 22:44 ` Patrick Venture [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='CAO=notx3M3VXv_U062_2zK+jvnKO4KRsJWMK70cwkqTDRof89g@mail.gmail.com' \
--to=venture@google.com \
--cc=openbmc@lists.ozlabs.org \
--cc=patrick@stwcx.xyz \
--cc=titusr@google.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 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).