From mboxrd@z Thu Jan 1 00:00:00 1970 From: Timur Tabi Date: Mon, 17 May 2010 09:16:31 -0500 Subject: [U-Boot] libfdt: make fdt_increase_size() available to everyone In-Reply-To: <20100517131650.1060EE6D663@gemini.denx.de> References: <1273526815-1091-1-git-send-email-timur@freescale.com> <1273975868.3244.9.camel@xps> <20100517131650.1060EE6D663@gemini.denx.de> Message-ID: <4BF14FBF.3040900@freescale.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Wolfgang Denk wrote: >> > I was expecting the caller of fdt_increase_size() to know that the >> > space after the fdt is available. > So where is the code that makes sure that there is sufficient space > available? Well, if I load the fdt to address c0000, and it's 10KB in size, I'm pretty sure I can expand it to 16KB if I know that there's nothing else between c0000 and c4000. If you're asking about what code do I have that actually calls fdt_increase_size(), that code is currently used for a new board that we're not yet ready to publish. I'd like my patch for fdt_increase_size() included in the next merge window, so that when rebase our internal repository on the next release, this patch will already be available. It makes our internal development easier. -- Timur Tabi Linux kernel developer at Freescale