Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1764798AbXHFMZr (ORCPT ); Mon, 6 Aug 2007 08:25:47 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1763602AbXHFMZk (ORCPT ); Mon, 6 Aug 2007 08:25:40 -0400 Received: from khc.piap.pl ([195.187.100.11]:55657 "EHLO khc.piap.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752183AbXHFMZj (ORCPT ); Mon, 6 Aug 2007 08:25:39 -0400 To: "Nathan Williams" Cc: linux-kernel Subject: Re: MODULE_LICENSE usage References: From: Krzysztof Halasa Date: Mon, 06 Aug 2007 14:25:37 +0200 In-Reply-To: (Nathan Williams's message of "Mon, 6 Aug 2007 17:53:44 +1000") Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1120 Lines: 28 Hi, "Nathan Williams" writes: > I'm working on a driver for an ADSL modem which requires the use of a > binary library from the chipset manufacturer. Legal things aside, the practical solutions are: a) if the binary "library" is just firmware running on modem's CPU (outside the host CPU and address space), then you should just make it a file and use firmware_loader to load it to ADSL. Having "open" firmware is nice but not a hard requirement. b) if the binary blob is really a library to be run in kernel (host) space then there is no point in writing such driver - there are completely open-source drivers for ADSL devices and most (if not all) people will prefer them over any binary library. Perhaps you can convince the chipset manufacturer to open the source or publish the complete docs, but I wouldn't count on it. -- Krzysztof Halasa - 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/