Skip to content

Add device tree support for VxWorks

myan u-boot 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest0 of 5 patches 0 repliesNew

Patches in v1 No applies recorded yet

None of the 5 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [U-Boot] [PATCH 0/5] Add device tree support for VxWorks

Hello Wolfgang,

Quoted 3 lines

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