From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jerry Van Baren Date: Tue, 24 Apr 2007 15:42:10 -0400 Subject: [U-Boot-Users] fdt addr should copy fdt out of flash In-Reply-To: <462E5A5E.8010905@freescale.com> References: <462E5492.2010404@freescale.com> <462E5992.3000405@smiths-aerospace.com> <462E5A5E.8010905@freescale.com> Message-ID: <462E5D92.7000303@smiths-aerospace.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Timur Tabi wrote: > Jerry Van Baren wrote: > >> The email addresses correspond to my day job, my night job, and I >> subscribed to the u-boot list at home via gmail to control my email >> clutter (I'm also subscribed to the u-boot list at my day job because >> I'm an email junkie). > > So if I had to email you out-of-the blue about an FDT issue, which one > should I use? Well, it is hard to say... if you want the fastest response during the day (Eastern TZ), the smiths-aerospace.com address will be the one, but it will probably change sometime fairly soon... (the deal is scheduled to close May 4). The gvb.uboot at gmail is how I'm subscribed as at home, and that is where I work on u-boot, but the response time will be less consistent. CC:ing the list will generally be the fastest and most reliable. >> "fdt addr" is to tell fdt where the blob is in memory. If you want to >> move it from flash to RAM, you need to use "fdt move". > > fdt move requires me to know how big the FDT is. Is there any way you > can have it figure out for me? Yup, I'll add that as a desired enhancement. The size should be optional like it is with "fdt addr". Done (adding it to the ToDo list, that is). >> The "bootm" code (should) still copy from flash to RAM if necessary, >> because I adapted the existing code. > > Ah yes, you're right.