[U-Boot] Segmented RAM, big userspace.

2011-12-13 Thread Sergey Lapin
Hi, all! We have a board, based on s3c2416, with 128MB of RAM and 1GB of NAND flash. RAM is organized as 2 memory banks with far placed bases: TOP UNUSED 64MB 64MB SDRAM --- 128MB segment base 1 - UNUSED 64MB 64MB SDRAM -- 128MB segment base 0 -- BOTTOM So we could have only 64MB

Re: [U-Boot] Segmented RAM, big userspace.

2011-12-13 Thread Wolfgang Denk
Dear Sergey Lapin, In message 20111213160810.ga27...@build.ihdev.net you wrote: We have a board, based on s3c2416, with 128MB of RAM and 1GB of NAND flash. RAM is organized as 2 memory banks with far placed bases: TOP UNUSED 64MB 64MB SDRAM --- 128MB segment base 1 - UNUSED 64MB

Re: [U-Boot] Segmented RAM, big userspace.

2011-12-13 Thread Sergey Lapin
On Tue, Dec 13, 2011 at 05:24:22PM +0100, Wolfgang Denk wrote: Dear Sergey Lapin, In message 20111213160810.ga27...@build.ihdev.net you wrote: We have a board, based on s3c2416, with 128MB of RAM and 1GB of NAND flash. RAM is organized as 2 memory banks with far placed bases: TOP

Re: [U-Boot] Segmented RAM, big userspace.

2011-12-13 Thread Wolfgang Denk
Dear Sergey Lapin, In message 20111213165113.ga27...@build.ihdev.net you wrote: So we could have only 64MB as one piece; Due to u-boot reloaction code we need to have u-boot in first 64MB also. ... Why would that be the case? If we specify memory size as 128MB (gd-ram_size) u-boot

Re: [U-Boot] Segmented RAM, big userspace.

2011-12-13 Thread Scott Wood
On 12/13/2011 10:08 AM, Sergey Lapin wrote: It is possible to flash filesystems in parts, but for this to work these are needed to be properly split. This raises a problem of bad blocks - writing previous piece might end not where you expect it to end, but a few blocks later. Hand-handling