651b44e211
as with user-land programs, include files are installed by each directory
in the tree that has includes to install. (This allows more flexibility
as to what gets installed, makes 'partial installs' easier, and gives us
more options as to which machines' includes get installed at any given
time.) The old SYS_INCLUDES={symlinks,copies} behaviours are _both_
still supported, though at least one bug in the 'symlinks' case is
fixed by this change. Include files can't be build before installation,
so directories that have includes as targets (e.g. dev/pci) have to move
those targets into a different Makefile.
|
||
|---|---|---|
| .. | ||
| Makefile | ||
| Makefile.pcidevs | ||
| README | ||
| ahc_pci.c | ||
| bha_pci.c | ||
| cy_pci.c | ||
| devlist2h.awk | ||
| eap.c | ||
| files.pci | ||
| i82365_pci.c | ||
| if_de.c | ||
| if_devar.h | ||
| if_en_pci.c | ||
| if_ep_pci.c | ||
| if_epic_pci.c | ||
| if_esh_pci.c | ||
| if_fpa.c | ||
| if_fxp.c | ||
| if_fxpreg.h | ||
| if_fxpvar.h | ||
| if_le_pci.c | ||
| if_levar.h | ||
| if_ne_pci.c | ||
| if_tl.c | ||
| if_tlregs.h | ||
| isp_pci.c | ||
| ncr.c | ||
| ncrreg.h | ||
| ncrstat.c | ||
| pci.c | ||
| pci_map.c | ||
| pci_quirks.c | ||
| pci_subr.c | ||
| pcidevs | ||
| pcidevs.h | ||
| pcidevs_data.h | ||
| pciide.c | ||
| pciidereg.h | ||
| pciidevar.h | ||
| pcireg.h | ||
| pcivar.h | ||
| ppb.c | ||
| ppbreg.h | ||
| tga.c | ||
| tga_bt463.c | ||
| tga_bt485.c | ||
| tga_conf.c | ||
| tgareg.h | ||
| tgavar.h | ||
| vga_pci.c | ||
| vga_pcivar.h | ||
| wdc_pciide.c | ||
README
$NetBSD: README,v 1.2 1994/10/27 04:21:29 cgd Exp $ This directory contains files which are used during PCI configuration and PCI device drivers. Eventually, most of the device drivers and some of the configuration support should become machine-independent and be moved to a more general location. The configuration support was implemented according to the `PCI Local Bus Specification, Production Version, Revision 2.0' dated April 30, 1993. Section numbers referred to in the code may be specific to that edition of the specification. Some attempt has been made to insure that the code works on rogue machines where the BIOS doesn't do its job, but in general I can't guarantee that. -- - Charles Hannum NetBSD group August 8, 1994