From: Jeremy Kerr <jk@ozlabs.org>
To: "Cédric Le Goater" <clg@fr.ibm.com>, openbmc@lists.ozlabs.org
Subject: Re: [PATCH openbmc 0/3] Re-enable obmc-console and add a ssh endpoint
Date: Fri, 15 Apr 2016 16:29:51 +0800 [thread overview]
Message-ID: <5710A67F.3030602@ozlabs.org> (raw)
In-Reply-To: <570FA5F1.1020201@fr.ibm.com>
Hi Cédric,
> I tried it on a palmetto. Very nice. This is perfect for me.
Excellent, thanks for testing!
> For my education on the topic, what are the plans for the OpenBMC
> host console ? Is obmc-console a temporary or a final solution ?
obmc-console will be the final solution; however, it doesn't mean we
need to always use ssh-based access to the console.
It allows multiple "handlers" for the UART data. At present, we have
two handlers: one that copies to/from stdio (which we then pipe over
ssh), and one that logs the host UART data to a file.
For a websocket, we'd just need a new handler to implement that.
We also have a TODO for a handler to implement redirection back to a
local UART:
https://github.com/openbmc/obmc-console/issues/3
Cheers,
Jeremy
prev parent reply other threads:[~2016-04-15 8:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 6:30 [PATCH openbmc 0/3] Re-enable obmc-console and add a ssh endpoint OpenBMC Patches
2016-04-14 6:30 ` [PATCH openbmc 1/3] Enable obmc-console project OpenBMC Patches
2016-04-14 6:30 ` [PATCH openbmc 2/3] dropbear: Add patch for -c <command> option to dropbear OpenBMC Patches
2016-04-14 6:30 ` [PATCH openbmc 3/3] obmc-console: Add ssh endpoint OpenBMC Patches
2016-04-14 14:15 ` [PATCH openbmc 0/3] Re-enable obmc-console and add a " Cédric Le Goater
2016-04-15 8:29 ` Jeremy Kerr [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=5710A67F.3030602@ozlabs.org \
--to=jk@ozlabs.org \
--cc=clg@fr.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.