Skip to contentSkip to conversation

Document 'bootm_low' and 'bootm_size' environment variables

PATCH New Bartlomiej Sieka 3 participants 4 messages Apr 9, 2008 – Apr 18, 2008

lore
Share & tools
lore

Bartlomiej Sieka

author
#0 lore raw

PATCH 1/1 Document 'bootm_low' and 'bootm_size' environment variables

Signed-off-by Bartlomiej Sieka <[email protected]>

---
Kumar, this patch pertains to your commit "[new uImage] Provide ability to restrict region used for boot images", id d3f2fa0d -- could you review and confirm that the documentation is OK? Thanks.

 README |   19 ++++++++++++++++++-
 1 files changed, 18 insertions(+), 1 deletions(-)
README +18 -1
index 5d059e7..a0dfe73 100644
@@ -1995,7 +1995,10 @@ Configuration Settings:
 		Maximum size of memory mapped by the startup code of
 		the Linux kernel; all data that must be processed by
 		the Linux kernel (bd_info, boot arguments, eventually
-		initrd image) must be put below this limit.
+		initrd image) must be put below this limit, unless
+		"bootm_low" enviroment variable is defined and non-zero.
+		In such case all data for the Linux kernel must be
+		between "bootm_low" and "bootm_low" + CFG_BOOTMAPSZ.
 
 - CFG_MAX_FLASH_BANKS:
 		Max number of Flash memory banks

@@ -2733,6 +2736,20 @@ Some configuration options can be set using Environment Variables:
 
   bootfile	- Name of the image to load with TFTP
 
+  bootm_low	- Memory range available for image processing in the bootm
+		  command can be restricted. This variable is given as
+		  a hexadecimal number and defines lowest address allowed
+		  for use by the bootm command. See also "bootm_size"
+		  environment variable. Address defined by "bootm_low" is
+		  also the base of the initial memory mapping for the Linux
+		  kernel -- see the descripton of CFG_BOOTMAPSZ.
+
+  bootm_size	- Memory range available for image processing in the bootm
+		  command can be restricted. This variable is given as
+		  a hexadecimal number and defines the size of the region
+		  allowed for use by the bootm command. See also "bootm_low"
+		  environment variable.
+
   autoload	- if set to "no" (any string beginning with 'n'),
 		  "bootp" will just load perform a lookup of the
 		  configuration from the BOOTP server, but not try to
#1 lore raw

PATCH 1/1 Document 'bootm_low' and 'bootm_size' environment variables

Quoted 15 lines · Bartlomiej Sieka
Signed-off-by Bartlomiej Sieka <[email protected]>

---
Kumar, this patch pertains to your commit "[new uImage] Provide ability to
restrict region used for boot images", id d3f2fa0d -- could you review and confirm that the documentation is OK? Thanks.

README | 19 ++++++++++++++++++-

1 files changed, 18 insertions(+), 1 deletions(-)
README +0 -0
index 5d059e7..a0dfe73 100644

README Configuration Settings: · line 2001

Quoted 8 lines
README +4 -1
@@ -1995,7 +1995,10 @@ Configuration Settings:
 		Maximum size of memory mapped by the startup code of
 		the Linux kernel; all data that must be processed by
 		the Linux kernel (bd_info, boot arguments, eventually
-		initrd image) must be put below this limit.
+		initrd image) must be put below this limit, unless
+		"bootm_low" enviroment variable is defined and non-zero.
+		In such case all data for the Linux kernel must be
+		between "bootm_low" and "bootm_low" + CFG_BOOTMAPSZ.

all data seems misleading since initrd doesn't have to be within CFG_BOOTMAPSZ.

Quoted 20 lines
README +0 -1
- CFG_MAX_FLASH_BANKS:
 		Max number of Flash memory banks

@@ -2733,6 +2736,20 @@ Some configuration options can be set using

Environment Variables:

bootfile - Name of the image to load with TFTP

+ bootm_low - Memory range available for image processing in the
bootm

README +8 -0
+		  command can be restricted. This variable is given as
+		  a hexadecimal number and defines lowest address allowed
+		  for use by the bootm command. See also "bootm_size"
+		  environment variable. Address defined by "bootm_low" is
+		  also the base of the initial memory mapping for the Linux
+		  kernel -- see the descripton of CFG_BOOTMAPSZ.
 
 
+
+  bootm_size	- Memory range available for image processing in the

bootm

README Some configuration options can be set using Environment Variables: · line 2752

Quoted 5 lines
README +5 -0
+		  command can be restricted. This variable is given as
+		  a hexadecimal number and defines the size of the region
+		  allowed for use by the bootm command. See also "bootm_low"
+		  environment variable.
+

these look fine.

- k

author
#2 lore raw

PATCH 1/1 Boot-related documentation update

- document 'bootm_low' and 'bootm_size' environment variables
- update inaccurate CFG_BOOTMAPSZ entry

Signed-off-by Bartlomiej Sieka <[email protected]>

---
Addressed comment by Kumar, changed patch description accordingly.

 README |   21 +++++++++++++++++++--
 1 files changed, 19 insertions(+), 2 deletions(-)
README +19 -2
index 5d059e7..63b1417 100644
@@ -1994,8 +1994,11 @@ Configuration Settings:
 - CFG_BOOTMAPSZ:
 		Maximum size of memory mapped by the startup code of
 		the Linux kernel; all data that must be processed by
-		the Linux kernel (bd_info, boot arguments, eventually
-		initrd image) must be put below this limit.
+		the Linux kernel (bd_info, boot arguments, FDT blob if
+		used) must be put below this limit, unless "bootm_low"
+		enviroment variable is defined and non-zero. In such case
+		all data for the Linux kernel must be between "bootm_low"
+		and "bootm_low" + CFG_BOOTMAPSZ.
 
 - CFG_MAX_FLASH_BANKS:
 		Max number of Flash memory banks

@@ -2733,6 +2736,20 @@ Some configuration options can be set using Environment Variables:
 
   bootfile	- Name of the image to load with TFTP
 
+  bootm_low	- Memory range available for image processing in the bootm
+		  command can be restricted. This variable is given as
+		  a hexadecimal number and defines lowest address allowed
+		  for use by the bootm command. See also "bootm_size"
+		  environment variable. Address defined by "bootm_low" is
+		  also the base of the initial memory mapping for the Linux
+		  kernel -- see the descripton of CFG_BOOTMAPSZ.
+
+  bootm_size	- Memory range available for image processing in the bootm
+		  command can be restricted. This variable is given as
+		  a hexadecimal number and defines the size of the region
+		  allowed for use by the bootm command. See also "bootm_low"
+		  environment variable.
+
   autoload	- if set to "no" (any string beginning with 'n'),
 		  "bootp" will just load perform a lookup of the
 		  configuration from the BOOTP server, but not try to
Applied
#3 lore raw

PATCH 1/1 Boot-related documentation update

Quoted 9 lines · In message <[email protected]> you wrote:

- document 'bootm_low' and 'bootm_size' environment variables
- update inaccurate CFG_BOOTMAPSZ entry

Signed-off-by Bartlomiej Sieka <[email protected]>

---
Addressed comment by Kumar, changed patch description accordingly.

 README |   21 +++++++++++++++++++--
 1 files changed, 19 insertions(+), 2 deletions(-)

Applied, thanks.

Best regards,

Wolfgang Denk

Signature · 7 lines
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
It [being a Vulcan] means to adopt a philosophy, a way of life  which
is logical and beneficial. We cannot disregard that philosophy merely
for personal gain, no matter how important that gain might be.
	-- Spock, "Journey to Babel", stardate 3842.4