summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorSimon Glass <sjg@chromium.org>2015-03-02 12:40:50 -0700
committerSimon Glass <sjg@chromium.org>2015-04-16 19:27:40 -0600
commit5692ccfacae05175ffa5a8e9c12ef7bda3631433 (patch)
treed4d572fc337e0e34ad37f05ecb00a278c5ca5bfd /doc
parent892ff8e972efc7d4f42750e4fdbb2c2fefb78229 (diff)
downloadtalos-obmc-uboot-5692ccfacae05175ffa5a8e9c12ef7bda3631433.tar.gz
talos-obmc-uboot-5692ccfacae05175ffa5a8e9c12ef7bda3631433.zip
x86: video: Allow keyboard presence to be controlled by device tree
At present a VGA console assumes a keyboard unless a CONFIG option is set. This difference can be dealt with by a device tree option, allowing boards that are otherwise the same to use the same configuration. Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'doc')
-rw-r--r--doc/README.fdt-control16
1 files changed, 16 insertions, 0 deletions
diff --git a/doc/README.fdt-control b/doc/README.fdt-control
index d8fe4a826f..e6d5ed0bb6 100644
--- a/doc/README.fdt-control
+++ b/doc/README.fdt-control
@@ -171,6 +171,22 @@ After board configuration is done, fdt supported u-boot can be build in two ways
$ make DEVICE_TREE=<dts-file-name>
+Configuration Options
+---------------------
+
+A number of run-time configuration options are provided in the /config node
+of the control device tree. You can access these using fdtdec_get_config_int(),
+fdtdec_get_config_bool() and fdtdec_get_config_string().
+
+Available options are:
+
+silent-console
+ If present and non-zero, the console is silenced by default on boot.
+
+no-keyboard
+ Tells U-Boot not to expect an attached keyboard with a VGA console
+
+
Limitations
-----------
OpenPOWER on IntegriCloud