diff --git a/books/beaglebone-cookbook/07kernel/kernel.rst b/books/beaglebone-cookbook/07kernel/kernel.rst
index a58663c82050d4976d7d845a477e05b0d8a30206..556939cc384a7cf0ebd841d04361f1ff6f200e81 100644
--- a/books/beaglebone-cookbook/07kernel/kernel.rst
+++ b/books/beaglebone-cookbook/07kernel/kernel.rst
@@ -28,11 +28,11 @@ Use the following command to determine which kernel you are running:
.. code-block:: bash
bone$ uname -a
- Linux beaglebone 5.10.168-ti-r62 #1bullseye SMP PREEMPT Tue May 23 20:15:00 UTC 2023 armv7l GNU/Linux
+ Linux beaglebone 5.10.168-ti-r62 #1bullseye SMP PREEMPT Tue May 23 20:15:00 UTC 2023 armv7l GNU/Linux
GNU/Linux
-The *5.10.168-ti-r62* string is the kernel version.
+The *5.10.168-ti-r62* string is the kernel version.
To update to the current kernel, ensure that your Bone is on the Internet
(:ref:`networking_usb` or :ref:`networking_wired`) and then run the following commands:
@@ -41,29 +41,29 @@ To update to the current kernel, ensure that your Bone is on the Internet
bone$ apt-cache pkgnames | grep linux-image | sort | less
...
- linux-image-5.10.162-ti-r59
- linux-image-5.10.162-ti-rt-r56
- linux-image-5.10.162-ti-rt-r57
- linux-image-5.10.162-ti-rt-r58
- linux-image-5.10.162-ti-rt-r59
- linux-image-5.10.168-armv7-lpae-x71
- linux-image-5.10.168-armv7-rt-x71
- linux-image-5.10.168-armv7-x71
- linux-image-5.10.168-bone71
- linux-image-5.10.168-bone-rt-r71
- linux-image-5.10.168-ti-r60
- linux-image-5.10.168-ti-r61
- linux-image-5.10.168-ti-r62
- linux-image-5.10.168-ti-rt-r60
- linux-image-5.10.168-ti-rt-r61
- linux-image-5.10.168-ti-rt-r62
+ linux-image-5.10.162-ti-r59
+ linux-image-5.10.162-ti-rt-r56
+ linux-image-5.10.162-ti-rt-r57
+ linux-image-5.10.162-ti-rt-r58
+ linux-image-5.10.162-ti-rt-r59
+ linux-image-5.10.168-armv7-lpae-x71
+ linux-image-5.10.168-armv7-rt-x71
+ linux-image-5.10.168-armv7-x71
+ linux-image-5.10.168-bone71
+ linux-image-5.10.168-bone-rt-r71
+ linux-image-5.10.168-ti-r60
+ linux-image-5.10.168-ti-r61
+ linux-image-5.10.168-ti-r62
+ linux-image-5.10.168-ti-rt-r60
+ linux-image-5.10.168-ti-rt-r61
+ linux-image-5.10.168-ti-rt-r62
...
-
- bone$ sudo apt install linux-image-5.10.162-ti-rt-r59
+
+ bone$ sudo apt install linux-image-5.10.162-ti-rt-r59
bone$ sudo reboot
-
+
bone$ uname -a
- Linux beaglebone 5.10.162-ti-rt-r59 #1 SMP PREEMPT Wed Nov 19 21:11:08 UTC 2014 armv7l
+ Linux beaglebone 5.10.162-ti-rt-r59 #1 SMP PREEMPT Wed Nov 19 21:11:08 UTC 2014 armv7l
GNU/Linux
@@ -71,7 +71,61 @@ The first command lists the versions of the kernel that are available. The secon
After you have rebooted, the new kernel will be running.
If the current kernel is doing its job adequately, you probably don't need to update, but sometimes a new
-software package requires a more up-to-date kernel. Fortunately, precompiled kernels are available and ready to download.
+software package requires a more up-to-date kernel.
+Fortunately, precompiled kernels are available and ready to download.
+
+Seeing which kernels are installed
+^^^
+
+You can have multiple kernels install at the same time. T
+hey are saved in **/boot**
+
+.. code-block:: bash
+
+ bone$ cd /boot
+ bone$ ls
+ config-5.10.168-ti-r62 initrd.img-5.10.168-ti-r63 uboot vmlinuz-5.10.168-ti-r63
+ config-5.10.168-ti-r63 SOC.sh uEnv.txt
+ dtbs System.map-5.10.168-ti-r62 uEnv.txt.orig
+ initrd.img-5.10.168-ti-r62 System.map-5.10.168-ti-r63 vmlinuz-5.10.168-ti-r62
+
+Here I have two kernel versions installed.
+
+.. tabs::
+
+ .. group-tab:: Bone
+
+ On the Bone (Not the Play) the file **uEnv.txt** tells which
+ kernel to use on the next reboot. Here are the first few lines:
+
+ .. code-block:: bash
+
+ Line
+ 1 #Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0
+ 2
+ 3 # uname_r=4.14.108-ti-r137
+ 4 uname_r=4.19.94-ti-r50
+ 5 # uname_r=5.4.52-ti-r17
+ 6 #uuid=
+
+ Lines 3-5 list the various kernels, and the uncommented one on line 4 is the one that will be used next time. You will have to add your own uname's. Get the names from the files in /boot. Be careful, if you mistype the name your Bone won't boot.
+
+ .. group-tab:: Play
+
+ On the Play you can see which version of the kernel will boot
+ next by:
+
+ .. code-block:: bash
+
+ play$ cat /boot/firmware/kversion
+ 5.10.168-ti-arm64-r106
+
+If you want to change the version run:
+
+.. code-block:: bash
+
+ bone$ sudo apt install linux-image-5.10.168-ti-arm64-r105 --reinstall
+
.. _kernel_building_modules:
@@ -88,7 +142,7 @@ Solution
---------
The solution is to run in kernel space by building a kernel module. There are entire
-`books on writing Linux Device Drivers <https://bootlin.com/doc/books/ldd3.pdf>`_. This recipe assumes that
+`books on writing Linux Device Drivers <https://bootlin.com/doc/books/ldd3.pdf>`_. This recipe assumes that
the driver has already been written and shows how to compile and install it. After you've
followed the steps for this simple module, you will be able to apply them to any other module.
@@ -107,7 +161,7 @@ Headers for the version of the kernel you're running:
.. code-block:: bash
- bone$ sudo apt install linux-headers-`uname -r`
+ bone$ sudo apt install linux-headers-`uname -r`
.. note::
@@ -138,14 +192,14 @@ Now, compile the kernel module by using the *make* command:
.. code-block:: bash
bone$ make
- make -C /lib/modules/5.10.168-ti-r62/build M=$PWD
- make[1]: Entering directory '/usr/src/linux-headers-5.10.168-ti-r62'
- CC [M] /home/debian/docs.beagleboard.io/books/beaglebone-cookbook/code/07kernel/hello.o
- MODPOST /home/debian/docs.beagleboard.io/books/beaglebone-cookbook/code/07kernel/Module.symvers
- CC [M] /home/debian/docs.beagleboard.io/books/beaglebone-cookbook/code/07kernel/hello.mod.o
- LD [M] /home/debian/host/BeagleBoard/docs.beagleboard.io/books/beaglebone-cookbook/code/07kernel/hello.ko
- make[1]: Leaving directory '/usr/src/linux-headers-5.10.168-ti-r62'
-
+ make -C /lib/modules/5.10.168-ti-r62/build M=$PWD
+ make[1]: Entering directory '/usr/src/linux-headers-5.10.168-ti-r62'
+ CC [M] /home/debian/docs.beagleboard.io/books/beaglebone-cookbook/code/07kernel/hello.o
+ MODPOST /home/debian/docs.beagleboard.io/books/beaglebone-cookbook/code/07kernel/Module.symvers
+ CC [M] /home/debian/docs.beagleboard.io/books/beaglebone-cookbook/code/07kernel/hello.mod.o
+ LD [M] /home/debian/host/BeagleBoard/docs.beagleboard.io/books/beaglebone-cookbook/code/07kernel/hello.ko
+ make[1]: Leaving directory '/usr/src/linux-headers-5.10.168-ti-r62'
+
bone$ ls
Makefile hello.c hello.mod.c hello.o
Module.symvers hello.ko hello.mod.o modules.order
@@ -156,20 +210,20 @@ Notice that several files have been created.
.. code-block:: bash
bone$ modinfo hello.ko
- filename: /home/debian/host/BeagleBoard/docs.beagleboard.io/books/beaglebone-cookbook/code/07kernel/hello.ko
- license: GPL
- description: Hello World Example
- author: Boris Houndleroy
+ filename: /home/debian/host/BeagleBoard/docs.beagleboard.io/books/beaglebone-cookbook/code/07kernel/hello.ko
+ license: GPL
+ description: Hello World Example
+ author: Boris Houndleroy
depends:
- name: hello
- vermagic: 5.10.168-ti-r62 SMP preempt mod_unload modversions ARMv7 p2v8
-
+ name: hello
+ vermagic: 5.10.168-ti-r62 SMP preempt mod_unload modversions ARMv7 p2v8
+
bone$ sudo insmod hello.ko
bone$ dmesg | tail -4
- [ 377.944777] lm75 1-004a: hwmon1: sensor 'tmp101'
- [ 377.944976] i2c i2c-1: new_device: Instantiated device tmp101 at 0x4a
- [85819.772666] Loading hello module...
- [85819.772687] Hello, World!
+ [ 377.944777] lm75 1-004a: hwmon1: sensor 'tmp101'
+ [ 377.944976] i2c i2c-1: new_device: Instantiated device tmp101 at 0x4a
+ [85819.772666] Loading hello module...
+ [85819.772687] Hello, World!
The first command displays information about the module. The *insmod* command inserts the module into the running kernel.
If all goes well, nothing is displayed, but the module does print something in the kernel log. The *dmesg* command displays
@@ -376,32 +430,32 @@ To download and compile the kernel, follow these steps:
.. code-block:: bash
- host$ git clone https://git.beagleboard.org/RobertCNelson/ti-linux-kernel-dev # <1>
- host$ cd ti-linux-kernel-dev
- host$ git checkout ti-linux-5.10.y # <2>
- host$ ./build_deb.sh # <3>
-
-.. note::
- If you are using a 64 bit Bone, **git checkout ti-linux-arm64-5.10.y**
+ host$ git clone https://git.beagleboard.org/RobertCNelson/ti-linux-kernel-dev # <1>
+ host$ cd ti-linux-kernel-dev
+ host$ git checkout ti-linux-5.10.y # <2>
+ host$ ./build_deb.sh # <3>
+
+.. note::
+ If you are using a 64 bit Bone, **git checkout ti-linux-arm64-5.10.y**
1. The first command clones a repository with the tools to build the kernel for the Bone.
-2. When you know which kernel to try, use *git checkout* to check it out.
- This command checks out branch *ti-linux-5.10.y*.
-3. *build_deb.sh* is the master builder. If needed, it will download the cross compilers
- needed to compile the kernel (`gcc <https://gcc.gnu.org/>`_ is the current cross compiler).
- If there is a kernel at ``~/linux-dev``, it will use it; otherwise,
- it will download a copy to ``ti-linux-kernel-dev/ignore/linux-src``.
- It will then patch the kernel so that it will run on the Bone.
-
-.. note::
- *build_deb.sh* may ask you to install additional files. Just run **sudo apt install *files*** to
- install them.
+2. When you know which kernel to try, use *git checkout* to check it out.
+ This command checks out branch *ti-linux-5.10.y*.
+3. *build_deb.sh* is the master builder. If needed, it will download the cross compilers
+ needed to compile the kernel (`gcc <https://gcc.gnu.org/>`_ is the current cross compiler).
+ If there is a kernel at ``~/linux-dev``, it will use it; otherwise,
+ it will download a copy to ``ti-linux-kernel-dev/ignore/linux-src``.
+ It will then patch the kernel so that it will run on the Bone.
+
+.. note::
+ *build_deb.sh* may ask you to install additional files. Just run **sudo apt install *files*** to
+ install them.
After the kernel is patched, you'll see a screen similar to :ref:`kernel_config_fig`, on which you can configure the kernel.
.. _kernel_config_fig:
-.. figure:: figures/KernelConfig5.10.png
+.. figure:: figures/KernelConfig5.10.png
:align: center
:alt: Kernel configuration menu
@@ -410,7 +464,7 @@ After the kernel is patched, you'll see a screen similar to :ref:`kernel_config_
You can use the arrow keys to navigate. No changes need to be made, so you can just press the right
arrow and Enter to start the kernel compiling. The entire process took about 25 minutes on my 8-core host.
-The ``ti-linux-kernel-dev/KERNEL`` directory contains the source code for the kernel. The ``ti-linux-kernel-dev/deploy``
+The ``ti-linux-kernel-dev/KERNEL`` directory contains the source code for the kernel. The ``ti-linux-kernel-dev/deploy``
directory contains the compiled kernel and the files needed to run it.
.. _kernel_install:
@@ -418,105 +472,105 @@ directory contains the compiled kernel and the files needed to run it.
Installing the Kernel on the Bone
===================================
-The **./build_deb.sh** script creates a single .deb file that contains all the files needed for the new kernel.
-You find it here:
-
-.. code-block:: bash
-
- host$ cd ti-linux-kernel-dev/deploy
- host$ ls -sh
- total 40M
- 7.7M linux-headers-5.10.168-ti-r62_1xross_armhf.deb 8.0K linux-upstream_1xross_armhf.buildinfo
- 33M linux-image-5.10.168-ti-r62_1xross_armhf.deb 4.0K linux-upstream_1xross_armhf.changes
- 1.1M linux-libc-dev_1xross_armhf.deb
-
-The **linux-image-** file is the one we want. It contains over 3000 files.
-
-.. code-block:: bash
-
- host$ dpkg -c linux-image-5.10.168-ti-r62_1xross_armhf.deb | wc
- 3251 19506 379250
-
-The **dpkg** command lists all the files in the .deb file and the wc counts all the lines in the output.
-You can see those files with:
-
-.. code-block:: bash
-
- host$ dpkg -c linux-image-5.10.168-ti-r62_1xross_armhf.deb | less
- drwxr-xr-x root/root 0 2023-06-12 12:57 ./
- drwxr-xr-x root/root 0 2023-06-12 12:57 ./boot/
- -rw-r--r-- root/root 4763113 2023-06-12 12:57 ./boot/System.map-5.10.168-ti-r62
- -rw-r--r-- root/root 191331 2023-06-12 12:57 ./boot/config-5.10.168-ti-r62
- drwxr-xr-x root/root 0 2023-06-12 12:57 ./boot/dtbs/
- drwxr-xr-x root/root 0 2023-06-12 12:57 ./boot/dtbs/5.10.168-ti-r62/
- -rwxr-xr-x root/root 90644 2023-06-12 12:57 ./boot/dtbs/5.10.168-ti-r62/am335x-baltos-ir2110.dtb
- -rwxr-xr-x root/root 91362 2023-06-12 12:57 ./boot/dtbs/5.10.168-ti-r62/am335x-baltos-ir3220.dtb
- -rwxr-xr-x root/root 91633 2023-06-12 12:57 ./boot/dtbs/5.10.168-ti-r62/am335x-baltos-ir5221.dtb
- -rwxr-xr-x root/root 88684 2023-06-12 12:57 ./boot/dtbs/5.10.168-ti-r62/am335x-base0033.dtb
-
-You can see it's putting things in the **/boot** directory.
-
-Note: You can also look into the other two .deb files and see what they install.
-
-Move the **linux-image-** file to your Bone.
-
-.. code-block:: bash
-
- host$ scp linux-image-5.10.168-ti-r62_1xross_armhf.deb bone:.
-
-You might have to use debian@192.168.7.2 for bone if you haven't set everything up.
-
-Now ssh to the bone.
-
-.. code-block:: bash
-
- host$ ssh bone
- bone$ ls -sh
- bin exercises linux-image-5.10.168-ti-r62_1xross_armhf.deb
-
-Now install it.
-
-.. code-block:: bash
-
- bone$ sudo dpkg --install linux-image-5.10.168-ti-r62_1xross_armhf.deb
-
-Wait a while. (Mine took almore 2 minutes.) Once done check /boot.
-
-.. code-block:: bash
-
- bone$ ls -sh /boot
- total 40M
- 160K config-4.19.94-ti-r50 4.0K SOC.sh 4.0K uEnv.txt.orig
- 180K config-5.10.168-ti-r62 3.5M System.map-4.19.94-ti-r50 9.7M vmlinuz-4.19.94-ti-r50
- 4.0K dtbs 4.1M System.map-5.10.168-ti-r62 8.6M vmlinuz-5.10.168-ti-r62
- 6.4M initrd.img-4.19.94-ti-r50 4.0K uboot
- 6.8M initrd.img-5.10.168-ti-r62 4.0K uEnv.txt
-
-You see the new kernel files along with the old files. Check uEnv.txt.
-
-.. code-block:: bash
-
- bone$ head /boot/uEnv.txt
- #Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0
- # uname_r=4.19.94-ti-r50
- uname_r=5.10.168-ti-r62
-
-I added the commented out uname_r line to make it easy to switch between versions of the kernel.
-
-Reboot and test out the new kernel.
-
-.. code-block:: bash
-
- bone$ sudo reboot
+The **./build_deb.sh** script creates a single .deb file that contains all the files needed for the new kernel.
+You find it here:
+
+.. code-block:: bash
+
+ host$ cd ti-linux-kernel-dev/deploy
+ host$ ls -sh
+ total 40M
+ 7.7M linux-headers-5.10.168-ti-r62_1xross_armhf.deb 8.0K linux-upstream_1xross_armhf.buildinfo
+ 33M linux-image-5.10.168-ti-r62_1xross_armhf.deb 4.0K linux-upstream_1xross_armhf.changes
+ 1.1M linux-libc-dev_1xross_armhf.deb
+
+The **linux-image-** file is the one we want. It contains over 3000 files.
+
+.. code-block:: bash
+
+ host$ dpkg -c linux-image-5.10.168-ti-r62_1xross_armhf.deb | wc
+ 3251 19506 379250
+
+The **dpkg** command lists all the files in the .deb file and the wc counts all the lines in the output.
+You can see those files with:
+
+.. code-block:: bash
+
+ host$ dpkg -c linux-image-5.10.168-ti-r62_1xross_armhf.deb | less
+ drwxr-xr-x root/root 0 2023-06-12 12:57 ./
+ drwxr-xr-x root/root 0 2023-06-12 12:57 ./boot/
+ -rw-r--r-- root/root 4763113 2023-06-12 12:57 ./boot/System.map-5.10.168-ti-r62
+ -rw-r--r-- root/root 191331 2023-06-12 12:57 ./boot/config-5.10.168-ti-r62
+ drwxr-xr-x root/root 0 2023-06-12 12:57 ./boot/dtbs/
+ drwxr-xr-x root/root 0 2023-06-12 12:57 ./boot/dtbs/5.10.168-ti-r62/
+ -rwxr-xr-x root/root 90644 2023-06-12 12:57 ./boot/dtbs/5.10.168-ti-r62/am335x-baltos-ir2110.dtb
+ -rwxr-xr-x root/root 91362 2023-06-12 12:57 ./boot/dtbs/5.10.168-ti-r62/am335x-baltos-ir3220.dtb
+ -rwxr-xr-x root/root 91633 2023-06-12 12:57 ./boot/dtbs/5.10.168-ti-r62/am335x-baltos-ir5221.dtb
+ -rwxr-xr-x root/root 88684 2023-06-12 12:57 ./boot/dtbs/5.10.168-ti-r62/am335x-base0033.dtb
+
+You can see it's putting things in the **/boot** directory.
+
+Note: You can also look into the other two .deb files and see what they install.
+
+Move the **linux-image-** file to your Bone.
+
+.. code-block:: bash
+
+ host$ scp linux-image-5.10.168-ti-r62_1xross_armhf.deb bone:.
+
+You might have to use debian@192.168.7.2 for bone if you haven't set everything up.
+
+Now ssh to the bone.
+
+.. code-block:: bash
+
+ host$ ssh bone
+ bone$ ls -sh
+ bin exercises linux-image-5.10.168-ti-r62_1xross_armhf.deb
+
+Now install it.
+
+.. code-block:: bash
+
+ bone$ sudo dpkg --install linux-image-5.10.168-ti-r62_1xross_armhf.deb
+
+Wait a while. (Mine took almore 2 minutes.) Once done check /boot.
+
+.. code-block:: bash
+
+ bone$ ls -sh /boot
+ total 40M
+ 160K config-4.19.94-ti-r50 4.0K SOC.sh 4.0K uEnv.txt.orig
+ 180K config-5.10.168-ti-r62 3.5M System.map-4.19.94-ti-r50 9.7M vmlinuz-4.19.94-ti-r50
+ 4.0K dtbs 4.1M System.map-5.10.168-ti-r62 8.6M vmlinuz-5.10.168-ti-r62
+ 6.4M initrd.img-4.19.94-ti-r50 4.0K uboot
+ 6.8M initrd.img-5.10.168-ti-r62 4.0K uEnv.txt
+
+You see the new kernel files along with the old files. Check uEnv.txt.
+
+.. code-block:: bash
+
+ bone$ head /boot/uEnv.txt
+ #Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0
+ # uname_r=4.19.94-ti-r50
+ uname_r=5.10.168-ti-r62
+
+I added the commented out uname_r line to make it easy to switch between versions of the kernel.
+
+Reboot and test out the new kernel.
+
+.. code-block:: bash
+
+ bone$ sudo reboot
.. _kernel_using_cross_compiler:
Using the Installed Cross Compiler
===================================
-.. todo
- This should be removed
-
+.. todo
+ This should be removed
+
Problem
--------
@@ -540,12 +594,12 @@ Solution
:ref:`kernel_compiling` installs a cross compiler, but you need to set up a
couple of things so that it can be found. :ref:`kernel_compiling` installed the
-kernel and other tools in a directory called ``ti-linux-kernel-dev``. Run the
+kernel and other tools in a directory called ``ti-linux-kernel-dev``. Run the
following commands to find the path to the cross compiler:
.. code-block:: bash
- host$ cd ti-linux-kernel-dev/dl
+ host$ cd ti-linux-kernel-dev/dl
host$ ls
gcc-linaro-arm-linux-gnueabihf-4.7-2013.04-20130415_linux
gcc-linaro-arm-linux-gnueabihf-4.7-2013.04-20130415_linux.tar.xz
@@ -592,7 +646,7 @@ to the *$PATH* the shell uses to find the commands it runs:
.. code-block:: bash
host$ pwd
- /home/yoder/BeagleBoard/ti-linux-kernel-dev/dl/\
+ /home/yoder/BeagleBoard/ti-linux-kernel-dev/dl/\
gcc-linaro-arm-linux-gnueabihf-4.7-2013.04-20130415_linux/bin
host$ echo $PATH
@@ -608,7 +662,7 @@ to be run. Currently, the cross-development tools are not in the *$PATH*. Let's
host$ export PATH=`pwd`:$PATH
host$ echo $PATH
- /home/yoder/BeagleBoard/ti-linux-kernel-dev/dl/\
+ /home/yoder/BeagleBoard/ti-linux-kernel-dev/dl/\
gcc-linaro-arm-linux-gnueabihf-4.7-2013.04-20130415_linux/bin:\
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:\
/usr/games:/usr/local/games
@@ -662,9 +716,9 @@ The *file* command shows that *a.out* was compiled for an ARM processor.
Applying Patches
=================
-.. todo
- Remove patches?
-
+.. todo
+ Remove patches?
+
Problem
--------
@@ -686,13 +740,13 @@ Solution
Here's how to use it:
- Install the kernel sources (:ref:`kernel_compiling`).
-- Change to the kernel directory (+cd ti-linux-kernel-dev/KERNEL+).
-- Add :ref:`kernel_hello_patch` to a file named ``hello.patch`` in the ``ti-linux-kernel-dev/KERNEL`` directory.
+- Change to the kernel directory (+cd ti-linux-kernel-dev/KERNEL+).
+- Add :ref:`kernel_hello_patch` to a file named ``hello.patch`` in the ``ti-linux-kernel-dev/KERNEL`` directory.
- Run the following commands:
.. code-block:: bash
- host$ cd ti-linux-kernel-dev/KERNEL
+ host$ cd ti-linux-kernel-dev/KERNEL
host$ patch -p1 < hello.patch
patching file hello/Makefile
patching file hello/hello.c
@@ -728,7 +782,7 @@ Before making your changes, check out a new branch:
.. code-block:: bash
- host$ cd ti-linux-kernel-dev/KERNEL
+ host$ cd ti-linux-kernel-dev/KERNEL
host$ git status
# On branch master
nothing to commit (working directory clean)
@@ -749,7 +803,7 @@ to the kernel you want. I did some work with a simple character driver that we c
.. code-block:: bash
- host$ cd ti-linux-kernel-dev/KERNEL/drivers/char/
+ host$ cd ti-linux-kernel-dev/KERNEL/drivers/char/
host$ git status
# On branch hello1
# Changes not staged for commit: