68159c8901
- always use pci_conf_read() and pci_conf_write(). (This is required to simulate non-existant devices in my system for PCI bridge code tests.) - reorder some functions (put the main functions at the end). - correct off by one bug in the code dealing with unitialized PCI to PCI bridge chips. (Bug found by ASAMI Satoshi.) - print function number for multi-function devices. |
||
---|---|---|
.. | ||
aic7870.c | ||
bt9xx.c | ||
dc21040.h | ||
if_de.c | ||
if_fxp.c | ||
if_fxpreg.h | ||
if_pdq.c | ||
if_vx.c | ||
if_vxreg.h | ||
locate.pl | ||
meteor_reg.h | ||
meteor.c | ||
ncr.c | ||
ncrreg.h | ||
pci.c | ||
pcibus.h | ||
pcireg.h | ||
pcisupport.c | ||
pcivar.h | ||
pdq_os.h | ||
pdq.c | ||
pdqreg.h | ||
README.de | ||
README.de-le | ||
wd82371.c | ||
wd82371reg.h |
$Id: README.de-le,v 1.1 1994/10/01 20:16:44 wollman Exp $ ---------------- The enclosed drivers should be considered beta-test software. These drivers are in no way supported by Digital Equipment. See the disclaimers in the sources for more information. Please be aware that Digital does not employee me to write drivers for FreeBSD. This kit contains one driver: de DEC DE435 PCI NIC or compatible See README.de for information and installation instruction specific to this driver. Could you please send me the startup messages in the boot long along with the type of your PC once the driver configures? If you have any problems, comments, suggestions, rant or raves, don't hesitate to send me mail @ thomas@lkg.dec.com. Lastly, if you change or modify the code, I want context diffs of your changes. I want this to the canonical DEC EtherWORKS driver kit for FreeBSD, NetBSD, BSD/386, and any other BSD based O/S. Please make sure your diffs are approriate conditionalized. Thanks, Matt Thomas -- Mail: thomas@lkg.dec.com URL: http://ftp.digital.com/~thomas/