Return-path: Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:37335 "EHLO sunset.davemloft.net" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1760023AbXGYAfa (ORCPT ); Tue, 24 Jul 2007 20:35:30 -0400 Date: Tue, 24 Jul 2007 17:35:29 -0700 (PDT) Message-Id: <20070724.173529.48529759.davem@davemloft.net> To: Stephen.Clark@seclark.us Cc: jeff@garzik.org, jketreno@linux.intel.com, axjslack@bluebottle.com, linux-wireless@vger.kernel.org, ipw3945-devel@lists.sourceforge.net Subject: Re: [ipw3945-devel] Request for help... From: David Miller In-Reply-To: <46A69998.7020108@seclark.us> References: <46A6A447.2080903@linux.intel.com> <46A69359.4030201@garzik.org> <46A69998.7020108@seclark.us> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Sender: linux-wireless-owner@vger.kernel.org List-ID: From: Stephen Clark Date: Tue, 24 Jul 2007 20:30:16 -0400 > I find it really sad that a hardware vendor that is willing to write > and develope drivers for Linux for their hardware aren't helped more > by "the community" or is the "the community" only interested in > hacking drivers where the manufacturer give no or minimal support? This is a massive mischaracterization of reality. I agree with every statement Jeff has made, Intel really is a problem child in this area, and consistently so. The only way we could "help them" more is to take over the code base and do the development for them. The thing you should find truly sad is how Intel handles these situations time and time again, rather than the tireless attempts of Jeff and others to education them on how to improve the situation.