Following abf4f68 - removes all references to the deleted [ORG 0x7c00],
and generally mention that the BIOS copies the boot sector into that
fixed memory location
The old links didn't point to valid locations.
Replace the old links with the new links and test those changes with a
small script: https://github.com/initBasti/markdown_link_check .
______________________________________________________________
In order to find and replace the links, I used the following commands:
grep -rwohP '.' -e "\(https\:\/\/0xax.gitbooks.io\/\S*\)" > links.txt
(Find all links recursivly in the project directories and print out the
only the matches links)
Within links.txt:
Remove the '(' & ')' => :%s/\(//g and :%s/\)//g
Remove duplicates => :sort u
Test if the links work with:
python3 md_link_check.py --pattern 0xax.gitbook --output-file bad.txt
(https://github.com/initBasti/markdown_link_check)
Create replace commands:
:%s/.*/grep -rl & '.' | xargs sed -i 's#&##g'
Enter replacement URL between the 2nd & 3rd '#'
Execute commands: :w !sh
Signed-off-by: Sebastian Fricke <sebastian.fricke.linux@gmail.com>
The btsl not only tests the bit, it tests the bit
by transfering it into the carry flag and then sets
it as well. Otherwise the wrmsr would not make sense.
Signed-off-by: Andreas J. Reichel <webmaster@6th-dimension.com>
This patch fixed half of issue of #645:
1.
"The value assigned to it is an offset relative to the offset of the segment"
-->
"The value assigned to it is an offset relative to the segment"
2.
"adding the address field of the instruction and the value of the program counter"
-->
"adding the address field of the instruction to the value of the program counter"
3.
"PAE mode" --> "PAE", because PAE is not a mode.
4.
"5 bit" --> "the 5th bit"
The use of ax, dx, cx to pass the function arguments is not `fastcall`
convention in GCC, which only uses cx and dx. This calling convention
comes from the GCC -mregparm=3 option.
[1] https://en.wikipedia.org/wiki/X86_calling_conventions
Jan Sonntag