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 Message-ID: <19970731133340.35670@mi.uni-koeln.de> In-Reply-To: <33E001D9.446B9B3D@w2xo.pgh.pa.us>; from Jim Durham on Wed, Jul 30, 1997 at 11:09:13PM -0400 References: <33E001D9.446B9B3D@w2xo.pgh.pa.us>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970731133340.35670>