Lines Matching refs:the

11 This file describes how to use the DM9000 platform-device based network driver
12 that is contained in the files drivers/net/dm9000.c and drivers/net/dm9000.h.
14 The driver supports three DM9000 variants, the DM9000E which is the first chip
15 supported as well as the newer DM9000A and DM9000B devices. It is currently
20 Defining the platform device
23 The minimum set of resources attached to the platform device are as follows:
25     1) The physical address of the address register
26     2) The physical address of the data register
27     3) The IRQ line the device's interrupt pin is connected to.
29 These resources should be specified in that order, as the ordering of the
30 two address regions is important (the driver expects these to be address
60 Note the setting of the IRQ trigger flag in bast_dm9k_resource[2].flags,
62 the flags field will be passed to request_irq() when registering the IRQ
63 handler to ensure that the IRQ is setup correctly.
65 This shows a typical platform device, without the optional configuration
66 platform data supplied. The next example uses the same resources, but adds
67 the optional platform data to pass extra configuration data:
89 Extra platform data for the DM9000 can describe the IO bus width to the
90 device, whether or not an external PHY is attached to the device and
91 the availability of an external configuration EEPROM.
93 The flags for the platform data .flags field are as follows:
113 	This can be used to signify that the board does not have an
114 	EEPROM, or that the EEPROM should be hidden from the user.
118 	Switch to using the simpler PHY polling method which does not
119 	try and read the MII PHY state regularly. This is only available
120 	when using the internal PHY. See the section on link state polling
131 The driver keeps track of the link state and informs the network core
133 depending on the version of the chip and on which PHY is being used.
135 For the internal PHY, the original (and currently default) method is
136 to read the MII state, either when the status changes if we have the
137 necessary interrupt support in the chip or every two seconds via a
140 To reduce the overhead for the internal PHY, there is now the option
141 of using the DM9000_FORCE_SIMPLE_PHY_POLL config, or DM9000_PLATF_SIMPLE_PHY
142 platform data option to read the summary information without the
146 When using an external PHY, the driver currently has to poll the MII
153 These chips are functionally similar to the DM9000E and are supported easily
154 by the same driver. The features are:
156    1) Interrupt on internal PHY state change. This means that the periodic
157       polling of the PHY status may be disabled on these devices when using
158       the internal PHY.
160    2) TCP/UDP checksum offloading, which the driver does not currently support.
166 The driver supports the ethtool interface for access to the driver
167 state information, the PHY state and the EEPROM.