From owner-freebsd-hackers  Mon Apr 10 20:04:03 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id UAA05842
          for hackers-outgoing; Mon, 10 Apr 1995 20:04:03 -0700
Received: from victor.innovus.com (victor.innovus.com [192.75.186.54])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id UAA05828
          for <hackers@freefall.cdrom.com>; Mon, 10 Apr 1995 20:03:44 -0700
Received: (from martin@localhost) by victor.innovus.com (8.6.11/8.6.9) id XAA06229; Mon, 10 Apr 1995 23:11:05 -0400
From: Martin Renters <martin@victor.innovus.com>
Message-Id: <199504110311.XAA06229@victor.innovus.com>
Subject: Re: netboot for each card?
To: babkin@hq.icb.chel.su (Serge A. Babkin)
Date: Mon, 10 Apr 1995 23:11:04 -0400 (EDT)
Cc: hackers@freefall.cdrom.com
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Content-Length: 1286      
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

I spent some time looking at how to fix the Makefile to build a version of
netboot for each type of card we support.  I looked through ether.c (actually
while trying to fix some breakage that occured to the SMC driver
during the 3C509 additions) and came to the conclusion that probably the
best approach is to separate out the two drivers and put each one in
its own source file.  (8390 boards in ns8390.c and 3c509 in 3c509.c)

Once that is done we can build a version of netboot that supports all the 8390
based cards and one that works on the 3C509 (with possible later additions
for the DEC chipset based boards).

What I would like to do is put all the ethernet specific code in the
source file for that driver.  Currently, the 3c503 driver has some ifdefs
in main.c and bootmenu.c to deal with the transceiver.  I'd like to remove
ifdefs and make 'trans' a standard command.  As far as the eth_fillname
function goes, I'd like to change that into a string defined by each driver.
Thus the ns8390 driver will declare

	char eth_driver[]="ed0";

and the 3c509 will declare

	char eth_driver[]="ep0";

I'd be willing to do the ns8390 based boards, and hopefully Serge will
take the 3c509 driver.  (If not I can look at that one too since I now
have access to those boards.)

Martin