
21 May
2007
21 May
'07
8:31 p.m.
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