I think the authors of the driver can release the source code using two or more licenses.
We already have an example of it in NuttX: SocketCAN Since they add the OR license clause it is fine. BR, Alan On 9/14/23, Alin Jerpelea <jerpe...@gmail.com> wrote: > Hi Pavel, > > small oftopic regarding the license header: > > https://www.gnu.org/licenses/license-compatibility.en.html > > "Apache 2.0, has patent clauses which are incompatible with GPL version 2; > since I think those patent clauses are good, I made GPL version 3 > compatible with them." > > Best regards > Alin > > > On Thu, 14 Sept 2023, 16:06 Pavel Pisa, <ppisa4li...@pikron.com> wrote: > >> Hello Alin, Brennan and Andrew, >> >> On Tuesday 12 of September 2023 19:39:31 Alin Jerpelea wrote: >> > from my knowledge the GPL code is disabled by default and users MUST >> > manually enable it >> > >> > On Tue, Sep 12, 2023 at 6:26 PM Brennan Ashton < >> bash...@brennanashton.com> >> > >> > wrote: >> > > I'm very confused as to the issue here. This is not GPL code, this is >> > > code that is dual licensed. I think two totally different topics are >> > > being conflated here. >> >> Excuse of jumping late into discussion. I have not noticed this thread >> and I am not sure about t outcome. I tried to be clean in the offlist >> discussion but I am not sure still for some nithes details from NuttX >> side. >> >> Our code is GPL licensed now but all copyright holders agree >> on providing it under license fully compatible with NuttX and RTEMS >> mainlines. >> >> I have offered and discussed the license >> >> // SPDX-License-Identifier: GPL-2.0-or-later OR BSD-2-Clause OR >> Apache-2.0 >> >> with keeping of the list of the authors and reference to the Czech >> Technical >> University at start of files. >> >> If the whole list of the licenses is kept, then it allows mutual >> enhancements >> between driver code forks for individual systems. As I describe >> elsewhere, >> I understand and agree that driver should be readable and with minimum >> adaptation/compatibility layers for each kernel even that it means >> additional >> effort on our side. >> >> The question to the NuttX stewards is wheather >> >> // SPDX-License-Identifier: GPL-2.0-or-later OR BSD-2-Clause OR >> Apache-2.0 >> >> line/license s acceptable for manline. >> If not, then we leave Apache-2.0 alone and try to track permission of >> other >> outside (non-CTU) contributors to reuse their possible code enhancements >> under other two licenses. >> >> Best wishes, >> >> Pavel >> >> -- >> Pavel Pisa >> >> phone: +420 603531357 >> e-mail: p...@cmp.felk.cvut.cz >> Department of Control Engineering FEE CVUT >> Karlovo namesti 13, 121 35, Prague 2 >> university: http://control.fel.cvut.cz/ >> personal: http://cmp.felk.cvut.cz/~pisa >> company: https://pikron.com/ PiKRON s.r.o. >> Kankovskeho 1235, 182 00 Praha 8, Czech Republic >> projects: https://www.openhub.net/accounts/ppisa >> social: https://social.kernel.org/ppisa >> CAN related:http://canbus.pages.fel.cvut.cz/ >> RISC-V education: https://comparch.edu.cvut.cz/ >> Open Technologies Research Education and Exchange Services >> https://gitlab.fel.cvut.cz/otrees/org/-/wikis/home >> >
