From: Vladimir 'phcoder' Serbinenko Date: Wed, 10 Mar 2010 21:58:13 +0000 (+0100) Subject: merge multiboot into mbtag-spec X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=0dc138c770feb3aa09ff53f7ae71375a0f151c1a;p=thirdparty%2Fgrub.git merge multiboot into mbtag-spec --- 0dc138c770feb3aa09ff53f7ae71375a0f151c1a diff --cc doc/multiboot.texi index 7ba36cded,631897a15..efe9b40f6 --- a/doc/multiboot.texi +++ b/doc/multiboot.texi @@@ -876,12 -813,14 +876,14 @@@ u32 | reserved @end group @end example -where @samp{size} is the size of the associated structure in bytes, which -can be greater than the minimum of 20 bytes. @samp{base_addr} is the -starting address. @samp{length} is the size of the memory region in bytes. +@samp{size} contains the size of current entry including this field itself. It may be bigger than 24 bytes in future versions but is guaranteed to be +@samp{base_addr} is the starting physical address. @samp{length} is the size of the memory region in bytes. @samp{type} is the variety of address range represented, where a - value of 1 indicates available @sc{ram}, and all other values currently + value of 1 indicates available @sc{ram}, value of 3 indicates usable memory + holding ACPI information, value of 4 indicates reserved memory which needs to + be preserved on hibernation and all other values currently indicated a reserved area. +@samp{reserved} is set to @samp{0} by bootloader and must be ignored by the OS image. The map provided is guaranteed to list all standard @sc{ram} that should be available for normal use.