From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264682AbTF0TRn (ORCPT ); Fri, 27 Jun 2003 15:17:43 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264689AbTF0TRn (ORCPT ); Fri, 27 Jun 2003 15:17:43 -0400 Received: from x35.xmailserver.org ([208.129.208.51]:9640 "EHLO x35.xmailserver.org") by vger.kernel.org with ESMTP id S264682AbTF0TRm (ORCPT ); Fri, 27 Jun 2003 15:17:42 -0400 X-AuthUser: davidel@xmailserver.org Date: Fri, 27 Jun 2003 12:30:22 -0700 (PDT) From: Davide Libenzi X-X-Sender: davide@bigblue.dev.mcafeelabs.com To: Michael Kimberlin cc: linux-kernel@vger.kernel.org Subject: Re: bcm4306 revisited In-Reply-To: <20030627181858.C64A4BAF8A@www.molandernet.com> Message-ID: References: <20030627181858.C64A4BAF8A@www.molandernet.com> 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 On Fri, 27 Jun 2003, Michael Kimberlin wrote: > I know that the subject of drivers for this broadcom chipset has been > raised before. But, what information is missing that prevents the > development of these drivers? Perhaps a little social engineering is in > order... I mean, this chipset has been out for a while and there don't > seem to be any signs of development (h3ll, if we poke at it long enough > we'll get it) for this chipset. is there just a lack of ambition here, or > is there something REAL keeping this from going forth. I mean, I'm having > to write this email from windows just because this driver doesn't > exist...and that brings me great sadness... > > Any, thoughts? I'm sorry if I have missed something obvious here...I'm no > driver developer...so, my understanding of the situation may be off. But, > h3ll...I'm motivated... ;) http://www.petitiononline.com/BCM4301/ - Davide