Changeset 0ea3431 for chapter10/kernel.xml

Timestamp:

09/26/2022 02:03:23 PM (19 months ago)

Author:

Xi Ruoyao <xry111@…>

Branches:

xry111/clfs-ng

Children:

259794e

Parents:

1f6dfd4 (diff), f427ba23 (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:

Merge remote-tracking branch 'origin/trunk' into xry111/clfs-ng

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]
@@ -271 +275 @@
 
       <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>
@@ -318 +336 @@
 
     <caution>
-      <para>As the cross-built LFS system has a separate /boot partition,
-      the files copied below should go there. The easiest way to do that is
-      to mount <filename class="directory">/boot</filename> before
-      proceeding.  As the &root; user:</para>
+      <para>As the cross-built LFS system has a separate &boot-dir;
+      partition, 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:</para>
 
 <screen role="nodump"><userinput>mount /boot</userinput></screen>