From mboxrd@z Thu Jan 1 00:00:00 1970 From: Timur Tabi Date: Mon, 21 May 2007 13:31:21 -0500 Subject: [U-Boot-Users] Ideas on U-Boot configuration with FDT In-Reply-To: <4651D47E.5040603@smiths-aerospace.com> References: <20070520093335.9FF32353428@atlas.denx.de> <4650477F.3040007@grandegger.com> <4651B871.2070904@freescale.com> <4651CF98.30107@grandegger.com> <4651D0B9.9080000@freescale.com> <4651D47E.5040603@smiths-aerospace.com> Message-ID: <4651E579.40905@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 Jerry Van Baren wrote: > You totally lost me on that assertion. What do you mean when you say > "macro commands?" It's a sequence of commands stored in an environment variable, executed via the "run" command. I guess they're called hush scripts. > If you mean a hush script when you say "macro commands", that would be a > way of setting an env variable, so how is that more flexible? We > already have the "fdt addr" command at the hush level that can be used > by hand or in scripts to set the fdt blob address, but that is _way_ > later in the boot cycle than what Wolfgang will be using. I mean more flexible in that you can use a hush script to set that variable and do other things at boot time. -- Timur Tabi Linux Kernel Developer @ Freescale