From mboxrd@z Thu Jan  1 00:00:00 1970
From: myan <miao.yan@windriver.com>
Date: Tue, 17 Sep 2013 10:14:35 +0800
Subject: [U-Boot] [PATCH 0/5] Add device tree support for VxWorks
In-Reply-To: <20130916193526.34CB138043D@gemini.denx.de>
References: <1379325490-3462-1-git-send-email-miao.yan@windriver.com>
	<20130916193526.34CB138043D@gemini.denx.de>
Message-ID: <5237BB0B.1000309@windriver.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

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:

   int do_bootm_vxworks(bootm_headers_t *images)
   {
       if (images->ft_addr)
          do_bootvx_fdt(images);
       else
          do_bootvx(NULL, 0, 0, NULL);
   }

So 'bootm' works with new versions of VxWorks if device tree blob
is provided, otherwise it falls back to 'bootvx'.

The original idea was to separate 'bootvx' from 'bootm' entirely,
but I am not sure how many users out there that depend on the old
  behavior, so I am inclined to keep it and not break anyone.

Could you help review the patches ? Thank you very much.

Miao