Lines Matching refs:OS
124 It should be possible to write compliant boot loaders that load the OS
129 relevant OS image and boot module data on disk, such as by
132 "boot partition" (e.g. OS/2), or even loading from within another
157 1.6 How to make OS development easier
160 OS images should be easy to generate. Ideally, an OS image should simply
163 disassemble OS images just like normal executables. Specialized tools
164 should not be required to create OS images in a _special_ file format.
168 boot process is created, whereas every bit of code in the OS image
173 operating system to do this makes creation of OS images much more
182 formats in existence in order to load the OS image -- otherwise the
186 Multiboot-compliant OS images always contain a magic "Multiboot header"
187 (*note OS image format::), which allows the boot loader to load the
203 these additional modules could be embedded in the main OS image along
223 We use the term "must", when any boot loader or OS image needs to
224 follow a rule -- otherwise, the boot loader or OS image is _not_
228 We use the term "should", when any boot loader or OS image is
233 We use the term "may", when any boot loader or OS image is allowed
246 "OS image"
248 transfers control to start an operating system. The OS image is
253 with an OS image, but does not interpret in any way other than
257 A boot loader or an OS image which follows the rules defined as
259 rule as "should" or "may", a Multiboot-complaint boot loader/OS
283 There are three main aspects of a boot loader/OS image interface:
285 1. The format of an OS image as seen by a boot loader.
295 * OS image format::
300 File: multiboot.info, Node: OS image format, Next: Machine state, Up: Specification
302 3.1 OS image format
305 An OS image may be an ordinary 32-bit executable file in the standard
311 An OS image must contain an additional header called "Multiboot
312 header", besides the headers of the format used by the OS image. The
314 bytes of the OS image, and must be longword (32-bit) aligned. In
326 File: multiboot.info, Node: Header layout, Next: Header magic fields, Up: OS image format
354 …Node: Header magic fields, Next: Header address fields, Prev: Header layout, Up: OS image format
364 The field `flags' specifies features that the OS image requests or
368 reason, it must notify the user and fail to load the OS image.
372 bits in the `flags' word must be set to zero in OS images. This
395 calculate where to load the OS image. This information does not
410 …der address fields, Next: Header graphics fields, Prev: Header magic fields, Up: OS image format
422 "synchronize" the mapping between OS image offsets and physical
427 segment. The offset in the OS image file at which to start loading
436 OS image; this is true for existing a.out executable formats. If
438 segments occupy the whole OS image file.
452 File: multiboot.info, Node: Header graphics fields, Prev: Header address fields, Up: OS image fo…
459 the OS image. If the mode exists, the boot loader should set it, when
474 indicates that the OS image has no preference.
479 indicates that the OS image has no preference.
483 in a text mode. The value zero indicates that the OS image has no
487 File: multiboot.info, Node: Machine state, Next: Boot information format, Prev: OS image format,…
533 The OS image must create its own stack as soon as it needs one.
537 the `GDTR' may be invalid, so the OS image must not load any
542 The OS image must leave interrupts disabled until it sets up its
560 FIXME: Split this chapter like the chapter "OS image format".
632 OS image from. If the OS image was not loaded from a BIOS disk, then
896 * Example OS code::
932 File: multiboot.info, Node: BIOS device mapping techniques, Next: Example OS code, Prev: Notes o…
1013 File: multiboot.info, Node: Example OS code, Next: Example boot loader code, Prev: BIOS device m…
1015 4.3 Example OS code
1048 File: multiboot.info, Node: multiboot.h, Next: boot.S, Up: Example OS code
1176 File: multiboot.info, Node: boot.S, Next: kernel.c, Prev: multiboot.h, Up: Example OS code
1264 …ultiboot.info, Node: kernel.c, Next: Other Multiboot kernels, Prev: boot.S, Up: Example OS code
1557 File: multiboot.info, Node: Other Multiboot kernels, Prev: kernel.c, Up: Example OS code
1569 File: multiboot.info, Node: Example boot loader code, Prev: Example OS code, Up: Examples
1641 Node: OS image format12418
1653 Node: Example OS code43296