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
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.
Where exactly is the needed, i. e. which spoecific
On Aug 4, 2008, at 1:56 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 the
Kumar Gala wrote:
On Aug 4, 2008, at 1:56 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
On Aug 4, 2008, at 3:19 PM, Jerry Van Baren wrote:
Kumar Gala wrote:
On Aug 4, 2008, at 1:56 PM, Wolfgang Denk wrote:
In message Pine.LNX.
[EMAIL PROTECTED] you wrote:
Added the 'fdtcmd' environment variable as a way to provide
'fdt' commands
that the user can supply to manipulate
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.
Where exactly is the needed, i. e.
Kumar Gala wrote:
On Aug 4, 2008, at 3:19 PM, Jerry Van Baren wrote:
Kumar Gala wrote:
On Aug 4, 2008, at 1:56 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
On Aug 4, 2008, at 3:27 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 the
On Aug 4, 2008, at 3:44 PM, Jerry Van Baren wrote:
Kumar Gala wrote:
On Aug 4, 2008, at 3:19 PM, Jerry Van Baren wrote:
Kumar Gala wrote:
On Aug 4, 2008, at 1:56 PM, Wolfgang Denk wrote:
In message [EMAIL PROTECTED]
you wrote:
Added the 'fdtcmd' environment variable as a way to provide
Kumar Gala wrote:
On Aug 4, 2008, at 3:27 PM, Wolfgang Denk wrote:
So just run the needed commands before you run bootm as part of your
boot command sequence.
This doesnt work. Lets say I want to remove a node or property that
ft_board_setup() adds. If I do what you are suggesting the
In message [EMAIL PROTECTED] you wrote:
I don't like it that bootm is calling out to all sorts of functions that
could better be scripted. It complicates the bootm code (badly!), it
prevents users from doing clever things (because it hard codes the calls
and sequences of the calls to
In message [EMAIL PROTECTED] you wrote:
So just run the needed commands before you run bootm as part of your
boot command sequence.
This doesnt work. Lets say I want to remove a node or property that
ft_board_setup() adds. If I do what you are suggesting the node or
prop will get
On Aug 4, 2008, at 3:55 PM, Scott Wood wrote:
Kumar Gala wrote:
On Aug 4, 2008, at 3:27 PM, Wolfgang Denk wrote:
So just run the needed commands before you run bootm as part of
your
boot command sequence.
This doesnt work. Lets say I want to remove a node or property
that
Kumar Gala wrote:
On Aug 4, 2008, at 3:55 PM, Scott Wood wrote:
Why not? Wouldn't it be just another environment variable, like the
load address for the kernel?
Right now the fdt is placed at the first 4k page after the kernel is
decompressed. I don't now where that address is.
Do we
On Aug 4, 2008, at 4:07 PM, Wolfgang Denk wrote:
In message F388F9D5-B685-4DD8-
[EMAIL PROTECTED] you wrote:
So just run the needed commands before you run bootm as part of
your
boot command sequence.
This doesnt work. Lets say I want to remove a node or property that
In message [EMAIL PROTECTED] you wrote:
Why not? Wouldn't it be just another environment variable, like the
load address for the kernel?
Right now the fdt is placed at the first 4k page after the kernel is
decompressed. I don't now where that address is.
Who places it there?
We
16 matches
Mail list logo
