From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264695AbTF0TF0 (ORCPT ); Fri, 27 Jun 2003 15:05:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264730AbTF0TFZ (ORCPT ); Fri, 27 Jun 2003 15:05:25 -0400 Received: from SP1-24.207.216.92.charter-stl.com ([24.207.216.92]:60815 "EHLO www.molandernet.com") by vger.kernel.org with ESMTP id S264695AbTF0TFX (ORCPT ); Fri, 27 Jun 2003 15:05:23 -0400 Date: Fri, 27 Jun 2003 23:58:18 -0500 (Central Standard Time) From: Michael Kimberlin Subject: bcm4306 revisited To: linux-kernel@vger.kernel.org MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Mailer: Mahogany 0.64.1 'Sparc', running under Windows NT 5.1 (build 2600, Service Pack 1) Message-Id: <20030627181858.C64A4BAF8A@www.molandernet.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org 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... ;) -michael -- Join the Anti-.htm Revolution!!!