short form: is there an efficient way to add a new vendor and new zynqmp-based board to the u-boot infrastructure without creating a whole new vendor directory that (mostly) duplicates what is already under board/xilinx/?

as i read it, if i configure u-boot for, say, a xilinx zynqmp-based ZCU102 (rev 1.0), the "board" selection is actually just the SoC specifier -- in this case, zynqmp. the resulting .config file contains, among other stuff:

CONFIG_SYS_ARCH="arm" CONFIG_SYS_CPU="armv8" CONFIG_SYS_SOC="zynqmp" CONFIG_SYS_VENDOR="xilinx" CONFIG_SYS_BOARD="zynqmp" CONFIG_SYS_CONFIG_NAME="xilinx_zynqmp"

with no indication of the actual (ZCU102) target board. again, as i read it, the board-specific content comes from:

1) the board defconfig file, say:

$ make xilinx_zynqmp_zcu102_rev1_0_defconfig

2) the board/xilinx/zynqmp/ subdirectory identified by

CONFIG_DEFAULT_DEVICE_TREE="zynqmp-zcu102-rev1.0"

with most of those xilinx/zynqmp/ subdirectories containing the single (board-specific) source file psu_init_gpl.c. in other words, it *seems* that a new zynqmp-based board can be entirely defined by (in the simple case):

1) an appropriate defconfig file 2) a board-specific psu_init_gpl.c file

now, if i wanted to define a new vendor and board as above (say, vendor "acme" and board "coyote" rev 1.0, based on ZCU102), i could of course just create an entirely new vendor directory and copy all of the relevant content from board/xilinx/ into it, but most of that would be identical.

is there an obvious way to somehow "steal" the xilinx vendor content so that i don't have to copy it? copying it would naturally be the most obvious strategy, just wondering if there is a more clever way to base the new vendor and board off the board/xilinx/ content. (symlinks would also work, i guess, but that just seems messy.)

i'm guessing there's no clever way to do this, but i'm willing to be corrected.

rday