Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932601AbWLNLSF (ORCPT ); Thu, 14 Dec 2006 06:18:05 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932598AbWLNLSE (ORCPT ); Thu, 14 Dec 2006 06:18:04 -0500 Received: from outpipe-village-512-1.bc.nu ([81.2.110.250]:45944 "EHLO lxorguk.ukuu.org.uk" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S932566AbWLNLSB (ORCPT ); Thu, 14 Dec 2006 06:18:01 -0500 Date: Thu, 14 Dec 2006 11:25:35 +0000 From: Alan To: David Woodhouse Cc: Linus Torvalds , Greg KH , Jonathan Corbet , Andrew Morton , Martin Bligh , "Michael K. Edwards" , linux-kernel@vger.kernel.org Subject: Re: GPL only modules [was Re: [GIT PATCH] more Driver core patches for 2.6.19] Message-ID: <20061214112535.16ee7708@localhost.localdomain> In-Reply-To: <1166084480.5253.849.camel@pmac.infradead.org> References: <20061214003246.GA12162@suse.de> <22299.1166057009@lwn.net> <20061214005532.GA12790@suse.de> <1166084480.5253.849.camel@pmac.infradead.org> X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1841 Lines: 40 On Thu, 14 Dec 2006 08:21:20 +0000 David Woodhouse wrote: > If they fail to do that under the 'honour system' then I'm not averse to > 'enforcing' it by technical measures. (For some value of 'enforcement' > which is easy for them to patch out if their lawyers are _really_ sure > they'll win when I sue them, that is.) There are specific rules against removal of technical measures *even if the result is legal*. It is an offence in many countries thanks to the RIAA lobbyists and their corrupt pet politicians to remove technical measures applied to a -public domain- work. So your argument doesn't fly. > Not on my part. The thing that makes me _particularly_ vehement about > binary-only crap this week is a very much a technical issue -- in > particular, the fact that we had to do post-production board > modifications to shoot our wireless chip in the head when it goes AWOL, > because the code for it wasn't available to us. Consider it an education process. Hopefully the contracts for the chips/docs were watertight enough you can sue the offending supplier for the total cost of the rework. If not then you are really complaining about getting contract negotiations wrong. > It's better to have a coherent approach, and for all of us to do it on > roughly the same timescale. Getting the distributions do so this is > going to be like herding cats -- having it upstream and letting it > trickle down is a much better approach, I think. I doubt any distribution but the FSF "purified" Debian (the one that has no firmware so doesn't work) would do it. Alan - 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/