Changeset c093e6b for chapter10/kernel.xml

Timestamp:

10/01/2022 10:30:12 PM (19 months ago)

Author:

Thomas Trepl (Moody) <thomas@…>

Branches:

multilib

Children:

f3b2f16

Parents:

f29824e (diff), 4349661 (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the (diff) links above to see all the changes relative to each parent.

Message:

Automatic merge of trunk into multilib

File:

• chapter10/kernel.xml (modified) (4 diffs)

chapter10/kernel.xml

@@ -118 +118 @@
   Graphics support --->
    Frame buffer Devices --->
-      [*] Support for frame buffer devices ----
+      <*> Support for frame buffer devices --->
+   Console display driver support --->
+      [*] Framebuffer Console support [CONFIG_FRAMEBUFFER_CONSOLE]
   Generic Driver Options  --->
    [ ] Support for uevent helper [CONFIG_UEVENT_HELPER]
@@ -157 +159 @@
    Frame buffer Devices --->
       <*> Support for frame buffer devices --->
+   Console display driver support --->
+      [*] Framebuffer Console support [CONFIG_FRAMEBUFFER_CONSOLE]
 File systems  --->
    [*] Inotify support for userspace [CONFIG_INOTIFY_USER]
@@ -303 +307 @@
 
       <varlistentry>
+        <term><parameter>Framebuffer Console support</parameter></term>
+        <listitem>
+          <para>This is needed to display the Linux console on a frame
+          buffer device.  To allow the kernel to print debug messages at an
+          early boot stage, it shouldn't be built as a kernel module
+          unless an initramfs will be used. And, if
+          <option>CONFIG_DRM</option> (Direct Rendering Manager) is enabled,
+          it's likely <option>CONFIG_DRM_FBDEV_EMULATION</option> (Enable
+          legacy fbdev support for your modesetting driver) should be
+          enabled as well.</para>
+        </listitem>
+      </varlistentry>
+
+      <varlistentry>
         <term><parameter>Support x2apic</parameter></term>
         <listitem>
@@ -350 +368 @@
 
     <caution>
-      <para>If the host system has a separate /boot partition, the files copied
-      below should go there. The easiest way to do that is to bind /boot on the
-      host (outside chroot) to /mnt/lfs/boot before proceeding.  As the
-      &root; user in the <emphasis>host system</emphasis>:</para>
-
-<screen role="nodump"><userinput>mount --bind /boot /mnt/lfs/boot</userinput></screen>
+      <para>If you've decided to use a separate &boot-dir; partition for the
+      LFS system (maybe sharing a &boot-dir; partition with the host
+      distro) , the files copied below should go there. The easiest way to
+      do that is to create the entry for &boot-dir; in &fstab; first (read
+      the previous section for details), then issue the following command
+      as the &root; user in the
+      <emphasis>chroot environment</emphasis>:</para>
+
+<screen role="nodump"><userinput>mount /boot</userinput></screen>
+
+      <para>The path to the device node is omitted in the command because
+      <command>mount</command> can read it from &fstab;.</para>
     </caution>