<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Embedded on remixware.com</title>
    <link>https://remixware.com/tags/embedded/</link>
    <description>Recent content in Embedded on remixware.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 26 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://remixware.com/tags/embedded/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>GPL 2 Firmware and the Apache Code That Cannot Go In</title>
      <link>https://remixware.com/gpl-2-firmware-and-the-apache-code-that-cannot-go-in/</link>
      <pubDate>Mon, 26 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://remixware.com/gpl-2-firmware-and-the-apache-code-that-cannot-go-in/</guid>
      <description>&lt;p&gt;A lot of firmware is licensed under GPL version 2, because it&amp;rsquo;s built on Linux, BusyBox or U-Boot, and a lot of it says &amp;ldquo;version 2 only&amp;rdquo;. That choice shuts out more code than people expect. Apache 2.0 code can&amp;rsquo;t go in, even though Apache is permissive. GPL version 3 code can&amp;rsquo;t go in either, even though it&amp;rsquo;s the GPL. The same Apache code would be fine in an MIT product and the GPL-3.0 code in a GPL-3.0 one, so a function that&amp;rsquo;s harmless in one of your products can be a problem in another.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
