1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
|
# This is the config file for creating Makefile rules for Etherboot ROMs
#
# To make a ROM for a supported NIC locate the appropriate family
# and add a line of the form
#
# ROM PCI-IDs Comment
#
# ROM is the desired output name for both .rom and .lzrom images.
# PCI IDs are the PCI vendor and device IDs of the PCI NIC
# For ISA NICs put -
#
# All PCI ROMs that share a single driver are only built once (because they
# only have different PCI-IDs, but identical code). ISA ROMS are built for
# each ROM type, because different vendors used a different logic around the
# basic chip. The most popular example is the NS8390, which some cards use
# in PIO mode, some in DMA mode. Two chips currently don't fit into this nice
# black-and-white scheme (the Lance and the NS8390). Their driver deals
# with both PCI and ISA cards. These drivers will be treated similarly to
# ISA only drivers by genrules.pl and are compiled for each ROM type that is
# ISA, and additionally compiled for the PCI card type.
#
# Then do: make clean, make Roms and make
#
# Please send additions to this file to <kenUNDERSCOREyap AT users PERIOD sourceforge PERIOD net>
# Start of configuration
family drivers/net/skel
family arch/ia64/drivers/net/undi_nii
undi_nii -
# 3c59x cards (Vortex) and 3c900 cards
# If your 3c900 NIC detects but fails to work, e.g. no link light, with
# the 3c90x driver, try using the 3c595 driver. I have one report that the
# 3c595 driver handles these NICs properly. (The 595 driver uses the
# programmed I/O mode of operation, whereas the 90x driver uses the bus
# mastering mode. These NICs are capable of either mode.) When it comes to
# making a ROM, as usual, you must choose the correct image, the one that
# contains the same PCI IDs as your NIC.
family drivers/net/3c595
# 3Com 3c90x cards
family drivers/net/3c90x
# Intel Etherexpress Pro/100
family drivers/net/eepro100
#Intel Etherexpress Pro/1000
family drivers/net/e1000
#Broadcom Tigon 3
family drivers/net/tg3
family drivers/net/pcnet32
# National Semiconductor ns83820 (Gigabit) family
family drivers/net/ns83820
family drivers/net/tulip
family drivers/net/davicom
family drivers/net/rtl8139
family drivers/net/r8169
family drivers/net/via-rhine
family drivers/net/w89c840
family drivers/net/sis900
family drivers/net/natsemi
family drivers/net/prism2_plx
family drivers/net/prism2_pci
# Various Prism2.5 (PCI) devices that manifest themselves as Harris Semiconductor devices
# (with the actual vendor appearing as the vendor of the first subsystem)
hwp01170 0x1260,0x3873 ActionTec HWP01170
dwl520 0x1260,0x3873 DLink DWL-520
family drivers/net/ns8390
wd - WD8003/8013, SMC8216/8416, SMC 83c790 (EtherEZ)
ne - NE1000/2000 and clones
3c503 - 3Com503, Etherlink II[/16]
family drivers/net/epic100
family drivers/net/3c509
3c509 - 3c509, ISA/EISA
3c529 - 3c529 == MCA 3c509
family drivers/net/3c515
3c515 - 3c515, Fast EtherLink ISA
family drivers/net/eepro
eepro - Intel Etherexpress Pro/10
family drivers/net/cs89x0
cs89x0 - Crystal Semiconductor CS89x0
family drivers/net/depca
depca - Digital DE100 and DE200
family drivers/net/forcedeth
family drivers/net/sk_g16
sk_g16 - Schneider and Koch G16
family drivers/net/smc9000
smc9000 - SMC9000
family drivers/net/sundance
family drivers/net/tlan
family drivers/disk/ide_disk
ide_disk 0x0000,0x0000 Generic IDE disk support
family drivers/disk/pc_floppy
family arch/i386/drivers/net/undi
undi 0x0000,0x0000 UNDI driver support
family drivers/net/pnic
family arch/armnommu/drivers/net/p2001_eth
family drivers/net/mtd80x
family drivers/net/dmfe
|
