Date: Thu, 17 Feb 2005 17:13:04 -0600
From: parker@citynetwireless.net
To: arjan@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: Please open sysfs symbols to proprietary modules
Message-ID: <20050217231304.GA18940@core.citynetwireless.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.28i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1104
Lines: 21

On Thu, 03 Feb 2005 09:41:00 +0100, Arjan van de Ven <arjan@infradead.org> wrote:
> On Wed, 2005-02-02 at 17:56 -0500, Pavel Roskin wrote:
> > Hello!
> >
> > I'm writing a module under a proprietary license.  I decided to use sysfs
> > to do the configuration.  Unfortunately, all sysfs exports are available
> > to GPL modules only because they are exported by EXPORT_SYMBOL_GPL.
> 
> I suggest you talk to a lawyer and review the general comments about
> binary modules with him (http://people.redhat.com/arjanv/COPYING.modules
> for example). You are writing an addition to linux from scratch, and it
> is generally not considered OK to do that in binary form (I certainly do
> not consider it OK).

So what about companies like ImageStream who write proprietary Linux network
drivers for their hardware from scratch with no previous ports from another OS?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/