diff --git a/source/devices/AM62PX/linux/_Release_Specific_QSG.rst b/source/devices/AM62PX/linux/_Release_Specific_QSG.rst index f6f3149a8..563b9cf38 100644 --- a/source/devices/AM62PX/linux/_Release_Specific_QSG.rst +++ b/source/devices/AM62PX/linux/_Release_Specific_QSG.rst @@ -76,7 +76,7 @@ on the target to verify that you are using the newly-built Linux kernel. .. code-block:: console - target# cat /proc/version + root@:~# cat /proc/version The output should indicate the build date, host PC name, etc. This verifies that your SDK has been setup correctly, enabling you to start development. diff --git a/source/devices/AM62X/linux/_Release_Specific_QSG.rst b/source/devices/AM62X/linux/_Release_Specific_QSG.rst index 78164da14..7282ed2af 100644 --- a/source/devices/AM62X/linux/_Release_Specific_QSG.rst +++ b/source/devices/AM62X/linux/_Release_Specific_QSG.rst @@ -76,7 +76,7 @@ on the target to verify that you are using the newly-built Linux kernel. .. code-block:: console - target# cat /proc/version + root@:~# cat /proc/version The output should indicate the build date, host PC name, etc. This verifies that your SDK has been setup correctly, enabling you to start development. diff --git a/source/linux/Foundational_Components/Hypervisor/Jailhouse.rst b/source/linux/Foundational_Components/Hypervisor/Jailhouse.rst index 66bebc96a..32dba6b89 100644 --- a/source/linux/Foundational_Components/Hypervisor/Jailhouse.rst +++ b/source/linux/Foundational_Components/Hypervisor/Jailhouse.rst @@ -750,7 +750,7 @@ the values using .. code-block:: console - target# cat /proc/interrupts | grep uio + root@:~# cat /proc/interrupts | grep uio Below changes in :file:`ivshmem-demo.c` can be done to send characters from root to inmate and vice versa. diff --git a/source/linux/How_to_Guides/Target/How_to_Recalibrate_the_Touchscreen.rst b/source/linux/How_to_Guides/Target/How_to_Recalibrate_the_Touchscreen.rst index 03121baec..e57d4b0d6 100644 --- a/source/linux/How_to_Guides/Target/How_to_Recalibrate_the_Touchscreen.rst +++ b/source/linux/How_to_Guides/Target/How_to_Recalibrate_the_Touchscreen.rst @@ -46,10 +46,10 @@ in this case if you already have a pointercal file on the SD card you will need to export the **TSLIB\_CALIBFILE** variable to point to that location before you run **ts\_calibrate**. i.e. -:: +.. code-block:: console - target# export TSLIB_CALIBFILE=/run/media/mmcblk0p1/pointercal - target# ts_calibrate + root@:~# export TSLIB_CALIBFILE=/run/media/mmcblk0p1/pointercal + root@:~# ts_calibrate **NOTE:** If you have Matrix or any other GUI application already running you should stop that application (`How to Stop @@ -111,9 +111,9 @@ Alternatively, you may delete the above listed files directly from the EVM's console by issuing the following commands at EVM's Linux prompt, and reboot the EVM to allow recalibration of the LCD. -:: +.. code-block:: console - rm /etc/udev/rules.d/ws-calibrate.rules - rm /run/media/mmcblk0p1/ws-calibrate.rules - reboot + root@:~# rm /etc/udev/rules.d/ws-calibrate.rules + root@:~# rm /run/media/mmcblk0p1/ws-calibrate.rules + root@:~# reboot diff --git a/source/linux/How_to_Guides/Target/Processor_SDK_Linux_File_System_Optimization_Customization.rst b/source/linux/How_to_Guides/Target/Processor_SDK_Linux_File_System_Optimization_Customization.rst index c62d20147..27c0ab9e4 100644 --- a/source/linux/How_to_Guides/Target/Processor_SDK_Linux_File_System_Optimization_Customization.rst +++ b/source/linux/How_to_Guides/Target/Processor_SDK_Linux_File_System_Optimization_Customization.rst @@ -24,14 +24,14 @@ by :command:`opkg` by running the following command on the target device: .. code-block:: console - target# opkg + root@:~# opkg To check the version of :command:`opkg` packaged in filesystem, .. code-block:: console - target# opkg --version - opkg version 0.6.3 (libsolv 0.7.28) + root@:~# opkg --version + opkg version 0.6.3 (libsolv 0.7.28) Show all installed packages =========================== @@ -41,7 +41,7 @@ each package you can run the following command on the target device: .. code-block:: console - target# opkg list-installed + root@:~# opkg list-installed .. important:: @@ -58,7 +58,7 @@ this you can use the following command: .. code-block:: console - target# opkg files + root@:~# opkg files Where is the name of the package as given in the *opkg list-installed* output. This command will produce a list of all the @@ -73,7 +73,7 @@ following command: .. code-block:: console - target# opkg search + root@:~# opkg search This command will find which package installed the given file. This may be useful later when you want to remove an particular file because this @@ -89,7 +89,7 @@ find the longer list of dependencies using: .. code-block:: console - target# opkg whatdepends + root@:~# opkg whatdepends This command will print the list of packages the depend on the package you entered, as well as the packages that depend on those packages, and @@ -104,7 +104,7 @@ pre-built packages). Removing a package is often as simple as: .. code-block:: console - target# opkg remove + root@:~# opkg remove However, sometimes a package is a DEPENDENCY of another package. In this case you have the following options: @@ -131,7 +131,7 @@ case you have the following options: .. code-block:: console - target# opkg remove --force-removal-of-dependent-packages + root@:~# opkg remove --force-removal-of-dependent-packages .. tip:: diff --git a/source/linux/How_to_Guides/Target/Update_U-Boot_Environment_Variables_stored_in_SPI_Flash_from_Linux.rst b/source/linux/How_to_Guides/Target/Update_U-Boot_Environment_Variables_stored_in_SPI_Flash_from_Linux.rst index 779804120..2ccef7f10 100644 --- a/source/linux/How_to_Guides/Target/Update_U-Boot_Environment_Variables_stored_in_SPI_Flash_from_Linux.rst +++ b/source/linux/How_to_Guides/Target/Update_U-Boot_Environment_Variables_stored_in_SPI_Flash_from_Linux.rst @@ -53,9 +53,9 @@ SPI MTD partitioning. Please note that the CROSS\_COMPILE flag is not used by the u-boot makefile here, the HOSTCC= variable must be set. -:: +.. code-block:: console - host# make HOSTCC=arm-arago-linux-gnueabi-gcc env + host# make HOSTCC=arm-arago-linux-gnueabi-gcc env This command is issued from the top of the u-boot source directory. Please be sure to see that the cross compiler was actually called and @@ -100,14 +100,14 @@ will run in. The executable fw\_printenv will dump the entire environment space, individual variables can be read by: -:: +.. code-block:: console - target# ./fw_printenv autoload + root@:~# ./fw_printenv autoload To set an environment variable use fw\_setenv . This example will set the variable autoload to no, use fw\_printenv to read back the change. -:: +.. code-block:: console - target# ./fw_setenv autoload no + root@:~# ./fw_setenv autoload no