From e90afd56575c79460a6ca0dda100a8f5bf0a564a Mon Sep 17 00:00:00 2001 From: Michal Soltys Date: Tue, 10 May 2011 13:45:09 +0200 Subject: [PATCH] com32/chain: minor doc fix Signed-off-by: Michal Soltys --- doc/chain.txt | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/doc/chain.txt b/doc/chain.txt index f7826d4..68238a0 100644 --- a/doc/chain.txt +++ b/doc/chain.txt @@ -105,9 +105,9 @@ options 'sect=' and 'seg='), the file will cause sector to not be loaded at all seg=:: *seg=0:0x7c00:0x7c00 -This triplet lets you alter the addresses a file will use. Loading is done to -, jumping to . When you chainload some other -bootloader or kernel, it's almost always mandatory. +This triplet lets you alter the addresses a file will use. It's loaded at +, the entry point is at . When you chainload some +other bootloader or kernel, it's almost always mandatory. The defaults, if option is not specified, are 0:0x7c00:0x7c00 If any of the fields are ommited (e.g. 0x2000::), they default to 0. @@ -117,10 +117,10 @@ If any of the fields are ommited (e.g. 0x2000::), they default to 0. *sect=0:0x7c00:0x7c00 nosect sets: nomaps -This triplet lets you alter the addresses a sector will use. File is loaded at -, the jump is made to . This option is mostly used -in tandem with 'file=' and 'seg=' options, as some loaders/kernels will expect -relocated sector at some particular address (e.g. DRKM). +This triplet lets you alter the addresses a sector will use. It's loaded at +, the entry point is at . This option is mostly +used in tandem with 'file=' and 'seg=' options, as some loaders/kernels will +expect relocated sector at some particular address (e.g. DRKM). 'nosect' will cause sector to not be loaded at all. In plenty cases, when a file is being chainloaded, sector is not necessary. -- 2.7.4