From mboxrd@z Thu Jan 1 00:00:00 1970 From: mazen.e Date: Tue, 27 May 2014 04:46:58 -0700 (PDT) Subject: [U-Boot] Statically allocate a range of physical memory to an OS image. In-Reply-To: <20140527104820.6CE0A3801AC@gemini.denx.de> References: <1401177091915-180825.post@n7.nabble.com> <20140527104820.6CE0A3801AC@gemini.denx.de> Message-ID: <1401191218533-180832.post@n7.nabble.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Great, many thanks for this information. On the other hand, according to my basic understanding (Please correct me if I am wrong), U-boot can pass through the bootargs env variable information about available memory in the platform. For instance, bootargs mem=512M at 0xA0000000 .. instructs the kernel that the available memory is 512 MB starting @ 0xA0000000, in such case the rest of the platform memory is not even visible to the kernel and its MMU. Is this conclusion true? Thank you very much. -- View this message in context: http://u-boot.10912.n7.nabble.com/Statically-allocate-a-range-of-physical-memory-to-an-OS-image-tp180825p180832.html Sent from the U-Boot mailing list archive at Nabble.com.