mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@studorgs.rutgers.edu>
To: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Cc: prism54-devel@prism54.org
Subject: RFC: Network Device Driver Group proposal
Date: Mon, 24 May 2004 04:49:45 -0400	[thread overview]
Message-ID: <20040524084945.GP3330@ruslug.rutgers.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 1592 bytes --]


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 
hardware/chipset manufacturer companies can contact to assist in 
writing/mantaining/giving specs to/giving source base for a 
new Linux Network device driver (wireless or not). 

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.

From 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, 
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 :)

-- 
GnuPG Key fingerprint = 113F B290 C6D2 0251 4D84  A34A 6ADD 4937 E20A 525E

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

                 reply	other threads:[~2004-05-24  8:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040524084945.GP3330@ruslug.rutgers.edu \
    --to=mcgrof@studorgs.rutgers.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    --cc=prism54-devel@prism54.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®