Lines Matching refs:loader
69 Every operating system ever created tends to have its own boot loader.
84 boot loader and a operating system, such that any complying boot loader
130 interpretation of specific file systems (e.g. the BSD/Mach boot loader),
150 how this configuration information is obtained by the boot loader, it
151 should provide a standard means for the boot loader to pass such
166 loader, that is probably appropriate, because all the memory consumed
167 by the boot loader will typically be made available again after the
171 switching code generally needs to be in the boot loader anyway in order
183 boot loader effectively becomes operating system specific again.
187 (*note OS image format::), which allows the boot loader to load the
207 system and user if the boot loader can load these additional modules
211 loader to indicate to the operating system what auxiliary boot modules
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
236 "boot loader"
238 operating system to be run on the machine. The boot loader may
241 of the boot loader -- the stage that eventually transfers control
243 document in order to be "Multiboot-compliant"; earlier boot loader
247 The initial binary image that a boot loader loads into memory and
252 Other auxiliary files that a boot loader loads into memory along
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.
287 2. The state of a machine when a boot loader starts an operating
290 3. The format of information passed by a boot loader to an operating
365 requires of an boot loader. Bits 0-15 indicate requirements; if the
366 boot loader sees any of these bits set but doesn't understand the
370 are set but the boot loader doesn't understand them, it may simply
385 the boot loader is capable of passing a memory map (the `mmap_*'
393 8-24 in the Multiboot header are valid, and the boot loader should
437 this field is zero, the boot loader assumes that the text and data
442 boot loader initializes this area to zero, and reserves the memory
445 boot loader assumes that no bss segment is present.
448 The physical address to which the boot loader should jump in order
459 the OS image. If the mode exists, the boot loader should set it, when
460 the user doesn't specify a mode explicitly. Otherwise, the boot loader
468 the boot loader may set a text mode, even if this field contains
492 When the boot loader invokes the 32-bit operating system, the machine
498 Multiboot-compliant boot loader (e.g. as opposed to another type of
499 boot loader that the operating system can also be loaded from).
503 information structure provided by the boot loader (*note Boot
545 However, other machine state should be left by the boot loader in
547 that's what the boot loader runs from). In other words, the operating
550 so. Also, the boot loader must leave the PIC programmed with the normal
564 which the boot loader communicates vital information to the operating
566 structure as it chooses; all information passed by the boot loader is
570 may be placed anywhere in memory by the boot loader (with the exception
616 bits must be set to zero by the boot loader. Any set bits that the
631 valid, and indicates which BIOS disk device the boot loader loaded the
662 hierarchical in nature. For example, if the boot loader boots from the
698 to 0 by the boot loader and ignored by the operating system.
801 `drive_mode' field represents the access mode used by the boot loader.
828 valid, and contains the physical address of the name of a boot loader
890 loader writers.
897 * Example boot loader code::
926 information. The interface here is meant to allow a boot loader to work
1013 File: multiboot.info, Node: Example OS code, Next: Example boot loader code, Prev: BIOS device m…
1021 Multiboot-compliant boot loader and for reference to how to implement a
1029 Multiboot-compliant boot loader loads and execute it, it initialize the
1034 `cmain', which checks if the magic number passed by the boot loader is
1084 /* The magic number passed by a Multiboot-compliant boot loader. */
1330 /* Am I booted by a Multiboot-compliant boot loader? */
1569 File: multiboot.info, Node: Example boot loader code, Prev: Example OS code, Up: Examples
1571 4.4 Example boot loader code
1575 Multiboot-compliant boot loader, supporting all required and optional
1596 a boot loader, APM information, and graphics information are
1658 Node: Example boot loader code60444