Hello Wolfgang,
I think this is not a good idea, for two reasons.
First, it means the behaviour of the "bootm" command is not
consistent - with FDT address passed as argument it behaves one way,
without it behaves different.
Second, You may want to support images that have the FDT attached or
Dear Myan,
In message <5237bb0b.1000...@windriver.com> you wrote:
> Hello Wolfgang,
>
> > You intend to 1) just keep the existing 'bootvx' command for
> > compatibility with older VxWorks versions, and 2) use plain 'bootm'
> > for new versions, like we do for other OSes?
>
>
> Yes, this is what
Hello Wolfgang,
You intend to 1) just keep the existing 'bootvx' command for
compatibility with older VxWorks versions, and 2) use plain 'bootm'
for new versions, like we do for other OSes?
Yes, this is what I intended to implement, sorry for not being
more clear. The pesdo-code is like this:
Dear Miao Yan,
In message <1379325490-3462-1-git-send-email-miao@windriver.com> you wrote:
>
> The 'bootvx' commnad stays unchaged, and is still avalaible under
> the configuration option CONFIG_CMD_ELF for older kernels. A new
> option CONFIG_BOOTM_VXWORKS is added for bootm to align with o
Hello Wolfgang and All,
The next release of VxWorks will adopt device tree as its
hardware description mechanism (for PowerPC and ARM), thus
requiring boot interface changes for these two architechtures.
And we would like to better support U-Boot with our operating
system, because almost all
5 matches
Mail list logo
