DM9000网卡驱动分析.docVIP

DM9000网卡驱动分析 #include linux/module.h#include linux/ioport.h#include linux/netdevice.h#include linux/etherdevice.h#include linux/init.h#include linux/skbuff.h#include linux/spinlock.h#include linux/crc32.h#include linux/mii.h#include linux/ethtool.h#include linux/dm9000.h#include linux/delay.h#include linux/platform_device.h#include linux/irq.h #include asm/delay.h#include asm/irq.h#include asm/io.h #if defined(CONFIG_ARCH_S3C2410)#include mach/regs-mem.h#endif #include dm9000.h /* Board/System/Debug information/definition ---------------- *///在EEPROM或PHY地址寄存器中要选择内部PHY，那么7-6位强制为01#define DM9000_PHY??0x40?/* PHY address 0x01 */ #define CARDNAME?dm9000#define DRV_VERSION?1.31 /*?* Transmit timeout, default 5 seconds.?*/?//传输超时时间设定，当传输超时时调用函数dm9000_timeout(struct net_device *dev)static int watchdog = 5000;module_param(watchdog, int, 0400);//在驱动程序加载时可以重新设定watchdogMODULE_PARM_DESC(watchdog, transmit timeout in milliseconds); /* DM9000 register address locking.?*?* The DM9000 uses an address register to control where data written?* to the data register goes. This means that the address register?* must be preserved over interrupts or similar calls.?*?* During interrupt and other critical calls, a spinlock is used to?* protect the system, but the calls themselves save the address?* in the address register in case they are interrupting another?* access to the device.?*?* For general accesses a lock is provided so that calls which are?* allowed to sleep are serialised so that the address register does?* not need to be saved. This lock also serves to serialise access?* to the EEPROM and PHY access registers which are shared between?* these two devices.?*/ /* The driver supports the original DM9000E, and now the two newer?* devices, DM9000A and DM9000B.?*/ enum dm9000_type {?TYPE_DM9000E,?/* original DM9000 */?TYPE_DM9000A,?TYPE_DM9000B}; /* Structure/enum declaration ------------------------------- */typedef struct board_info {/