From owner-freebsd-hackers  Thu Jul 31 04:34:29 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id EAA00597
          for hackers-outgoing; Thu, 31 Jul 1997 04:34:29 -0700 (PDT)
Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id EAA00580
          for <hackers@freebsd.org>; Thu, 31 Jul 1997 04:34:23 -0700 (PDT)
Received: from x14.mi.uni-koeln.de (annexr3-6.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA15494
  (5.67b/IDA-1.5 for <hackers@FreeBSD.ORG>); Thu, 31 Jul 1997 13:33:50 +0200
Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.6/8.6.9) id NAA14572; Thu, 31 Jul 1997 13:33:40 +0200 (CEST)
X-Face: "<d]#=8pzx);RzeqSKI86OVa7=!0/(uRa.+B.9Z9\eNUn@UG?!`y7yt2dFNn%k4'.}](uE%
 yCO)$e&Y1%3EO~ifu6Q-#YUM&JZ't,}JkPnAz,8Dj33u%@GBi%[Y#LHz$]h7a<p4)-jKI7~sKjlP-^
 EvA[G;]v&0]W!EL%shs,{7x0|oqN4YVIs5,NI#,V{9"WF):5&RkOhyj*#-IAG}Tnu;YCF,d
Message-Id: <19970731133340.35670@mi.uni-koeln.de>
Date: Thu, 31 Jul 1997 13:33:40 +0200
From: Stefan Esser <se@FreeBSD.ORG>
To: Jim Durham <durham@w2xo.pgh.pa.us>
Cc: hackers@FreeBSD.ORG
Subject: Re: Generic PCI ethernet card
References: <33E001D9.446B9B3D@w2xo.pgh.pa.us>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.74
In-Reply-To: <33E001D9.446B9B3D@w2xo.pgh.pa.us>; from Jim Durham on Wed, Jul 30, 1997 at 11:09:13PM -0400
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Jul 30, Jim Durham <durham@w2xo.pgh.pa.us> wrote:
> I have a "generic" (read "cheap") PCI ethernet
> card here that purports to be able to use the
> NE2000 driver.
> 
> I notice when I boot the system that the PCI stuff
> is all OK, but, apparently, the ID code on the card
> is not recognized, and no driver is assigned.
> 
> Is this just a matter of adding the ID code to
> the driver in if_ed_p.c, where it lists RealTek 8029,
> ProLan, and etc...and I guess I have to boot the
> system and see what code is returned...or am I off
> on the wrong path? Also, how does the system know to
> even have if_ed_p.c scan for a code if it doesn't know
> what kind of card it is dealing with? Is this handed
> down from the bios? Lotsa questions...

Please send a boot message log
and information on the name the
card is sold under. I'll send a
patch and will add the device ID 
to -current.

For the -current PCI code I plan
to allow assigning drivers to PCI
devices that could not be identified.
(I.e. your card would show up in the
user config screen with a "no driver"
flag, and you could assign "ed" to it,
or, say, "ed4" if you care for the unit 
number.)

Regards, STefan