summaryrefslogtreecommitdiff
path: root/extra/README
diff options
context:
space:
mode:
authorAnton Staaf <robotboy@chromium.org>2014-09-10 12:33:58 -0700
committerchrome-internal-fetch <chrome-internal-fetch@google.com>2014-09-11 20:00:21 +0000
commitdab91fe9ec6ecddea2e3f6f46d207263b58d7982 (patch)
treeaae6f9162e2498fadf2595cf92f258f9c18ddf2e /extra/README
parent0e59d4f38a97defe45351f2b1e132f76f17160e6 (diff)
downloadchrome-ec-dab91fe9ec6ecddea2e3f6f46d207263b58d7982.tar.gz
extra: Move lightbar simulator into subdirectory
This clears the top level extra directory for additional extras. Signed-off-by: Anton Staaf <robotboy@chromium.org> BRANCH=None BUG=None TEST=cd extra/lightbar; make; lightbar Change-Id: If05a768e4d33cbf21b2ce47a056c960a95728558 Reviewed-on: https://chromium-review.googlesource.com/217537 Tested-by: Anton Staaf <robotboy@chromium.org> Reviewed-by: Bill Richardson <wfrichar@chromium.org> Commit-Queue: Anton Staaf <robotboy@chromium.org>
Diffstat (limited to 'extra/README')
-rw-r--r--extra/README41
1 files changed, 0 insertions, 41 deletions
diff --git a/extra/README b/extra/README
index 16659415fb..874a7b1b32 100644
--- a/extra/README
+++ b/extra/README
@@ -3,44 +3,3 @@ This directory is for experiments only. It is not built automatically,
required, supported, guaranteed to work, or necessarily well-documented.
The contents may change without warning at any time.
-
-------------------------------------------------------------------------------
-Lightbar simulator
-------------------------------------------------------------------------------
-
-Build with "make lightbar". The executable is "./lightbar".
-
-You may need to install libxcb1-dev or similar.
-
-This provides a simulation environment for the lightbar task, compiling
-common/lightbar.c from the EC source, but faking the rest of the EC.
-
-The EC console is on stdin/stdout, delivering all input to the lightbar's
-console command handler (so it prefixes any input with "lightbar"). The
-lightbar itself is displayed in an X window. You can click in that window to
-emulate changes to the battery level, AC connection, and brightness, all of
-which are normally outside the lightbar task's direct control.
-
-The initial sequence is "S5". Try issuing the command "seq s3s0" to see
-something more familiar.
-
-
-Note: the Pixel lightbar circuitry has three modes of operation:
-
-Unpowered
-
- When the host CPU is off (S5/G3), all power to the lightbar and its
- controller circuitry is lost.
-
-On
-
- When the host CPU is on (S0) or suspended (S3), the lightbar is powered
- again. After every power loss, it will need to be reinitialized by calling
- lb_init() before it can be used.
-
-Standby
-
- The lightbar controller ICs can turn off all the LED outputs to conserve
- power. This is the initial state when power is applied. You can turn the
- LEDs off manually by calling lb_off(). When suspended, the controller will
- respond to commands, but the LEDs aren't lit. Turn them on with lb_on().