Joel Sherrill created an issue: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5335
## Summary We use rtems-bin2c to turn files into arrays of unsigned characters. These arrays can be compiled and embedded into programs. This is used for a tar file containing the initial file system image, device tree, and more. The generated files in the RTEMS source tree are a hodge podge of no license/attribution and odd attributions that need to be reviewed. At least the following files are impacted: - testsuites/fstests/fsdosfsname01/image.h - testsuites/fstests/fsdosfsname01/files.h - testsuites/fstests/fsdosfsname01/image_bin_le_multibyte.h - testsuites/fstests/fsdosfsname01/image_bin_le_singlebyte.h - testsuites/fstests/fsdosfsname01/init.c - testsuites/libtests/libfdt01/some.h - testsuites/libtests/libfdt01/some.c - testsuites/libtests/ofw01/some.c - testsuites/libtests/ofw01/some.h - bsps/arm/imxrt/dts/imxrt1050-evkb.c - bsps/arm/imxrt/dts/imxrt1166-cm7-saltshaker.c - bsps/riscv/riscv/include/bsp/beaglevfire.h - bsps/riscv/riscv/include/bsp/kendryte-k210-dtb.h - bsps/riscv/riscv/include/bsp/mpfs-dtb.h - bsps/aarch64/raspberrypi/fdt/rpi4b_dtb.c - bsps/microblaze/microblaze_fpga/include/bsp/microblaze-dtb.h We need to decide what to do with these files. It seems wrong to claim attribution for the bin2c version of a device tree. I think rtems-bin2c may need some additions to help with this. - option (-2) to just insert 2-BSD SPDX and license. - automatically generated comment to follow Doxygen style for @file and include the name of the source file - option (?) for SPDX string. Already has option for license file to insert. ### Pre-set options -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5335 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
