Return-path: Received: from static-ip-62-75-166-246.inaddr.intergenia.de ([62.75.166.246]:46466 "EHLO vs166246.vserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753205AbXDEQrz (ORCPT ); Thu, 5 Apr 2007 12:47:55 -0400 From: Michael Buesch To: Marcus Glocker Subject: Re: OpenBSD bcw: Possible GPL license violation issues Date: Thu, 5 Apr 2007 18:47:05 +0200 Cc: Marcus Glocker , Jon Simola , Theo de Raadt , Stefano Brivio , Martin Langer , Danny van Dyk , Andreas Jaggi , Larry Finger , Quaker.Fang@sun.com, Johannes Berg , Joseph Jezak , John Linville , Greg kh , bcm43xx-dev@lists.berlios.de, linux-wireless@vger.kernel.org, license-violation@gpl-violations.org References: <200704041945.21447.mb@bu3sch.de> <20070405054107.GB7660@gollum.nazgul.ch> In-Reply-To: <20070405054107.GB7660@gollum.nazgul.ch> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Message-Id: <200704051847.05778.mb@bu3sch.de> Sender: linux-wireless-owner@vger.kernel.org List-ID: On Thursday 05 April 2007 07:41, Marcus Glocker wrote: > I wanted to make some quick progress (maybe too quick), and rewrite > the functions in question after seeing some first success, e.g. > receivment of first frames, which isn't the case right now. But > still, the specs for some functions are so strict, writing tons > of registers in a strict order, some parts will still look similar. To make it clear. We are not issueing any copyright claims on these magic register sequences. This is only about algorithms and so on. I mentioned the LO state machine, for example. > The last thing I want is to start a license war with you guys, > and also I don't want to harm OpenBSD further with this issue. > And of course we want to solve that license issue ASAP. > > So, I am suggestion three options: > > 1. You give me some time and I try to rewrite the code > in question. We keep in touch, and maybe we can split > up both parties in freedom afterwards. > > 2. Same as option one, but if my time resources keep > shrinking like they do right now, spending weekends > in the office and I can't fix up the driver soon, > I'll drop the driver. > > 3. We don't come to a point and I'll plain drop the driver > directly, very soon. 4. bcm43xx people review the driver and think about relicensing (parts of) bcw, so you don't have to rewrite it. We don't want to distrurb bcw development, but we don't like the harsh way of taking code without permission and asking for permission afterwards. If you want to have more code relicensed, please ask on a case-by-case base _before_ importing it into bcw. -- Greetings Michael.