Well, you can already do extreme tinkering to the point that RPi can no longer guarantee it functioning properly :) IIRC it's just that the bootcode.bin file i

Well, you can already do extreme tinkering to the point that RPi can no longer guarantee it functioning properly :) IIRC it's just that the bootcode.bin file is provided by Broadcom, and not the RPi foundation, so they can't open source it because they don't have the license to do so (this isn't the only proprietary blob in the default Pi distribution, but most of the other ones have open source alternatives/aren't that necessary/are open source now that they use the RP1 chip instead of broadcom peripherals). There's similar, slightly more open arrangements, with the Pi Pico W, where they can't provide the firmware for the Wifi chip, but they can provide a library to interface with it, with the caveat that the license _only_ allows for that library to be used with the RP* family of microcontrollers [1] [1]: https://github.com/georgerobotics/cyw43-driver/blob/faf36381bad1f668a30172b6336c9a970966ef4c/LICENSE.RP https://github.com/georgerobotics/cyw43-driver/blob/faf36381...