MIT vs GNU licences for Embedded system projectsCan I Open Source a software for a particular operating system?Using the (L)GPL as an open-source hardware license?What if a company uses my open source project for a closed-source system?What is the point of including the MIT copyright text if you use someone's code licensed under MIT?GNU GPL LicensingCan I sell my project using GNU GPL v3?How to apply the MIT License to a program including its embedded resource data?Open source components in a larger one-off system setupIs License Zero compatible with other open source licenses like GNU, MIT or BSD licenses for example?What is the difference between LGPLv2.1 and LGPLv3?
Create a program that prints the amount of characters it has, in words
Adjusting the definition of a well-powered category to category theory with universes: size issues
Decay of spin-1/2 particle into two spin-1/2 particles
Drawing some fruits with tikz
How to selectively rsync folders while retaining tree structure?
Did Bercow say the would have sent the EU extension-request letter himself had Johnson not done so?
Why is macOS limited to 1064 processes?
Why is the Falcon Heavy center core recovery done at sea?
Where is the deflector array on the Phoenix?
In Cura, can I make my top and bottom layer be all perimiters?
How would a young girl/boy (about 14) who never gets old survive in the 16th century?
Intuition behind the paradox of instantaneous heat propagation
Are the Shimano Derailleurs sold in Ali Express genuine or fake?
Leaving passport in the hotel room
Meaning of "in arms"
Why is Ancient Greek "δέ" translated by Gothic "þan" /then/?
What order of magnitude incoming asteroid could we, in fact, deflect?
Are there any spells that aren't on any class's spell list?
What is a GPU year?
Why buy a first class ticket on Southern trains?
Spent or spend?
Right way to say I disagree with the design but ok I will do
Hypothesis testing- with normal approximation
where does black come from in CMYK color mode?
MIT vs GNU licences for Embedded system projects
Can I Open Source a software for a particular operating system?Using the (L)GPL as an open-source hardware license?What if a company uses my open source project for a closed-source system?What is the point of including the MIT copyright text if you use someone's code licensed under MIT?GNU GPL LicensingCan I sell my project using GNU GPL v3?How to apply the MIT License to a program including its embedded resource data?Open source components in a larger one-off system setupIs License Zero compatible with other open source licenses like GNU, MIT or BSD licenses for example?What is the difference between LGPLv2.1 and LGPLv3?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;
For embedded system projects which have small hardware using MCU's and sensors and use open source c-source codes. How will it make a difference if my license is an MIT or a GNU licenses?
licensing
migrated from electronics.stackexchange.com Jun 2 at 18:29
This question came from our site for electronics and electrical engineering professionals, students, and enthusiasts.
add a comment
|
For embedded system projects which have small hardware using MCU's and sensors and use open source c-source codes. How will it make a difference if my license is an MIT or a GNU licenses?
licensing
migrated from electronics.stackexchange.com Jun 2 at 18:29
This question came from our site for electronics and electrical engineering professionals, students, and enthusiasts.
1
When speaking of computer programs, "code" is always singular. "Codes" are the things you use to open a combination lock or to encrypt secret messages.
– JRE
Jun 2 at 10:13
… or to add information to allow for forward error correction (channel codes), or to make a digital data stream transportable reliably over a physical cable (line codes).
– Marcus Müller
Jun 2 at 10:22
add a comment
|
For embedded system projects which have small hardware using MCU's and sensors and use open source c-source codes. How will it make a difference if my license is an MIT or a GNU licenses?
licensing
For embedded system projects which have small hardware using MCU's and sensors and use open source c-source codes. How will it make a difference if my license is an MIT or a GNU licenses?
licensing
licensing
asked Jun 2 at 10:01
jacklyjackly
migrated from electronics.stackexchange.com Jun 2 at 18:29
This question came from our site for electronics and electrical engineering professionals, students, and enthusiasts.
migrated from electronics.stackexchange.com Jun 2 at 18:29
This question came from our site for electronics and electrical engineering professionals, students, and enthusiasts.
migrated from electronics.stackexchange.com Jun 2 at 18:29
This question came from our site for electronics and electrical engineering professionals, students, and enthusiasts.
1
When speaking of computer programs, "code" is always singular. "Codes" are the things you use to open a combination lock or to encrypt secret messages.
– JRE
Jun 2 at 10:13
… or to add information to allow for forward error correction (channel codes), or to make a digital data stream transportable reliably over a physical cable (line codes).
– Marcus Müller
Jun 2 at 10:22
add a comment
|
1
When speaking of computer programs, "code" is always singular. "Codes" are the things you use to open a combination lock or to encrypt secret messages.
– JRE
Jun 2 at 10:13
… or to add information to allow for forward error correction (channel codes), or to make a digital data stream transportable reliably over a physical cable (line codes).
– Marcus Müller
Jun 2 at 10:22
1
1
When speaking of computer programs, "code" is always singular. "Codes" are the things you use to open a combination lock or to encrypt secret messages.
– JRE
Jun 2 at 10:13
When speaking of computer programs, "code" is always singular. "Codes" are the things you use to open a combination lock or to encrypt secret messages.
– JRE
Jun 2 at 10:13
… or to add information to allow for forward error correction (channel codes), or to make a digital data stream transportable reliably over a physical cable (line codes).
– Marcus Müller
Jun 2 at 10:22
… or to add information to allow for forward error correction (channel codes), or to make a digital data stream transportable reliably over a physical cable (line codes).
– Marcus Müller
Jun 2 at 10:22
add a comment
|
1 Answer
1
active
oldest
votes
You're asking this from an electrical engineer's perspective, which puts all this in the context of building electronic devices and handing them to other people.
It's very simple: If you give anybody a device with GPL software on it, you must offer the source code at no additional expense (aside from the physical cost of copying the source code, which should be effectively zero these days) to them, especially including all your modification to it, and all the build infrastructure needed to build that software.
MIT doesn't require that.
Both licenses require you to let the receiver of the device including the software know that the software is licensed under MIT or GPL terms.
GPL is more "dispersive": when you write software that builds upon GPL code (e.g. you use a GPL library to calculate coordinates), that software becomes copyleft, too, and you'll need to also offer that software's source code to the receiver of the device.
Notice that there are multiple versions, especially of the GPL, and some contain specific exceptions. So, you need to make an individual case for each.
Generally, most complex embedded consumer devices you know run a lot of Free & Open Source Software – for example, the Linux kernel powering both your Android phone and probably your airplane seat TV and quite likely your internet router and … is GPL'ed. Your smart TV contains probably copious amounts of LGPL, MIT, Apache licensed code. The Arduino Platform itself is LGPL/GPL. The arm mbed operating system, which is relatively popular in IoT devices, is Apache Licensed; FreeRTOS, one of the very most popular emdedded operating systems for smaller, real-time devices, is MIT-licensed.
Also note: if you're not giving your device to anyone (paid or not), but are keeping it to yourself, there's no differences.
Further, note that in the world of hardware description languages (e.g. Verilog, VHDL), things are a bit fuzzy when it comes to the effects of GPL.
add a comment
|
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "619"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/4.0/"u003ecc by-sa 4.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fopensource.stackexchange.com%2fquestions%2f8365%2fmit-vs-gnu-licences-for-embedded-system-projects%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You're asking this from an electrical engineer's perspective, which puts all this in the context of building electronic devices and handing them to other people.
It's very simple: If you give anybody a device with GPL software on it, you must offer the source code at no additional expense (aside from the physical cost of copying the source code, which should be effectively zero these days) to them, especially including all your modification to it, and all the build infrastructure needed to build that software.
MIT doesn't require that.
Both licenses require you to let the receiver of the device including the software know that the software is licensed under MIT or GPL terms.
GPL is more "dispersive": when you write software that builds upon GPL code (e.g. you use a GPL library to calculate coordinates), that software becomes copyleft, too, and you'll need to also offer that software's source code to the receiver of the device.
Notice that there are multiple versions, especially of the GPL, and some contain specific exceptions. So, you need to make an individual case for each.
Generally, most complex embedded consumer devices you know run a lot of Free & Open Source Software – for example, the Linux kernel powering both your Android phone and probably your airplane seat TV and quite likely your internet router and … is GPL'ed. Your smart TV contains probably copious amounts of LGPL, MIT, Apache licensed code. The Arduino Platform itself is LGPL/GPL. The arm mbed operating system, which is relatively popular in IoT devices, is Apache Licensed; FreeRTOS, one of the very most popular emdedded operating systems for smaller, real-time devices, is MIT-licensed.
Also note: if you're not giving your device to anyone (paid or not), but are keeping it to yourself, there's no differences.
Further, note that in the world of hardware description languages (e.g. Verilog, VHDL), things are a bit fuzzy when it comes to the effects of GPL.
add a comment
|
You're asking this from an electrical engineer's perspective, which puts all this in the context of building electronic devices and handing them to other people.
It's very simple: If you give anybody a device with GPL software on it, you must offer the source code at no additional expense (aside from the physical cost of copying the source code, which should be effectively zero these days) to them, especially including all your modification to it, and all the build infrastructure needed to build that software.
MIT doesn't require that.
Both licenses require you to let the receiver of the device including the software know that the software is licensed under MIT or GPL terms.
GPL is more "dispersive": when you write software that builds upon GPL code (e.g. you use a GPL library to calculate coordinates), that software becomes copyleft, too, and you'll need to also offer that software's source code to the receiver of the device.
Notice that there are multiple versions, especially of the GPL, and some contain specific exceptions. So, you need to make an individual case for each.
Generally, most complex embedded consumer devices you know run a lot of Free & Open Source Software – for example, the Linux kernel powering both your Android phone and probably your airplane seat TV and quite likely your internet router and … is GPL'ed. Your smart TV contains probably copious amounts of LGPL, MIT, Apache licensed code. The Arduino Platform itself is LGPL/GPL. The arm mbed operating system, which is relatively popular in IoT devices, is Apache Licensed; FreeRTOS, one of the very most popular emdedded operating systems for smaller, real-time devices, is MIT-licensed.
Also note: if you're not giving your device to anyone (paid or not), but are keeping it to yourself, there's no differences.
Further, note that in the world of hardware description languages (e.g. Verilog, VHDL), things are a bit fuzzy when it comes to the effects of GPL.
add a comment
|
You're asking this from an electrical engineer's perspective, which puts all this in the context of building electronic devices and handing them to other people.
It's very simple: If you give anybody a device with GPL software on it, you must offer the source code at no additional expense (aside from the physical cost of copying the source code, which should be effectively zero these days) to them, especially including all your modification to it, and all the build infrastructure needed to build that software.
MIT doesn't require that.
Both licenses require you to let the receiver of the device including the software know that the software is licensed under MIT or GPL terms.
GPL is more "dispersive": when you write software that builds upon GPL code (e.g. you use a GPL library to calculate coordinates), that software becomes copyleft, too, and you'll need to also offer that software's source code to the receiver of the device.
Notice that there are multiple versions, especially of the GPL, and some contain specific exceptions. So, you need to make an individual case for each.
Generally, most complex embedded consumer devices you know run a lot of Free & Open Source Software – for example, the Linux kernel powering both your Android phone and probably your airplane seat TV and quite likely your internet router and … is GPL'ed. Your smart TV contains probably copious amounts of LGPL, MIT, Apache licensed code. The Arduino Platform itself is LGPL/GPL. The arm mbed operating system, which is relatively popular in IoT devices, is Apache Licensed; FreeRTOS, one of the very most popular emdedded operating systems for smaller, real-time devices, is MIT-licensed.
Also note: if you're not giving your device to anyone (paid or not), but are keeping it to yourself, there's no differences.
Further, note that in the world of hardware description languages (e.g. Verilog, VHDL), things are a bit fuzzy when it comes to the effects of GPL.
You're asking this from an electrical engineer's perspective, which puts all this in the context of building electronic devices and handing them to other people.
It's very simple: If you give anybody a device with GPL software on it, you must offer the source code at no additional expense (aside from the physical cost of copying the source code, which should be effectively zero these days) to them, especially including all your modification to it, and all the build infrastructure needed to build that software.
MIT doesn't require that.
Both licenses require you to let the receiver of the device including the software know that the software is licensed under MIT or GPL terms.
GPL is more "dispersive": when you write software that builds upon GPL code (e.g. you use a GPL library to calculate coordinates), that software becomes copyleft, too, and you'll need to also offer that software's source code to the receiver of the device.
Notice that there are multiple versions, especially of the GPL, and some contain specific exceptions. So, you need to make an individual case for each.
Generally, most complex embedded consumer devices you know run a lot of Free & Open Source Software – for example, the Linux kernel powering both your Android phone and probably your airplane seat TV and quite likely your internet router and … is GPL'ed. Your smart TV contains probably copious amounts of LGPL, MIT, Apache licensed code. The Arduino Platform itself is LGPL/GPL. The arm mbed operating system, which is relatively popular in IoT devices, is Apache Licensed; FreeRTOS, one of the very most popular emdedded operating systems for smaller, real-time devices, is MIT-licensed.
Also note: if you're not giving your device to anyone (paid or not), but are keeping it to yourself, there's no differences.
Further, note that in the world of hardware description languages (e.g. Verilog, VHDL), things are a bit fuzzy when it comes to the effects of GPL.
edited Jun 2 at 19:05
MadHatter♦
13.4k1 gold badge25 silver badges52 bronze badges
13.4k1 gold badge25 silver badges52 bronze badges
answered Jun 2 at 10:18
Marcus MüllerMarcus Müller
2061 silver badge4 bronze badges
2061 silver badge4 bronze badges
add a comment
|
add a comment
|
Thanks for contributing an answer to Open Source Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fopensource.stackexchange.com%2fquestions%2f8365%2fmit-vs-gnu-licences-for-embedded-system-projects%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
When speaking of computer programs, "code" is always singular. "Codes" are the things you use to open a combination lock or to encrypt secret messages.
– JRE
Jun 2 at 10:13
… or to add information to allow for forward error correction (channel codes), or to make a digital data stream transportable reliably over a physical cable (line codes).
– Marcus Müller
Jun 2 at 10:22