Using Linux Kernel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 4.1.1 non-interactive configuration . . . . . . . . . . . . . . . . . . . . . . 30 4.1.2 using kernel modules . . . . . . . . . . . . . . . . . . . . . . . . . . 31 4.1.3 using kernel features . . . . . . . . . . . . . . . . . . . . . . . . . . 32 4.1.4 Create new development branch . . . . . . . . . . . . . . 11 Running any make goals . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 4.12 Speed up kernel development . . . . . . . . . . . . . . . . . . . . . . . . . 45 4.12.1 Speed up compiling and save

Using Linux Kernel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 4.1.1 non-interactive configuration . . . . . . . . . . . . . . . . . . . . . . 30 4.1.2 using kernel modules . . . . . . . . . . . . . . . . . . . . . . . . . . 31 4.1.3 using kernel features . . . . . . . . . . . . . . . . . . . . . . . . . . 32 4.1.4 Create new development branch . . . . . . . . . . . . . . 11 Running any make goals . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 4.12 Speed up kernel development . . . . . . . . . . . . . . . . . . . . . . . . . 45 4.12.1 Speed up compiling and save

Using Linux Kernel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 4.1.1 non-interactive configuration . . . . . . . . . . . . . . . . . . . . . . 30 4.1.2 using kernel modules . . . . . . . . . . . . . . . . . . . . . . . . . . 31 4.1.3 using kernel features . . . . . . . . . . . . . . . . . . . . . . . . . . 32 4.1.4 Create new development branch . . . . . . . . . . . . . . time, prepare the configs . . . . . . . . . . . . . . . . . . . . . 47 5.6 Choose the versions of kernel, rootfs and U-Boot . . . . . . . . . . . . . . 48 5.7 Configure, build and boot them . . . . .

notebook has exactly one interactive session connected to a kernel, which will execute code sent by the user and communicate back results. This kernel remains active if the web browser window is closed, and the web application to the same kernel. In the dashboard, notebooks with an active kernel have a Shutdown button next to them, whereas notebooks without an active kernel have a Delete button in its place Other clients may connect to the same kernel. When each kernel is started, the notebook server prints to the terminal a message like this: [NotebookApp] Kernel started: 87f7d2c0-13e3-43df-8bb8-1bd37aaf3373

notebook has exactly one interactive session connected to a kernel, which will execute code sent by the user and communicate back results. This kernel remains active if the web browser window is closed, and the web application to the same kernel. In the dashboard, notebooks with an active kernel have a Shutdown button next to them, whereas notebooks without an active kernel have a Delete button in its place Other clients may connect to the same kernel. When each kernel is started, the notebook server prints to the terminal a message like this: [NotebookApp] Kernel started: 87f7d2c0-13e3-43df-8bb8-1bd37aaf3373

notebook has exactly one interactive session connected to a kernel, which will execute code sent by the user and communicate back results. This kernel remains active if the web browser window is closed, and the web application to the same kernel. In the dashboard, notebooks with an active kernel have a Shutdown button next to them, whereas notebooks without an active kernel have a Delete button in its place Other clients may connect to the same kernel. When each kernel is started, the notebook server prints to the terminal a message like this: [NotebookApp] Kernel started: 87f7d2c0-13e3-43df-8bb8-1bd37aaf3373

notebook has exactly one interactive session connected to a kernel, which will execute code sent by the user and communicate back results. This kernel remains active if the web browser window is closed, and the web application to the same kernel. In the dashboard, notebooks with an active kernel have a Shutdown button next to them, whereas notebooks without an active kernel have a Delete button in its place Other clients may connect to the same kernel. When each kernel is started, the notebook server prints to the terminal a message like this: [NotebookApp] Kernel started: 87f7d2c0-13e3-43df-8bb8-1bd37aaf3373

notebook has exactly one interactive session connected to a kernel, which will execute code sent by the user and communicate back results. This kernel remains active if the web browser window is closed, and the web application to the same kernel. In the dashboard, notebooks with an active kernel have a Shutdown button next to them, whereas notebooks without an active kernel have a Delete button in its place Other clients may connect to the same kernel. When each kernel is started, the notebook server prints to the terminal a message like this: [NotebookApp] Kernel started: 87f7d2c0-13e3-43df-8bb8-1bd37aaf3373

notebook has exactly one interactive session connected to a kernel, which will execute code sent by the user and communicate back results. This kernel remains active if the web browser window is closed, and the web application to the same kernel. In the dashboard, notebooks with an active kernel have a Shutdown button next to them, whereas notebooks without an active kernel have a Delete button in its place Other clients may connect to the same kernel. When each kernel is started, the notebook server prints to the terminal a message like this: [NotebookApp] Kernel started: 87f7d2c0-13e3-43df-8bb8-1bd37aaf3373

notebook has exactly one interactive session connected to a kernel, which will execute code sent by the user and communicate back results. This kernel remains active if the web browser window is closed, and the web application to the same kernel. In the dashboard, notebooks with an active kernel have a Shutdown button next to them, whereas notebooks without an active kernel have a Delete button in its place Other clients may connect to the same kernel. When each kernel is started, the notebook server prints to the terminal a message like this: [NotebookApp] Kernel started: 87f7d2c0-13e3-43df-8bb8-1bd37aaf3373