* doc/multiboot.texi: Clarify command line format.

diff --git a/ChangeLog b/ChangeLog
index 1cb200f9bfcbc4dd9e3245f95031bb578c3e6d24..1793e5a6f6ebcd00e76b4d05697b7c0dde2167d1 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+2010-09-13  Vladimir Serbinenko  <phcoder@gmail.com>
+
+       * doc/multiboot.texi: Clarify command line format.
+
 2010-09-03  Vladimir Serbinenko  <phcoder@gmail.com>
 
        Reimport mbchk.

diff --git a/doc/multiboot.texi b/doc/multiboot.texi
index 11e8b8c5dd265029531c340f393aa67217c79464..fe70fd532def06e6ca0f71dc4e292acdf9923e3b 100644 (file)
--- 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