User: Change output block to type none.

user/tools/bsp-builder.rst

@@ -344,7 +344,7 @@ spinning disk mounted under `build`. The build uses a development source tree
 that is bootstrapped and ready to build. The source can have local patches that
 need to be regression tested:
 
-.. code-block:: shell
+.. code-block:: none
 
   $ /opt/rtems/5/bin/rtems-bsp-builder --build-path=/build/rtems \
             --rtems-tools=/opt/work/rtems/5 \
@@ -393,7 +393,7 @@ need to be regression tested:
 
 To build a couple of BSPs you are interested in with tests:
 
-.. code-block:: shell
+.. code-block:: none
 
   $ /opt/rtems/5/bin/rtems-bsp-builder --build-path=/build/rtems \
             --rtems-tools=/opt/work/rtems/5 \

user/tools/exeinfo.rst

@@ -94,7 +94,7 @@ Examples
 
 Prints all reports for the ``hello.exe`` for the ``i386/pc686`` BSP:
 
-.. code-block:: shell
+.. code-block:: none
 
   $ rtems-exeinfo -a i386-rtems5/c/pc686/testsuites/samples/hello/hello.exe
   RTEMS Executable Info 5.6f5cfada964c
@@ -168,7 +168,7 @@ drivers.
 
 Print the ``Init`` section data for the ``cdtest.exe`` for the ``i386/pc686`` BSP:
 
-.. code-block:: shell
+.. code-block:: none
 
   $ rtems-exeinfo -I i386-rtems5/c/pc686/testsuites/samples/cdtest/cdtest.exe
   RTEMS Executable Info 5.6f5cfada964c

user/tools/symbols.rst

@@ -135,7 +135,7 @@ Examples
 Create a dynamlically loaded symbol table for the ``minimum.exe`` sample
 program for the ``i386/pc686`` BSP:
 
-.. code-block:: shell
+.. code-block:: none
 
   $ rtems-syms -o ms.o i386-rtems5/c/pc686/testsuites/samples/minimum/minimum.exe
   $ file ms.o
@@ -143,7 +143,7 @@ program for the ``i386/pc686`` BSP:
 
 Run the same command, this time create a map file:
 
-.. code-block:: shell
+.. code-block:: none
 
   $ rtems-syms -o ms.o -m ms.map i386-rtems5/c/pc686/testsuites/samples/minimum/minimum.exe
   $ head -10 ms.map
@@ -161,7 +161,7 @@ Run the same command, this time create a map file:
 Run the same command with a raise verbose level to observe the stages the
 command performs:
 
-.. code-block:: shell
+.. code-block:: none
 
   $ rtems-syms -vvv -o ms.o i386-rtems5/c/pc686/testsuites/samples/minimum/minimum.exe
   RTEMS Kernel Symbols 5.a72a462adc18

user/tools/tester.rst

@@ -36,7 +36,7 @@ Available BSP testers
 
 You can list the available BSP testers with:
 
-.. code-block:: shell
+.. code-block:: none
 
     $ rtems-test --list-bsps
     arm920
@@ -78,7 +78,7 @@ running the ``bootstrap`` procedure, building and finally installing the
 kernel. Be sure to enable tests by using ``--enable-tests`` option with
 configure after running ``bootstrap``.
 
-.. code-block:: shell
+.. code-block:: none
 
     $ ../../rtems.git/configure --target=sparc-rtems5 \
                         --enable-tests --enable-rtemsbsp=erc32
@@ -99,7 +99,7 @@ Before running all the tests it is a good idea to run the ``hello`` test. The
 running it shows you have a working tool chain and build of RTEMS ready to run
 the tests. Using the run with the ERC32 BSP the command is:
 
-.. code-block:: shell
+.. code-block:: none
 
     $ sparc-rtems5-run sparc-rtems5/c/erc32/testsuites/samples/hello/hello.exe
 
@@ -111,7 +111,7 @@ The run command is the GDB simulator without the GDB part.
 
 Running the example using GDB:
 
-.. code-block:: shell
+.. code-block:: none
 
     $ sparc-rtems5-gdb sparc-rtems5/c/erc32/testsuites/samples/hello/hello.exe
     GNU gdb (GDB) 7.12
@@ -162,7 +162,7 @@ extension for RTEMS executables built within RTEMS.
 To run the erc32 tests enter the following command from the top of the erc32
 BSP build tree:
 
-.. code-block:: shell
+.. code-block:: none
 
     $ ~/development/rtems/test/rtems-tools.git/tester/rtems-test \
              --log=log_erc32_run \
@@ -234,7 +234,7 @@ invalid count changing means a test running before this test started failed,
 not the starting test. The status here has 7 tests passed, no failures, 5
 timeouts and 1 invalid test.
 
-.. code-block:: shell
+.. code-block:: none
 
     [ 5/13] p:2  f:0  u:0  e:0  I:0  B:0  t:0  i:0  | sparc/erc32: hello.exe
 
@@ -345,7 +345,7 @@ The output is tagged so you can determine where it comes from. The following is
 the complete output for the In Memory File System test ``imfs_fslink.exe``
 running on a Coldfire MCF5235 using GDB and a BDM pod:
 
-.. code-block:: shell
+.. code-block:: none
 
     [ 11/472] p:9   f:0   t:0   i:1   | m68k/mcf5235: imfs_fslink.exe
     > gdb: ..../bin/m68k-rtems4.11-gdb -i=mi --nx --quiet ..../imfs_fslink.exe
@@ -429,7 +429,7 @@ Command Line Help
 The :program:`rtems-test` command line accepts a range of options. You can
 review the available option by the ``--help`` option:
 
-.. code-block:: shell
+.. code-block:: none
 
     RTEMS Tools Project (c) 2012-2014 Chris Johns
     Options and arguments: