From owner-freebsd-hackers Wed Nov 15 07:41:13 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA12613 for hackers-outgoing; Wed, 15 Nov 1995 07:41:13 -0800 Received: from fang.cs.sunyit.edu (fang.cs.sunyit.edu [192.52.220.66]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id HAA12602 for ; Wed, 15 Nov 1995 07:41:09 -0800 From: chuck@fang.cs.sunyit.edu Received: (from chuck@localhost) by fang.cs.sunyit.edu (8.6.9/8.6.9) id KAA25999 for hackers@freebsd.org; Wed, 15 Nov 1995 10:41:07 -0500 Date: Wed, 15 Nov 1995 10:41:07 -0500 Message-Id: <199511151541.KAA25999@fang.cs.sunyit.edu> X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: hackers@freebsd.org Subject: Device drivers Sender: owner-hackers@freebsd.org Precedence: bulk I have access to a Etherlink III PCI 3C590 Ethernet card and a Intel EtherExpress PRO/100 LAN Adapter (actually they sit in a drawer collecting dust :). I understand that there is a driver in -current for the 3C590 but I also understand that it doesn't take advantage of the full capabilities of the card (which capabilities I'm not clear on because I'm not an expert on this card). Anyhow, I'd be more than willing to spend a little time trying to write drivers for these cards (or testing other people's if they are already working on them). However, I have very little experience writing drivers for FreeBSD and would like advice on how to accomplish my goal. For example, how to properly debug the driver, where I might get programming hints or spec.s for the two cards, or any other related information I should know. I'd even appreciate any examples of how other people went about writing other device drivers. -- Charles Green UN*X System Administration 22 Powell Ave. Apt. B UN*X Security & Whitesboro, NY 13492 Programming