mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Holger Schurig <holgerschurig@gmail.com>
To: barebox@lists.infradead.org
Subject: [PATCH 09/12] doc: remove board type from barebox prompt examples
Date: Fri, 27 Jun 2014 13:00:18 +0200	[thread overview]
Message-ID: <1403866821-4029-10-git-send-email-holgerschurig@gmail.com> (raw)
In-Reply-To: <1403866821-4029-1-git-send-email-holgerschurig@gmail.com>

I kept however the one example that directly demos the bootup on an
Efika board.
---
 Documentation/user/driver-model.rst |   10 +++++-----
 Documentation/user/networking.rst   |    2 +-
 Documentation/user/updating.rst     |    2 +-
 Documentation/user/variables.rst    |    2 +-
 4 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/Documentation/user/driver-model.rst b/Documentation/user/driver-model.rst
index fae275e..ab7d292 100644
--- a/Documentation/user/driver-model.rst
+++ b/Documentation/user/driver-model.rst
@@ -34,7 +34,7 @@ handled with device detection. The user visible interface to device detection
 is the :ref:`command_detect` command. ``detect -l`` shows a list of detectable
 devices::
 
-  barebox@Genesi Efika MX Smartbook:/ detect -l
+  barebox:/ detect -l
   70004000.esdhc
   70008000.esdhc
   73f80000.usb
@@ -48,7 +48,7 @@ devices::
 
 A particular device can be detected with ``detect <devname>``::
 
-  barebox@Genesi Efika MX Smartbook:/ detect 73f80200.usb
+  barebox:/ detect 73f80200.usb
   Found SMSC USB331x ULPI transceiver (0x0424:0x0006).
   Bus 002 Device 004: ID 13d3:3273 802.11 n WLAN
   mdio_bus: miibus0: probed
@@ -67,7 +67,7 @@ additional information for a device. The parameters can be listed with the
 :ref:`command_devinfo` command. A ``devinfo <devicename>`` will print the parameters
 of a device::
 
-  barebox@Genesi Efika MX Smartbook:/ devinfo eth0
+  barebox:/ devinfo eth0
   Parameters:
     ipaddr: 192.168.23.197
     serverip: 192.168.23.1
@@ -82,9 +82,9 @@ The parameters can be used as shell variables::
 
 device variables may have a type, so assigning wrong values may fail::
 
-  barebox@Genesi Efika MX Smartbook:/ eth0.ipaddr="This is not an IP"
+  barebox:/ eth0.ipaddr="This is not an IP"
   set parameter: Invalid argument
-  barebox@Genesi Efika MX Smartbook:/ echo $?
+  barebox:/ echo $?
   1
 
 **HINT:** barebox has tab completion for variables. Typing ``eth0.<TAB><TAB>``
diff --git a/Documentation/user/networking.rst b/Documentation/user/networking.rst
index c22685f..9c6eeb6 100644
--- a/Documentation/user/networking.rst
+++ b/Documentation/user/networking.rst
@@ -14,7 +14,7 @@ device is usually ``eth0``. The current configuration can be viewed with the
 
 .. code-block:: sh
 
-  barebox@Genesi Efika MX Smartbook:/ devinfo eth0
+  barebox:/ devinfo eth0
   Parameters:
     ipaddr: 192.168.23.197
     serverip: 192.168.23.1
diff --git a/Documentation/user/updating.rst b/Documentation/user/updating.rst
index 0503e7d..2a963b6 100644
--- a/Documentation/user/updating.rst
+++ b/Documentation/user/updating.rst
@@ -18,7 +18,7 @@ Updating barebox can be as easy as::
 Multiple handlers can be registered to the update mechanism. Usually the device
 barebox has been started from is registered as default (marked with a ``*``)::
 
-  barebox@Genesi Efika MX Smartbook:/ barebox_update -l
+  barebox:/ barebox_update -l
   registered update handlers:
   * mmc         -> /dev/mmc1
     spinor	-> /dev/m25p0
diff --git a/Documentation/user/variables.rst b/Documentation/user/variables.rst
index e349874..13477a0 100644
--- a/Documentation/user/variables.rst
+++ b/Documentation/user/variables.rst
@@ -33,7 +33,7 @@ Since it's hard to remember which variables these are and if the current
 barebox has support for them the :ref:`command_magicvar` command can print a list
 of all variables with special meaning along with a short description::
 
-  barebox@Genesi Efika MX Smartbook:/ magicvar
+  barebox:/ magicvar
   OPTARG                           optarg for hush builtin getopt
   PATH                             colon separated list of pathes to search for executables
   PS1                              hush prompt
-- 
1.7.10.4


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  parent reply	other threads:[~2014-06-27 10:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-27 11:00 [PATCH 00/12] documentation updates Holger Schurig
2014-06-27 11:00 ` [PATCH 01/12] doc: .gitignore generated files Holger Schurig
2014-06-27 11:00 ` [PATCH 02/12] doc: make "System setup" an appendix Holger Schurig
2014-06-27 11:00 ` [PATCH 03/12] doc: start (almost) all headlines with a capital Holger Schurig
2014-06-27 11:00 ` [PATCH 04/12] doc: only include own download chapter Holger Schurig
2014-06-27 11:00 ` [PATCH 05/12] doc: filesystemtype -> filesystem type Holger Schurig
2014-06-27 11:00 ` [PATCH 06/12] doc: mention "make xconfig" Holger Schurig
2014-06-27 11:00 ` [PATCH 07/12] doc: add colon after NOTE and HINT Holger Schurig
2014-06-27 11:00 ` [PATCH 08/12] doc: add hint on how to calculate in hush Holger Schurig
2014-06-27 11:00 ` Holger Schurig [this message]
2014-06-27 11:00 ` [PATCH 10/12] doc: reformat overly long lines Holger Schurig
2014-06-27 11:00 ` [PATCH 11/12] doc: move variables near device parameters Holger Schurig
2014-06-27 11:00 ` [PATCH 12/12] doc: link back from variables to " Holger Schurig
2014-06-27 19:48 ` [PATCH 00/12] documentation updates Sascha Hauer

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=1403866821-4029-10-git-send-email-holgerschurig@gmail.com \
    --to=holgerschurig@gmail.com \
    --cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox