9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@coraid.com>
To: 9fans@cse.psu.edu
Subject: [9fans] coraid ethernet console
Date: Sun, 18 Mar 2007 18:56:46 -0400	[thread overview]
Message-ID: <95f6317dab359359885a16c68c407ef7@coraid.com> (raw)

coraid ethernet console (cec) is a way to do most of what you
can do over a serial console over raw ethernet frames.

coraid appliances use cec instead of a serial console so we can
have console access without tcp, ip or a serial connection.
i've put our plan 9 client in /n/sources/contrib/quanstro/cec.tar.
there's a protocol description and a man page in that tar.

i've also submitted a port of the cec device to the cpu kernel.
/n/sources/patch/cpu-cec.  unfortunately as i'm writing this, 
(i realize that i forgot to write a manual page.  i'll fix that in the
next few days.)

i've used this driver to debug a couple of device drivers.
we don't always have enough ports on the console server to go
around.  generally, cec will give you all the output that would be 
available on the serial console once plan 9 has started.  it
definately beats sitting in the unix room.

limitations (or future work)

1.  consolefs doesn't yet speak cec.  (good soc project.)
2.  the cec client doesn't know how to listen for the Toffer
sent by the kernel driver when it starts listening.
3.  thus, 9load doesn't speak cec.
4.  i didn't submit my boot time modifications that make
cec available on boot.

due to a limitation in netif, only one cec client may
run per interface.

enjoy
- erik


             reply	other threads:[~2007-03-18 22:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-18 22:56 erik quanstrom [this message]
2007-03-19 13:39 ` Russ Cox
2007-03-19 14:29   ` erik quanstrom
2007-03-19 14:34   ` Eric Van Hensbergen

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=95f6317dab359359885a16c68c407ef7@coraid.com \
    --to=quanstro@coraid.com \
    --cc=9fans@cse.psu.edu \
    /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).