From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264138AbUEXI7o (ORCPT ); Mon, 24 May 2004 04:59:44 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264186AbUEXI62 (ORCPT ); Mon, 24 May 2004 04:58:28 -0400 Received: from zeus.kernel.org ([204.152.189.113]:37541 "EHLO zeus.kernel.org") by vger.kernel.org with ESMTP id S264197AbUEXIty (ORCPT ); Mon, 24 May 2004 04:49:54 -0400 Date: Mon, 24 May 2004 04:49:45 -0400 From: "Luis R. Rodriguez" To: linux-kernel@vger.kernel.org, netdev@oss.sgi.com Cc: prism54-devel@prism54.org Subject: RFC: Network Device Driver Group proposal Message-ID: <20040524084945.GP3330@ruslug.rutgers.edu> Reply-To: "Luis R. Rodriguez" Mail-Followup-To: linux-kernel@vger.kernel.org, netdev@oss.sgi.com, prism54-devel@prism54.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="UIrAl4r1g2eOkvhC" Content-Disposition: inline User-Agent: Mutt/1.3.28i X-Operating-System: 2.4.18-1-686 Organization: Rutgers University Student Linux Users Group Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org --UIrAl4r1g2eOkvhC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable This is a RFC for the start of a Network Device Driver Group. There is currently no central group that I am aware of that=20 hardware/chipset manufacturer companies can contact to assist in=20 writing/mantaining/giving specs to/giving source base for a=20 new Linux Network device driver (wireless or not).=20 There is also no central group I know of besides the netdev mailing list for interaction between network driver developers. Most drivers seem to have their own mailing list, if any, and a cheesy website, if any. =46rom my experience so far it seems like manufacturers can sometimes be very willing to help, but I think that sometimes they just fail to see where and how they can help. So, it seems we have to first help ourselves out, building an entity onto which companies/manufacuters can refer to if they'd like to donate a source base for a driver / a firmware for a driver or even provide specifications for a driver. Sort of like an organizational structure like the DRI project. Just wanted to throw ideas in the air and see if other netdevs agree and think this would be a good idea. I've been speaking to Pavel Roskin,=20 a co-mantainer of the orinoco driver, and he agrees there many ways in which just both of our projects can benefit from a close relationship (in our case since our chipset's manufacturer is the same; prism 2/2.5.3 and prism gt/duette/indigo). OSLD wants to be the "center of gravity for all Linux related stuff". Well maybe OSDL can help us :) --=20 GnuPG Key fingerprint =3D 113F B290 C6D2 0251 4D84 A34A 6ADD 4937 E20A 525E --UIrAl4r1g2eOkvhC Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAsbcpat1JN+IKUl4RAjjvAJ9Y7uY1+yVeQ1xVM/Mo/PPam6Us6ACeOUaL obTD20dbsequFGew7w5Gb4M= =ysCn -----END PGP SIGNATURE----- --UIrAl4r1g2eOkvhC--