You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working on building a custom Debug Probe, and was auditing the SDK's licenses for files my compiler touches during building.
double_v1_rom_shim.S is copywritten by Mark Owen under GPLv2, but contains an alternate sublicense through Raspberry Pi. However, this sublicense only permits use of the software (specifically only on a Raspberry Pi Pico device), but it does not permit recipients to sublicense or distribute this software (such as in a firmware binary to end-users).
Is it possible to reword this sublicense with more conventional language so that it grants recipients permission to sublicense & distribute without having to resort to the copyleft of GPLv2?
Additionally, would it be relevant to expand the restrictiont to allow usage on all RP2040 devices, rather than exlusively the Pico?
The text was updated successfully, but these errors were encountered:
I'm working on building a custom Debug Probe, and was auditing the SDK's licenses for files my compiler touches during building.
double_v1_rom_shim.S
is copywritten by Mark Owen under GPLv2, but contains an alternate sublicense through Raspberry Pi. However, this sublicense only permits use of the software (specifically only on a Raspberry Pi Pico device), but it does not permit recipients to sublicense or distribute this software (such as in a firmware binary to end-users).Is it possible to reword this sublicense with more conventional language so that it grants recipients permission to sublicense & distribute without having to resort to the copyleft of GPLv2?
Additionally, would it be relevant to expand the restrictiont to allow usage on all RP2040 devices, rather than exlusively the Pico?
The text was updated successfully, but these errors were encountered: