@ifinfo
Copyright @copyright{} 1995, 96 Bryan Ford <baford@@cs.utah.edu>
Copyright @copyright{} 1995, 96 Erich Stefan Boleyn <erich@@uruk.org>
-Copyright @copyright{} 1999, 2000 Free Software Foundation, Inc.
+Copyright @copyright{} 1999, 2000, 2001, 2002 Free Software Foundation, Inc.
Permission is granted to make and distribute verbatim copies of
this manual provided the copyright notice and this permission notice
@titlepage
@sp 10
@title The Multiboot Specification
-@author OKUJI Yoshinori, Bryan Ford, Erich Stefan Boleyn, Kunihiro Ishiguro
+@author Yoshinori K. Okuji, Bryan Ford, Erich Stefan Boleyn, Kunihiro Ishiguro
@page
@vskip 0pt plus 1filll
Copyright @copyright{} 1995, 96 Bryan Ford <baford@@cs.utah.edu>
Copyright @copyright{} 1995, 96 Erich Stefan Boleyn <erich@@uruk.org>
-Copyright @copyright{} 1999, 2000, 2001 Free Software Foundation, Inc.
+Copyright @copyright{} 1999, 2000, 2001, 2002 Free Software Foundation, Inc.
Permission is granted to make and distribute verbatim copies of
this manual provided the copyright notice and this permission notice
@headings double
@ifnottex
-@node Top, Overview, (dir), (dir)
+@node Top
@top Multiboot Specification
This file documents Multiboot Specification, the proposal for the boot
@end menu
-@node Overview, Terminology, Top, Top
+@node Overview
@chapter Introduction to Multiboot Specification
This chapter describes some rough information on the Multiboot
@end menu
-@node Motivation, Architecture, Overview, Overview
+@node Motivation
@section The background of Multiboot Specification
Every operating system ever created tends to have its own boot loader.
only how they must interface with the operating system being loaded.
-@node Architecture, Operating systems, Motivation, Overview
+@node Architecture
@section The target architecture
This specification is primarily targeted at @sc{pc}, since they are the
adopted for them as well.
-@node Operating systems, Boot sources, Architecture, Overview
+@node Operating systems
@section The target operating systems
This specification is targeted toward free 32-bit operating systems
specification as well, but that's probably a pipe dream.
-@node Boot sources, Boot-time configuration, Operating systems, Overview
+@node Boot sources
@section Boot sources
It should be possible to write compliant boot loaders that load the OS
user-friendliness.
-@node Boot-time configuration, Convenience to operating systems, Boot sources, Overview
+@node Boot-time configuration
@section Configure an operating system at boot-time
It is often necessary for one reason or another for the user to be able
information to the operating system.
-@node Convenience to operating systems, Boot modules, Boot-time configuration, Overview
+@node Convenience to operating systems
@section How to make OS development easier
OS images should be easy to generate. Ideally, an OS image should simply
Multiboot-compliant.
-@node Boot modules, , Convenience to operating systems, Overview
+@node Boot modules
@section Boot modules
Many modern operating system kernels, such as those of VSTa and Mach, do
because some operating systems will be unable to boot without them.
-@node Terminology, Specification, Overview, Top
+@node Terminology
@chapter The definitions of terms used through the specification
@table @dfn
@item u16
The type of unsigned 16-bit data. Because the target architecture is
-little-endian, WORD is coded in little-endian.
+little-endian, u16 is coded in little-endian.
@item u32
The type of unsigned 32-bit data. Because the target architecture is
-little-endian, DWORD is coded in little-endian.
+little-endian, u32 is coded in little-endian.
@item u64
The type of unsigned 64-bit data. Because the target architecture is
-little-endian, QWORD is coded in little-endian.
+little-endian, u64 is coded in little-endian.
@end table
-@node Specification, Examples, Terminology, Top
+@node Specification
@chapter The exact definitions of Multiboot Specification
There are three main aspects of a boot loader/OS image interface:
@end menu
-@node OS image format, Machine state, Specification, Specification
+@node OS image format
@section OS image format
An OS image may be an ordinary 32-bit executable file in the standard
@end menu
-@node Header layout, Header magic fields, OS image format, OS image format
+@node Header layout
@subsection The layout of Multiboot header
The layout of the Multiboot header must be as follows:
defind in @ref{Header graphics fields}.
-@node Header magic fields, Header address fields, Header layout, OS image format
+@node Header magic fields
@subsection The magic fields of Multiboot header
@table @samp
@end table
-@node Header address fields, Header graphics fields, Header magic fields, OS image format
+@node Header address fields
@subsection The address fields of Multiboot header
All of the address fields enabled by flag bit 16 are physical addresses.
@end table
-@node Header graphics fields, , Header address fields, OS image format
+@node Header graphics fields
@subsection The graphics fields of Multiboot header
Also, information about a preferred default mode can be specified in the
a kernel to just say it wants a 32-bit resolution, for example.
-@node Machine state, Boot information format, OS image format, Specification
+@node Machine state
@section Machine state
FIXME: Use a table like the chapter ``Header layout''.
changed them during the switch to 32-bit mode.
-@node Boot information format, , Machine state, Specification
+@node Boot information format
@section Boot information format
FIXME: Split this chapter like the chapter ``OS image format''.
if they were @sc{vbe} modes.
-@node Examples, History, Specification, Top
+@node Examples
@chapter Examples
@strong{Caution:} The following items are not part of the specification
@end menu
-@node Notes on PC, BIOS device mapping techniques, Examples, Examples
+@node Notes on PC
@section Notes on PC
In reference to bit 0 of the @samp{flags} parameter in the Multiboot
the operating system as desired.
-@node BIOS device mapping techniques, Example OS code, Notes on PC, Examples
+@node BIOS device mapping techniques
@section BIOS device mapping techniques
Both of these techniques should be usable from any PC operating system,
@end menu
-@node Data comparison technique, I/O restriction technique, BIOS device mapping techniques, BIOS device mapping techniques
+@node Data comparison technique
@subsection Data comparison technique
Before activating @emph{any} of the device drivers, gather enough data
@end enumerate
-@node I/O restriction technique, , Data comparison technique, BIOS device mapping techniques
+@node I/O restriction technique
@subsection I/O restriction technique
This first step may be unnecessary, but first create copy-on-write
logically numbered devices on the controller.
-@node Example OS code, Example boot loader code, BIOS device mapping techniques, Examples
+@node Example OS code
@section Example OS code
In this distribution, the example Multiboot kernel @file{kernel} is
@end menu
-@node multiboot.h, boot.S, Example OS code, Example OS code
+@node multiboot.h
@subsection multiboot.h
This is the source code in the file @file{multiboot.h}:
@end example
-@node boot.S, kernel.c, multiboot.h, Example OS code
+@node boot.S
@subsection boot.S
In the file @file{boot.S}:
@end example
-@node kernel.c, Other Multiboot kernels, boot.S, Example OS code
+@node kernel.c
@subsection kernel.c
And, in the file @file{kernel.c}:
@end example
-@node Other Multiboot kernels, , kernel.c, Example OS code
+@node Other Multiboot kernels
@subsection Other Multiboot kernels
Other useful information should be available in Multiboot kernels, such
library supporting the specification.
-@node Example boot loader code, , Example OS code, Examples
+@node Example boot loader code
@section Example boot loader code
The GNU GRUB (@pxref{Top, , GRUB, grub.info, The GRUB manual}) project
more information.
-@node History, Index, Examples, Top
+@node History
@chapter The change log of this specification
@table @asis
@end table
-@node Index, , History, Top
+@node Index
@unnumbered Index
@printindex cp
projects / thirdparty / grub.git / commitdiff
