On Aug 5, 2008, at 4:40 PM, Wolfgang Denk wrote:
> In message <[EMAIL PROTECTED]>
> you wrote:
>> Added the 'fdtcmd' environment variable as a way to provide 'fdt'
>> commands
>> that the user can supply to manipulate the device tree after
>> ft_board_setup() and before the tree is handled to
In message <[EMAIL PROTECTED]> you wrote:
> Added the 'fdtcmd' environment variable as a way to provide 'fdt' commands
> that the user can supply to manipulate the device tree after
> ft_board_setup() and before the tree is handled to the kernel.
>
> The idea is that users may want to add or manip
On Aug 5, 2008, at 11:50 AM, Kumar Gala wrote:
> Added the 'fdtcmd' environment variable as a way to provide 'fdt'
> commands
> that the user can supply to manipulate the device tree after
> ft_board_setup() and before the tree is handled to the kernel.
>
> The idea is that users may want to ad
Added the 'fdtcmd' environment variable as a way to provide 'fdt' commands
that the user can supply to manipulate the device tree after
ft_board_setup() and before the tree is handled to the kernel.
The idea is that users may want to add or manipulate nodes w/changing the
u-boot binary. The curre