From 6ae974e435c729baeddbe4be52b5bcd9025ddb98 Mon Sep 17 00:00:00 2001 From: Vladimir 'phcoder' Serbinenko Date: Mon, 13 Sep 2010 13:44:34 +0200 Subject: [PATCH] * doc/multiboot.texi: Clarify command line format. --- ChangeLog | 4 ++++ doc/multiboot.texi | 6 +++++- 2 files changed, 9 insertions(+), 1 deletion(-) diff --git a/ChangeLog b/ChangeLog index 1cb200f9b..1793e5a6f 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,7 @@ +2010-09-13 Vladimir Serbinenko + + * doc/multiboot.texi: Clarify command line format. + 2010-09-03 Vladimir Serbinenko Reimport mbchk. diff --git a/doc/multiboot.texi b/doc/multiboot.texi index 11e8b8c5d..fe70fd532 100644 --- a/doc/multiboot.texi +++ b/doc/multiboot.texi @@ -708,7 +708,11 @@ partition on a disk partitioned in conventional DOS style, then If bit 2 of the @samp{flags} longword is set, the @samp{cmdline} field is valid, and contains the physical address of the command line to be passed to the kernel. The command line is a normal C-style -zero-terminated string. +zero-terminated string. The exact format of command line is left to +OS developpers. General-purpose boot loaders should allow user a complete +control on command line independently of other factors like image name. +Boot loaders with specific payload in mind may completely or partially generate +it algorithmically. If bit 3 of the @samp{flags} is set, then the @samp{mods} fields indicate to the kernel what boot modules were loaded along with the -- 2.47.2