From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Schwierzeck Date: Wed, 6 Jul 2016 16:49:02 +0200 Subject: [U-Boot] [PATCH] test/py: support 'memstart =' in u_boot_utils.find_ram_base() In-Reply-To: <577D17AA.5030308@wwwdotorg.org> References: <20160706104422.22359-1-daniel.schwierzeck@gmail.com> <577D17AA.5030308@wwwdotorg.org> Message-ID: <577D1A5E.4020306@gmail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Am 06.07.2016 um 16:37 schrieb Stephen Warren: > On 07/06/2016 04:44 AM, Daniel Schwierzeck wrote: >> Some archs like MIPS or PPC have a different 'bdinfo' output >> than ARM regarding the memory configuration. Also support >> 'memstart = 0x*' in u_boot_utils.find_ram_base() to make >> all tests requiring the RAM base working on those archs. > > Acked-by: Stephen Warren > > ... although wouldn't it be better to fix the bdinfo command so that it > printed the same thing on all architectures? yes, but bdinfo isn't the only one affected. Currently we have two variants in "struct bd_info" of how to store the memory configuration: - bi_memstart and bi_memsize - struct bi_dram[CONFIG_NR_DRAM_BANKS] if a board or arch defines CONFIG_NR_DRAM_BANKS Maybe we could unify this one day. But this requires changes to other commands and generic board init. Until then test/py should support both variants. -- - Daniel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: