<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Linux Infusion</title>
  <subtitle>Infuse yourself with GNU/Linux</subtitle>
  <link rel="alternate" type="text/html" href="http://www.linuxinfusion.com/broadcom-driver-dispute"/>
  <link rel="self" type="application/atom+xml" href="http://www.linuxinfusion.com/node/71/atom/feed"/>
  <id>http://www.linuxinfusion.com/node/71/atom/feed</id>
  <updated>2007-04-07T10:13:11-07:00</updated>
  <entry>
    <title>The Broadcom Driver Dispute</title>
    <link rel="alternate" type="text/html" href="http://www.linuxinfusion.com/broadcom-driver-dispute" />
    <id>http://www.linuxinfusion.com/broadcom-driver-dispute</id>
    <published>2007-04-07T10:13:11-07:00</published>
    <updated>2007-04-07T10:13:11-07:00</updated>
    <author>
      <name>Moparx</name>
    </author>
    <category term="GPL" />
    <summary type="html"><![CDATA[<p>I was reading the fiasco that erupted out of the <a rel="external" href="http://thread.gmane.org/gmane.linux.kernel.wireless.general/1558" title="Read the thread" rel="nofollow" rel="nofollow">recent Broadcom driver dispute</a> and couldn't help but shake my head in disbelief.<br />
It was discovered that source code originating from the bcm43xx driver (licensed under the GPL) had been copied verbatim and committed into OpenBSD's own bcw driver.<br />
Michael Buesch, the lead developer of the bcm43xx project, sent a message regarding the GPL license violation in which he outlined some examples and even expressed some interest in cooperating with OpenBSD so that their own driver would be free of the before mentioned violations.<br />
However, things didn't go as smoothly as he had hoped. Theo De Raadt decided to focus on the fact that the issue was brought up on a public mailing list rather than the actual issues at hand.</p>
    ]]></summary>
  </entry>
</feed>
