Return-path: Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:38442 "EHLO sunset.davemloft.net" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1753211AbYAZNmK (ORCPT ); Sat, 26 Jan 2008 08:42:10 -0500 Date: Sat, 26 Jan 2008 05:42:23 -0800 (PST) Message-Id: <20080126.054223.118097210.davem@davemloft.net> (sfid-20080126_134219_198326_886E930C) To: inaky@linux.intel.com Cc: mb@bu3sch.de, torvalds@linux-foundation.org, johannes@sipsolutions.net, linville@tuxdriver.com, linux-wireless@vger.kernel.org Subject: Re: Linux 2.6.24-rc7 From: David Miller In-Reply-To: <200801251328.35985.inaky@linux.intel.com> References: <200801251311.45392.inaky@linux.intel.com> <200801252221.07558.mb@bu3sch.de> <200801251328.35985.inaky@linux.intel.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Sender: linux-wireless-owner@vger.kernel.org List-ID: From: Inaky Perez-Gonzalez Date: Fri, 25 Jan 2008 13:28:35 -0800 > For example: want to ship new firmware, drivers *and* full validation and > certification for a product that is already completed just to satisfy a > fraction of a market which is not part of the designed target? > > Do you know how much money that costs? I'm glad you guys are the only one's with access to the firmware source, thus enduring that you can constantly come up with reasons like this in order to not have to fix the problem. You know that if the source were available, the community would have fixed the bug ages ago. But the situation is entirely in Intel's control which is surely exactly the way they like it.