From: Wolfgang Denk Date: Mon, 16 Sep 2013 21:35:26 +0200 Subject: [U-Boot] [PATCH 0/5] Add device tree support for VxWorks In-Reply-To: <1379325490-3462-1-git-send-email-miao.yan@windriver.com> References: <1379325490-3462-1-git-send-email-miao.yan@windriver.com> Message-ID: <20130916193526.34CB138043D@gemini.denx.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Dear Miao Yan, In message <1379325490-3462-1-git-send-email-miao.yan@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 other > bootm supported operating systems. > > So the do_bootm_vxworks will work as below: > > #if (libfdt && (ppc || arm)) > if (using device tree) > boot_vxworks_with_device_tree > else > #endif > bootvx(...); I'm not sure I understand what this means. Please correct if my interpretation is incorrect or incomplete: 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? That sounds good to me. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de You got to learn three things. What's real, what's not real, and what's the difference." - Terry Pratchett, _Witches Abroad_