Merging xloader, bootloader and boot environment variables partitions into a single partition on NAND

[Elvis Dowson]

Hi,
  I was wondering what the merits and demerits are of having a single 
integrated xloader+bootloader+boot environment variables in a single partition 
in NAND, as opposed to having multiple partitions that hold xloader, bootloader 
and the uboot environment in separate partitions?

Elvis Dowson

--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

RE: Merging xloader, bootloader and boot environment variables partitions into a single partition on NAND

[Ghorai, Sukumar]

 -Original Message-
 From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
 ow...@vger.kernel.org] On Behalf Of Elvis Dowson
 Sent: Thursday, January 20, 2011 10:51 PM
 To: linux-omap Mailing List
 Subject: Merging xloader, bootloader and boot environment variables
 partitions into a single partition on NAND
 
 Hi,
   I was wondering what the merits and demerits are of having a single
 integrated xloader+bootloader+boot environment variables in a single
 partition in NAND, as opposed to having multiple partitions that hold
 xloader, bootloader and the uboot environment in separate partitions?
[Ghorai] This the way we represent or arrange the nand/flash. 
Current design helps to update x-loader, u-boot, saveen or kernel in different 
partition(s) from user-space without remember the offset.

 
 Elvis Dowson
 
 --
 To unsubscribe from this list: send the line unsubscribe linux-omap in
 the body of a message to majord...@vger.kernel.org
 More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html