Some 'igor -z' improvements.
Approved by: gjb (mentor)
This commit is contained in:
parent
95c5268076
commit
83e3a618a7
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=40921
1 changed files with 4 additions and 4 deletions
|
@ -184,7 +184,7 @@ Timecounter "i8254" frequency 1193182 Hz</screen></para></entry>
|
||||||
time.</para>
|
time.</para>
|
||||||
|
|
||||||
<para>As mentioned previously, the <literal>INT 0x19</literal>
|
<para>As mentioned previously, the <literal>INT 0x19</literal>
|
||||||
instruction loads an MBR, i.e. the <filename>boot0</filename>
|
instruction loads an MBR, i.e., the <filename>boot0</filename>
|
||||||
content, into the memory at address 0x7c00. Taking a look at
|
content, into the memory at address 0x7c00. Taking a look at
|
||||||
the file <filename>sys/boot/i386/boot0/boot0.S</filename> can
|
the file <filename>sys/boot/i386/boot0/boot0.S</filename> can
|
||||||
give a guess at what is happening there - this is the boot
|
give a guess at what is happening there - this is the boot
|
||||||
|
@ -317,7 +317,7 @@ boot2: boot2.ldr boot2.bin ${BTX}/btx/btx
|
||||||
link the binary. BTX, which stands for BooT eXtender, is a
|
link the binary. BTX, which stands for BooT eXtender, is a
|
||||||
piece of code that provides a protected mode environment for the
|
piece of code that provides a protected mode environment for the
|
||||||
program, called the client, that it is linked with. So
|
program, called the client, that it is linked with. So
|
||||||
<literal>boot2</literal> is a BTX client, i.e. it uses the
|
<literal>boot2</literal> is a BTX client, i.e., it uses the
|
||||||
service provided by BTX.</para>
|
service provided by BTX.</para>
|
||||||
|
|
||||||
<indexterm><primary>linker</primary></indexterm>
|
<indexterm><primary>linker</primary></indexterm>
|
||||||
|
@ -707,7 +707,7 @@ begin:</programlisting>
|
||||||
at a 4Gb boundary. Therefore, the instruction's linear
|
at a 4Gb boundary. Therefore, the instruction's linear
|
||||||
virtual address for this example would just be the value of
|
virtual address for this example would just be the value of
|
||||||
EIP. Segment registers such as CS, DS etc are the selectors,
|
EIP. Segment registers such as CS, DS etc are the selectors,
|
||||||
i.e. indexes, into GDT (to be more precise, an index is not a
|
i.e., indexes, into GDT (to be more precise, an index is not a
|
||||||
selector itself, but the INDEX field of a selector). FreeBSD's
|
selector itself, but the INDEX field of a selector). FreeBSD's
|
||||||
GDT holds descriptors for 15 selectors per CPU:</para>
|
GDT holds descriptors for 15 selectors per CPU:</para>
|
||||||
|
|
||||||
|
@ -918,7 +918,7 @@ __asm(".previous");</programlisting>
|
||||||
<literal>__asm</literal> is. The third
|
<literal>__asm</literal> is. The third
|
||||||
<literal>__asm</literal> instruction marks the end of a
|
<literal>__asm</literal> instruction marks the end of a
|
||||||
section. If a directive with the same section name occurred
|
section. If a directive with the same section name occurred
|
||||||
before, the content, i.e. the 32-bit value, will be appended
|
before, the content, i.e., the 32-bit value, will be appended
|
||||||
to the existing section, so forming an array of 32-bit
|
to the existing section, so forming an array of 32-bit
|
||||||
pointers.</para>
|
pointers.</para>
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue