From: Patrick Venture <venture@google.com>
To: Patrick Williams <patrick@stwcx.xyz>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>,
Titus Rwantare <titusr@google.com>
Subject: Aspeed BMCs using KCS?
Date: Tue, 3 Aug 2021 13:15:20 -0700 [thread overview]
Message-ID: <CAO=notyh_UQ8WJktb7ffhkZyeP+btqHJ_JSR28coXqrq3XZAsg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 313 bytes --]
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?
Thanks,
Patrick
[-- Attachment #2: Type: text/html, Size: 410 bytes --]
next reply other threads:[~2021-08-03 20:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 20:15 Patrick Venture [this message]
2021-08-03 21:37 ` Aspeed BMCs using KCS? Patrick Williams
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:
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=notyh_UQ8WJktb7ffhkZyeP+btqHJ_JSR28coXqrq3XZAsg@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).