re-design the graphics table in the Multiboot spec.

diff --git a/ChangeLog b/ChangeLog
index d27851c83d04e234cc55555de9f8e7e04276302e..2a0a1860953d73c6bf01d87dec3cec8e55051446 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2000-10-23  OKUJI Yoshinori  <okuji@gnu.org>
+
+       * docs/multiboot.texi: Upgraded to 0.6.92.
+       (Boot information format): Re-designed the graphics table.
+       
 2000-10-22  OKUJI Yoshinori  <okuji@gnu.org>
 
        * docs/tutorial.texi: Miscellaneous updates.

diff --git a/docs/multiboot.texi b/docs/multiboot.texi
index 90fa85177426fd3f1ee1cd473af6e6a316e1fbb4..596c5373c0a5bb65767b2e57a881a7e99733559b 100644 (file)
--- a/docs/multiboot.texi
+++ b/docs/multiboot.texi
@@ -71,7 +71,7 @@ into another language, under the above conditions for modified versions.
 @top Multiboot Specification
 
 This file documents Multiboot Specification, the proposal for the boot
-sequence standard. This edition documents version 0.6.91.
+sequence standard. This edition documents version 0.6.92.
 @end ifnottex
 
 
@@ -576,7 +576,12 @@ follows:
         +-------------------+
 68      | apm_table         |    (present if flags[10] is set)
         +-------------------+
-?? - ?? | graphics_table    |    (present if flags[11] is set)
+72      | vbe_control_info  |    (present if flags[11] is set)
+76      | vbe_mode_info     |
+80      | vbe_mode          |
+82      | vbe_interface_seg |
+84      | vbe_interface_off |
+86      | vbe_interface_len |
         +-------------------+
 @end group
 @end example
@@ -859,36 +864,30 @@ bytes, and the others are 2 bytes. See
 @uref{http://www.microsoft.com/hwdev/busbios/amp_12.htm, Advanced Power
 Management (APM) BIOS Interface Specification}, for more information.
 
-If bit 11 in the @samp{flags} is set, video mode information is
-available in the mode table. This should only be done if the kernel has
-indicated in the @samp{Multiboot Header} that it accepts graphics modes.
+If bit 11 in the @samp{flags} is set, the graphics table is available.
+This must only be done if the kernel has indicated in the
+@samp{Multiboot Header} that it accepts a graphics mode.
 
-The mode table looks like this:
+The fields @samp{vbe_control_info} and @samp{vbe_mode_info} contain
+the physical addresses of @sc{vbe} control information returned by the
+@sc{vbe} Function 00h and @sc{vbe} mode information returned by the
+@sc{vbe} Function 01h, respectively.
 
-@example
-@group
-
-        +----------------------+
-0       | mode_type            |
-4       | width                |
-8       | height               |
-12      | depth                |
-16      | frame_buffer_address |
-        +----------------------+
-
-@end group
-@end example
+The field @samp{vbe_mode} indicates current video mode in the format
+specified in @sc{vbe} 3.0.
 
-Valid numbers for @samp{mode_type} is 0 for linear graphics mode and 1
-for EGA-standard text mode. Everything else is reserved for future
-expansion.
+The rest fields @samp{vbe_interface_seg}, @samp{vbe_interface_off}, and
+@samp{vbe_interface_len} contain the table of a protected mode interface
+defined in @sc{vbe} 2.0+. If this information is not available, those
+fields contain zero. Note that @sc{vbe} 3.0 defines another protected
+mode interface which is incompatible with the old one. If you want to
+use the new protected mode interface, you will have to find the table
+yourself.
 
-@samp{width} and @samp{height} is specified in pixels, if graphics mode,
-or characters in EGA text mode. @samp{depth} is given in bits per pixel
-for graphics, or unused for EGA text mode.
+The fields for the graphics table are designed for @sc{vbe}, but
+Multiboot boot loaders may simulate @sc{vbe} on non-@sc{vbe} modes, as
+if they were @sc{vbe} modes.
 
-@samp{frame_buffer_address} specifies the physical start address of the
-linear frame buffer. This is valid for both graphics and text modes.
 
 @node Examples
 @chapter Examples