From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] doc: add README for CONFIG_HWCONFIG option
Date: Tue, 09 Feb 2010 15:50:30 +0100 [thread overview]
Message-ID: <4B717636.8060203@denx.de> (raw)
Signed-off-by: Heiko Schocher <hs@xpert.denx.de>
---
doc/README.hwconfig | 51 +++++++++++++++++++++++++++++++++++++++++++++++++++
1 files changed, 51 insertions(+), 0 deletions(-)
create mode 100644 doc/README.hwconfig
diff --git a/doc/README.hwconfig b/doc/README.hwconfig
new file mode 100644
index 0000000..dd5bdd8
--- /dev/null
+++ b/doc/README.hwconfig
@@ -0,0 +1,51 @@
+Enable this feature just define CONFIG_HWCONFIG in your board
+config file.
+
+This implements simple hwconfig infrastructure: an
+interface for software knobs to control a hardware.
+
+This is very simple implementation, i.e. it is implemented
+via `hwconfig' environment variable. Later we could write
+some "hwconfig <enable|disable|list>" commands, ncurses
+interface for Award BIOS-like interface, and frame-buffer
+interface for AMI GUI[1] BIOS-like interface with mouse
+support[2].
+
+Current implementation details/limitations:
+
+1. Doesn't support options dependencies and mutual exclusion.
+ We can implement this by integrating apt-get[3] into the
+ u-boot. But I didn't bother yet.
+
+2. Since we don't implement hwconfig command, i.e. we're working
+ with the environement directly, there is no way to tell that
+ toggling a particular option will need a reboot to take
+ an effect. So, for now it's advised to always reboot the
+ target after modifying hwconfig variable.
+
+3. We support hwconfig options with arguments. For example,
+
+ set hwconfig "dr_usb:mode=peripheral,phy_type=ulpi"
+
+ There are three hwconfig options selected:
+ 1. dr_usb - enable Dual-Role USB controller;
+ 2. dr_usb_mode:peripheral - USB in Function mode;
+ 3. dr_usb_phy_type:ulpi - USB should work with ULPI PHYs.
+
+The purpose of this simple implementation is to define some
+internal API and then we can continue improving user experience
+by adding more mature interface, like hwconfig command with
+bells and whistles. Or not adding, if we feel that current
+interface fits its needs.
+
+[1] http://en.wikipedia.org/wiki/American_Megatrends
+[2] Regarding ncurses and GUI with mouse support -- I'm just
+ kidding.
+[3] The comment regarding apt-get is also a joke, meaning that
+ dependency tracking could be non-trivial. For example, for
+ enabling HW feature X we may need to disable Y, and turn Z
+ into reduced mode (like RMII-only interface for ethernet,
+ no MII).
+
+ It's quite trivial to implement simple cases though.
+
--
1.6.2.5
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next reply other threads:[~2010-02-09 14:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-09 14:50 Heiko Schocher [this message]
2010-02-09 17:44 ` [U-Boot] doc: add README for CONFIG_HWCONFIG option Mike Frysinger
2010-02-10 7:03 ` [U-Boot] [PATCH v2] [PATCH] " Heiko Schocher
2010-03-11 23:09 ` Wolfgang Denk
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=4B717636.8060203@denx.de \
--to=hs@denx.de \
--cc=u-boot@lists.denx.de \
/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.