[U-Boot] [PATCH v3 1/5] common/cmd_bootm.c: seperate do_bootm_vxworks related code from CONFIG_CMD_ELF.

2013-11-28 Thread myan
From: Miao Yan miao@windriver.com do_bootm_vxworks now is available under the configuration option CONFIG_BOOTM_VXWORKS, thus aligned with other operating systems that supported by bootm command. The bootvx command still depneds on CONFIG_CMD_ELF. Signed-off-by: Miao Yan

[U-Boot] [PATCH v3 3/5] common/cmd_bootm: extend do_bootm_vxworks to support the new VxWorks boot interface.

2013-11-28 Thread myan
From: Miao Yan miao@windriver.com The next version VxWorks adopts device tree (for PowerPC and ARM) as its hardware description mechanism. For PowerPC, the boot interface conforms to the ePAPR standard, which is: void (*kernel_entry)(ulong fdt_addr, ulong r4 /* 0 */,

[U-Boot] [PATCH v3 5/5] README.vxworks: add a document describing the new VxWorks boot interface

2013-11-28 Thread myan
From: Miao Yan miao@windriver.com Signed-off-by: Miao Yan miao@windriver.com --- changes: v2-v3: rebase to master: d19ad726bcd5d9106f7ba9c750462fcc369f1020 v1-v2: none doc/README.vxworks | 19 +++ 1 file changed, 19 insertions(+) create mode 100644

[U-Boot] [PATCH v3 2/5] common/config_defaults.h: make CONFIG_BOOTM_VXWORKS default configuration

2013-11-28 Thread myan
From: Miao Yan miao@windriver.com Signed-off-by: Miao Yan miao@windriver.com --- Changes: v2-v3: rebase to master: d19ad726bcd5d9106f7ba9c750462fcc369f1020 v1-v2: none include/config_defaults.h |1 + 1 file changed, 1 insertion(+) diff --git a/include/config_defaults.h

[U-Boot] [PATCH v3 4/5] common/fdt_support.c: avoid unintended return from fdt_fixup_memory_banks()

2013-11-28 Thread myan
From: Miao Yan miao@windriver.com fdt_fixup_memory_banks() will add and update /memory node in device tree blob. In the case that /memory node doesn't exist, after adding a new one, this function returns error. The correct behavior should be continuing to update its properties.

[U-Boot] [PATCH] common/cmd_bootm.c: fix subcommand processing in OS specific do_bootm_xxx() functions

2013-11-03 Thread myan
From: Miao Yan miao@windriver.com In commit 5c427e4: use BOOTM_STATE_OS_CMDLINE flag for plain bootm and 3d187b3: Only pass BOOTM_STATE_OS_CMDLINE on PowerPC/MIPS, BOOTM_STATE_OS_CMLINE was added to do_bootm for PowerPC and MIPS. This breaks other OSes (vxworks, netbsd, plan9,...) that don't

[U-Boot] [PATCH v2] common/cmd_bootm.c: fix subcommand processing in OS specific do_bootm_xxx() functions

2013-11-03 Thread myan
From: Miao Yan miao@windriver.com In commit 5c427e4: use BOOTM_STATE_OS_CMDLINE flag for plain bootm and 3d187b3: Only pass BOOTM_STATE_OS_CMDLINE on PowerPC/MIPS, BOOTM_STATE_OS_CMDLINE was added to do_bootm for PowerPC and MIPS. This breaks other OSes (vxworks, netbsd, plan9,...) that don't

Re: [U-Boot] [PATCH v2 0/5] Add device tree support for VxWorks

2013-11-01 Thread myan
Hi Tom, On 10/31/2013 07:31 PM, Tom Rini wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/31/2013 05:56 AM, myan wrote: Will this go into master in this merge window ? And I noticed there are some changes to common do_bootm, which reqiures adjustment to vxworks subcommand

Re: [U-Boot] [PATCH v2 0/5] Add device tree support for VxWorks

2013-10-31 Thread myan
Hi Tom, On 09/24/2013 07:27 AM, Tom Rini wrote: I think things look OK, but as they were posted after the merge window closed, they won't go in to master until after the v2013.10 release, thanks! Will this go into master in this merge window ? And I noticed there are some changes to

Re: [U-Boot] help on adding bootelf to u-boot

2013-10-16 Thread myan
Hi, On 10/16/2013 03:10 PM, Robin Fernandes wrote: hi sir/madam I am trying to run bootelf command from u-boot. But the command is not inbuilt in it. So could you please let me know what is the procedure to compile.. make sure you have CONFIG_CMD_ELF in your board config file. Miao

Re: [U-Boot] help on adding bootelf to u-boot

2013-10-16 Thread myan
On 10/16/2013 03:10 PM, Robin Fernandes wrote: hi sir/madam I am trying to run bootelf command from u-boot. But the command is not inbuilt in it. So could you please let me know what is the procedure to compile.. for build instructions, see them here: http://www.denx.de/wiki/DULG/UBoot

Re: [U-Boot] [PATCH v2 0/5] Add device tree support for VxWorks

2013-09-21 Thread myan
Hi Tom, I posted some patches to add device tree support for VxWorks several days ago. Wolfgang provided me with some very useful feedback, and I sent v2 patches. The discussion and patches are recorded here:

Re: [U-Boot] [PATCH v2 0/5] Add device tree support for VxWorks

2013-09-18 Thread myan
Hi Wolfgang, Changes for v2: 1) separating legacy do_bootvx code from do_bootm_vxworks, thus making do_bootm_vxworks only work with new kernels, old kernels can still use 'bootvx' 2) minor fixes to make code more clear I've posted the v2 patches, how do you think

Re: [U-Boot] [PATCH 0/5] Add device tree support for VxWorks

2013-09-17 Thread myan
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

Re: [U-Boot] [PATCH 0/5] Add device tree support for VxWorks

2013-09-16 Thread myan
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