• 2 Posts
  • 100 Comments
Joined 1 year ago
cake
Cake day: September 29th, 2023

help-circle











  • You’re right, seems like GPLv2 is incompatible with AGPL. GPLv3 includes extra clauses to allow it.

    From the GNU Licensing page

    Please note that the GNU AGPL is not compatible with GPLv2. It is also technically not compatible with GPLv3 in a strict sense: you cannot take code released under the GNU AGPL and convey or modify it however you like under the terms of GPLv3, or vice versa. However, you are allowed to combine separate modules or source files released under both of those licenses in a single project, which will provide many programmers with all the permission they need to make the programs they want. See section 13 of both licenses for details.




  • exu@feditown.comtoOpen Source@lemmy.mlWhy is GrapheneOS against GNU?
    link
    fedilink
    English
    arrow-up
    8
    arrow-down
    1
    ·
    30 days ago

    Unfortunately, the FSF isn’t against firmware blobs, only against those updatable by a user.

    From their Respects Your Freedom requirements page.

    However, there is one exception for secondary embedded processors. The exception applies to software delivered inside auxiliary and low-level processors and FPGAs, within which software installation is not intended after the user obtains the product. This can include, for instance, microcode inside a processor, firmware built into an I/O device, or the gate pattern of an FPGA. The software in such secondary processors does not count as product software.

    This means that proprietary firmware flashed at the factory and impossible to replace gets a pass, while hardware with firmware updates through blobs is rejected. Important security fixes (CPU microcode) or stability improvements will be missing if you can’t update the firmware.