On Mon, Jun 27, 2022 at 7:12 PM Tim Newsome <t...@sifive.com> wrote: > > src/target/riscv/debug_defines.h: >> >> The license CC BY 4.0 is one-way compatible with GPLv3 >> https://creativecommons.org/2015/10/08/cc-by-sa-4-0-now-one-way-compatible-with-gplv3/ >> https://www.fsf.org/blogs/licensing/creative-commons-by-sa-4-0-declared-one-way-compatible-with-gnu-gpl-version-3 > > >> but I cannot find any statement about compatibility with the GPLv2 >> license of OpenOCD. > > >> Do you have any info to allow us keeping this file in OpenOCD? >> Can the license terms of this file be modified? > > > What does the text in the file need to say to be acceptable to OpenOCD? I can > see about getting it changed.
It should report a license compatible with GPLv2. Either GPLv2, BSD in any flavor, MIT. O dual licensing, like "CC-BY-4.0 OR BSD-3-Clause" >> src/target/riscv/encoding.h >> It reports only: >> /* See LICENSE for license details. */ >> Does it point to the old OpenOCD's LICENSE file, so GPLv2 ? Or it >> points to some other file in the auto-generation blob? > > > This file comes from https://github.com/riscv/riscv-opcodes. The LICENSE in > question looks a bit painful as well. I'll see about including the license > directly in that header file as a string, so it's present in the source and > could be displayed in a binary. The best option would be to have directly the standard SPDX tag in the first line, but it's also ok having just a line reporting under which license this file can be used. I will send out tonight or tomorrow a patch set that switches all the files in the src folder to SPDX. Only the two files above cannot be converted yet. Thanks, Antonio
