8 ms·
Where is the source code for the actual bootloader shipped with the Prusa Mini+?
- danuker 5y agoThis is an attempt sneak DRM into an industry full of passionate and knowledgeable buyers. Bad move.
- djmips 5y agoReading the entire thread from the posted link, it appears they will open source the bootloader.
- 95014_refugee 5y agoNo, this is just the usual torches-and-pitchforks crowd.
- mistrial9 5y agobusiness of all sizes, and government and all their cohort, routinely ignore FOSS license in all parts of the world. Even if ninety percent of those are compliant, its a big, big world. Why mock people who stand up for this situation on the part of FOSS ?
- jefftk 5y ago> Why mock people who stand up for this situation on the part of FOSS? In this case, because they are wrong and the GPL does not say what they think it says.
- oneplane 5y agoNo it's not. They have a known-good path you can deviate off of that allows you to run whatever you want with no restrictions. Everything still works, but the only thing is that since you can now do things that they might not have thought of, they are not going to be responsible for the side-effects that might have. Essentially, it's an irreversible switch which allows you to run firmware that is not signed by their private key, which makes it a end-user choice: you can be in a safe and protected world, or you can be in a free do-what-you-want world; all you have to do is choose.
- xf1cf 5y agoThis would be a nice to have with the crealitys. You can flash the board with custom firmware, you can make small surface level modifications to the LCD, but you cannot access the full LCD firmware. For some reason they made the board firmware open but the LCD firmware closed. Unlike what Prusa did, creality seems actively hostile.
- danuker 5y ago> not everyone feels that Prusa Research has made the Mini as “open” as its predecessors. Some concerned owners have pointed out that according to the documentation for the Buddy board, they’ll need to physically snap off a section of the PCB so they can flash custom firmware images via Device Firmware Upgrade (DFU) mode. Once this piece of the board has been broken off, which the documentation refers to as the Appendix, Prusa Research will no longer honor any warranty claims for the electronic components of the printer. https://hackaday.com/2019/12/16/prusa-dares-you-to-break-their-latest-printer/ https://hackaday.com/2019/12/16/prusa-dares-you-to-break-the...
- Lammy 5y agoEven though I disagree with the notion of software changes nullifying a hardware warranty, that is a cute way to do it that I’ve never seen before.
- sschueller 5y agoUsually software can't easily destroy a device like a network switch. However on a 3d printer you can burn the whole unit into ash if you remove overheat protections. You may also be able to destroy stepper motors or drivers.
- gjsman-1000 5y agoAnd this isn't even theoretical. Buggy 3D Printer Software has literally burned people's homes down in the past.
- mschuster91 5y agoThat's really bad design then. Any design worth its salt should incorporate a thermal soft-fuse at the heater element that cuts power off if the printhead ever goes above the maximum temperature that any filament can handle. Pure software interlocks are not sufficient. One might think people would have learned a lesson, nearly half a decade after Therac-25.
- lights0123 5y agoWhy would a bootloader ever be considered part of the same program—they don't even ever run at the same time. Also, this person (https://github.com/prusa3d/Prusa-Firmware-Buddy/issues/1440#issuecomment-855153091 https://github.com/prusa3d/Prusa-Firmware-Buddy/issues/1440#...) misread the GPL, when they said this: > but the license clearly states that it is not an aggregate if they are combined to form a larger program in or on a storage or distribution medium The GPL very much does not say that: > which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an “aggregate”
- gjsman-1000 5y agoOtherwise GRUB, which boots Linux, would force your entire OS to be GPL. Worse, GRUB can boot Windows when dual-booting, and because Windows will never be GPL, GRUB's ability to boot Windows would be a GPL violation. The bootloader on the Prusa Mini is basically GRUB in this case.
- sokoloff 5y agoI don’t think that my installing Grub and Windows for my own use would be a GPL violation under that line of reasoning. I can freely co-install non-GPL and GPL software, so long as I do not propagate (or convey) the result. One excerpt: “This License explicitly affirms your unlimited permission to run the unmodified Program.”
- weinzierl 5y ago> Why would a bootloader ever be considered part of the same program—they don't even ever run at the same time. Hmm, its not so easy, I think. A bootloader is code that might be in the address space after boot and may well run even after boot. Real world examples of this are the PC-BIOS (if you agree to classify it as kind of a boot loader) and Sun OpenBoot PROM. The PC-BIOS routines are used during runtime of older Operating Systems and to bring up the newer ones. Diagnostics Mode on a Sun can be entered any time by pressing a special key combo (Stop+A) and this will run OpenBoot code. Even for more modern systems using U-Boot it is not clear cut. At least U-Boot deemed it necessary to clarify it in its license: "U-Boot is Free Software. It is copyrighted by Wolfgang Denk and many others who contributed code (see the actual source code and the git commit messages for details). You can redistribute U-Boot and/or modify it under the terms of version 2 of the GNU General Public License as published by the Free Software Foundation. Most of it can also be distributed, at your option, under any later version of the GNU General Public License -- see individual files for exceptions. NOTE! This license does not cover the so-called "standalone" applications that use U-Boot services by means of the jump table provided by U-Boot exactly for this purpose - this is merely considered normal use of U-Boot, and does not fall under the heading of "derived work" -- see file Licenses/Exceptions for details. " EDIT: Just to be clear, I agree with lights0123's main argument, I just wanted to point out that it's not trivial and that "they don't even ever run at the same time." is not the strongest supporting point.
- rrss 5y agomatthewlloyd believes that distributing a bootloader and Marlin on the same flash memory makes them one large program, so Marlin's GPLv3 license should cover both. Prusa believes that the bootloader and Marlin are two separate programs aggregated together, so they can have separate licenses. It does not make sense to me to consider a bootloader and whatever it boots to be one program. seems like GRUB (GPLv3) generally is not considered to infect everything it boots / chainloads. > Where's the line between two separate programs, and one program with two parts? This is a legal question, which ultimately judges will decide. We believe that a proper criterion depends both on the mechanism of communication (exec, pipes, rpc, function calls within a shared address space, etc.) and the semantics of the communication (what kinds of information are interchanged). https://www.gnu.org/licenses/gpl-faq.en.html https://www.gnu.org/licenses/gpl-faq.en.html
- PragmaticPulp 5y agoI don’t see any way this holds up. The bootloader hands off execution to a separate program, so they have about as minimal communication as possible. They don’t even run at the same time. It also doesn’t make sense to consider different, independently engineered pieces to be one in the same simply because they were shipped on the same storage medium.
- gjsman-1000 5y agoOtherwise, would GRUB or the old LILO literally force your entire OS to be GPL? That would be insanity.
- macksd 5y agoYeah, this seems like an even weaker connection than disibributing a GNU/Linux-based VM or Docker image with a non-GPL/LGPL application in it.
- amelius 5y ago> It does not make sense to me to consider a bootloader and whatever it boots to be one program. Yes the name says it: a bootloader loads some other program into memory.
- rm445 5y agoIt seems fairly clear from a licensing point of view that a bootloader is a separate program from what it boots (which can be pretty much anything). It does seem like something which could concern the community though. What if (in future) the bootloader only boots Prusa-signed firmware, and lines for programming the board directly are disabled in hardware at the factory? If Prusa aren't planning any user-hostile behaviour, they should act fairly quickly to keep their community happy.
- gjsman-1000 5y agoI have an original Prusa Mini I upgraded to the Mini+. I ordered it and it arrived in December 2019. Like other Prusa Minis, it comes with an "appendix" you must physically break to be able to install unsigned firmware. And, of course, breaking the appendix voids the warranty and drops all liability on the part of the manufacturer. My warranty has long expired but I haven't broken it yet. Personally, I think that in this era of Hardware Root of Trust devices and locked bootloaders, if we were to try to prevent such devices from existing, I think the appendix is a fairly brilliant solution that could be applied elsewhere. For example, my iPhone. Apple doesn't allow side-loading because, well, they're afraid Facebook or Epic would force users to side-load against their will, among other business reasons. But if they were legally mandated to offer an appendix that could be snapped to enable sideloading, it would hopefully keep Facebook at bay (there's no way Facebook can convince people broadly to do such a thing), and would satisfy us hardware hackers. It's still not perfect, but I think it could be an excellent "first step" in unlocking these devices that, among many solutions, could potentially be bipartisan and harder for tech companies to argue against.
- smoldesu 5y agoI mostly think the "appendix" system works, but I think the first party should still assume limited liability for the hardware of the device after the appendix is broken, so they still have an incentive not to conspire against their users. Furthermore: > Apple doesn't allow side-loading because, well, they're afraid Facebook or Epic would force users to side-load against their will, among other business reasons. I think "other business reasons" are the bigger issue here. Facebook and Epic wouldn't "force" users to side-load content any more than Apple "forces" you to use the App Store on iOS. It's an available option that you can use at your own discretion. Apple (unlike Prusa) has painted themselves into a pretty favorable corner. They've made their value proposition immaterial, which allows them to pretty easily deflect any accusations that their 30% cut is out of line. Apple has full control over the goalposts here: they could claim that their cut goes to hosting alone or covers the entirety of the review process.
- R0b0t1 5y ago> I mostly think the "appendix" system works, but I think the first party should still assume limited liability for the hardware of the device after the appendix is broken, so they still have an incentive not to conspire against their users. The seller can not absolve themselves of liability in this way. They still assume liability under their warranty and must prove changes you made are the cause of malfunction even if you modify the device. https://en.wikipedia.org/wiki/Magnuson%E2%80%93Moss_Warranty_Act https://en.wikipedia.org/wiki/Magnuson%E2%80%93Moss_Warranty...