From: myan <miao.yan@windriver.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/5] Add device tree support for VxWorks
Date: Tue, 17 Sep 2013 10:14:35 +0800 [thread overview]
Message-ID: <5237BB0B.1000309@windriver.com> (raw)
In-Reply-To: <20130916193526.34CB138043D@gemini.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
next prev parent reply other threads:[~2013-09-17 2:14 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 9:58 [U-Boot] [PATCH 0/5] Add device tree support for VxWorks Miao Yan
2013-09-16 9:58 ` [U-Boot] [PATCH 1/5] common/cmd_bootm.c: seperate do_bootm_vxworks related code from CONFIG_CMD_ELF Miao Yan
2013-09-16 9:58 ` [U-Boot] [PATCH 2/5] common/config_defaults.h: make CONFIG_BOOTM_VXWORKS default configuration Miao Yan
2013-09-16 9:58 ` [U-Boot] [PATCH 3/5] common/cmd_bootm: extend do_bootm_vxworks to support the new VxWorks boot interface Miao Yan
2013-09-16 9:58 ` [U-Boot] [PATCH 4/5] common/fdt_support.c: avoid unintended return from fdt_fixup_memory_banks() Miao Yan
2013-09-16 9:58 ` [U-Boot] [PATCH 5/5] doc/README.vxworks: add a document describing the new VxWorks boot interface Miao Yan
2013-09-16 19:35 ` [U-Boot] [PATCH 0/5] Add device tree support for VxWorks Wolfgang Denk
2013-09-17 2:14 ` myan [this message]
2013-09-17 6:14 ` Wolfgang Denk
2013-09-17 7:44 ` myan
2013-09-17 11:33 ` [U-Boot] [PATCH v2 " Miao Yan
2013-09-17 11:33 ` [U-Boot] [PATCH v2 1/5] common/cmd_bootm.c: seperate do_bootm_vxworks related code from CONFIG_CMD_ELF Miao Yan
2013-11-28 9:51 ` [U-Boot] [PATCH v3 " myan
2013-11-28 9:51 ` [U-Boot] [PATCH v3 2/5] common/config_defaults.h: make CONFIG_BOOTM_VXWORKS default configuration myan
2013-12-16 14:14 ` [U-Boot] [U-Boot, v3, " Tom Rini
2013-11-28 9:51 ` [U-Boot] [PATCH v3 3/5] common/cmd_bootm: extend do_bootm_vxworks to support the new VxWorks boot interface myan
2013-12-16 14:14 ` [U-Boot] [U-Boot, v3, " Tom Rini
2013-11-28 9:51 ` [U-Boot] [PATCH v3 4/5] common/fdt_support.c: avoid unintended return from fdt_fixup_memory_banks() myan
2013-12-16 14:14 ` [U-Boot] [U-Boot, v3, " Tom Rini
2013-11-28 9:51 ` [U-Boot] [PATCH v3 5/5] README.vxworks: add a document describing the new VxWorks boot interface myan
2013-12-16 14:15 ` [U-Boot] [U-Boot, v3, " Tom Rini
2013-12-16 14:17 ` [U-Boot] [U-Boot, v3, 1/5] common/cmd_bootm.c: seperate do_bootm_vxworks related code from CONFIG_CMD_ELF Tom Rini
2013-09-17 11:34 ` [U-Boot] [PATCH v2 2/5] common/config_defaults.h: make CONFIG_BOOTM_VXWORKS default configuration Miao Yan
2013-09-17 11:34 ` [U-Boot] [PATCH v2 3/5] common/cmd_bootm: extend do_bootm_vxworks to support the new VxWorks boot interface Miao Yan
2013-09-17 11:34 ` [U-Boot] [PATCH v2 4/5] common/fdt_support.c: avoid unintended return from fdt_fixup_memory_banks() Miao Yan
2013-09-17 11:34 ` [U-Boot] [PATCH v2 5/5] doc/README.vxworks: add a document describing the new VxWorks boot interface Miao Yan
2013-09-18 6:14 ` [U-Boot] [PATCH v2 0/5] Add device tree support for VxWorks myan
2013-09-22 2:57 ` myan
2013-09-23 23:27 ` Tom Rini
2013-10-31 9:56 ` myan
2013-10-31 11:31 ` Tom Rini
2013-11-01 7:44 ` myan
2013-11-01 12:23 ` Tom Rini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5237BB0B.1000309@windriver.com \
--to=miao.yan@windriver.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox