From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752910AbYL3LFw (ORCPT ); Tue, 30 Dec 2008 06:05:52 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751729AbYL3LFj (ORCPT ); Tue, 30 Dec 2008 06:05:39 -0500 Received: from rhlx01.hs-esslingen.de ([129.143.116.10]:51110 "EHLO rhlx01.hs-esslingen.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751561AbYL3LFi (ORCPT ); Tue, 30 Dec 2008 06:05:38 -0500 Date: Tue, 30 Dec 2008 12:05:36 +0100 From: Andreas Mohr To: Johannes Berg Cc: Andrew Morton , Andreas Mohr , David Miller , torvalds@linux-foundation.org, bunk@kernel.org, Jeff Kirsher , auke-jan.h.kok@intel.com, e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [GIT]: Networking Message-ID: <20081230110536.GA15907@rhlx01.hs-esslingen.de> Reply-To: andi@lisas.de References: <20081228.000118.121541932.davem@davemloft.net> <20081229102515.GA17171@rhlx01.hs-esslingen.de> <20081229091728.d869f1c1.akpm@linux-foundation.org> <1230584983.3116.71.camel@johannes> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1230584983.3116.71.camel@johannes> X-Priority: none User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On Mon, Dec 29, 2008 at 10:09:43PM +0100, Johannes Berg wrote: > On Mon, 2008-12-29 at 09:17 -0800, Andrew Morton wrote: > > > > - acx100 (ok, that one is a bit mean to add to this list ;) > > > > What's that? > > > > Just resend everything, please, fulyl changelogged, with all necessary > > cc's. > > acx100 is legally challenged. We don't want to see it without a clear > and full indication by the authors that they can guarantee that it was > written without any copyrighted Texas Instruments material. Which > they've never bothered to provide. True (and fully agreed), but then that particular entry was just meant to stir up some fog, I didn't really intend to focus on it at all ;) The project was based on non-clean-room reverse-engineering from the get-go anyway (5 people working for 3 months), thus the only way to get this unfortunate hardware non-support situation resolved would be by trying to get TI (or possibly newer holders of that technology) to extend its specifications/firmware blessing to older variants, not just the Android device-related chipsets supported by their new driver which they now provided, thankfully. Andreas Mohr