-
Notifications
You must be signed in to change notification settings - Fork 780
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GPLv3 Compatibility? #364
Comments
I'm in for changing the license as well. I have a few 3D printers running Marlin, so I'm excited to see what they come up with :) |
I've no problem with GPL2 or later... |
This is fantastic news! Another engineer and I have already done preliminary work on this and we know that we can reuse the FAT routines that Marlin already has for SD cards, so we only need the following files that implement the block-level USB mass storage access:
So for our purposes, if just those particular files were updated with the wording "GPL v2 or later", we would be able to perform the integration. Thank you so much! -- Marcio |
I just wanted to share some preliminary results. This is actually Marlin reading files from a USB drive. It is also driving a color LCD touch panel (another project we have been working on): Printing already works, although the only glitch is that currently the drive insertion/removal is not recognized (we still haven't figured out how to detect those events) |
Very cool.
Thanks for sharing!
…On Mar 19, 2018 11:43 AM, "Marcio Teixeira" ***@***.***> wrote:
I just wanted to share some preliminary results. This is actually Marlin
reading files from a USB drive. It is also driving a color LCD touch panel
(another project we have been working on):
[image: marlinusb]
<https://user-images.githubusercontent.com/29129419/37605915-e30ff9d6-2b59-11e8-978d-47302ceb6044.JPG>
Printing already works, although the only glitch is that currently the
drive insertion/removal is not recognized.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#364 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADskzDSeVvBNJCLHKGbZMNLvnj4wDiwBks5tf9IggaJpZM4SpQPX>
.
|
Curious whether there will be a commit with the files with an updated license? This is not something I feel comfortable doing myself on just our sources. I would like to replace the files I am currently using with something with the correct licenses that matches what is in this repo. I suppose I could also try using USB Host Shield 3.0, if you guys feel that is a better choice and are willing to re-license that as well. |
Since @felis assigned himself, I was assuming that he would do it? |
Anything happening with this? |
@marcio-ao I have updated the copyright header in the relevant files in 00aa355. |
@Lauszus : Awesome! Thank you so much! |
You're welcome :) |
@Lauszus : Sorry to bother you again, is there a chance you could update the license for the following files as well?
I'm sorry I didn't request this sooner. I got caught up in a new printer releases and I had to put this on hold for a while. |
@marcio-ao sorry for the late reply, it was fixed in: 06d5ed1. |
Great! Looking forward to seeing the code in the wild :) |
Hello,
We would like to incorporate the code from the USB Host Shield in the Marlin firmware for 3D printers as this would allow printers to read USB Flash Drives rather the SD cards. The company I work for is a great believer in open-source and we would donate all our integration work to the open-source and 3D printing community.
However, I notice that the USB Host Shield is released under "GPL v2" rather than "GPLv2 or later", which would preclude integration with Marlin, which is released under the "GPL v3".
Is there any chance the license could be upgraded to either the GPL v3, or to include the wording "GPLv2 or later" in order to maintain compatibility with the GPL v3?
Information why this is necessary for the GPLv3 and GPLv2 is listed here:
https://www.gnu.org/licenses/gpl-faq.html#AllCompatibility
Thank you!
-- Marcio
The text was updated successfully, but these errors were encountered: