freebsd-dev/sys/pci/if_stereg.h

555 lines
16 KiB
C
Raw Normal View History

/*
* Copyright (c) 1997, 1998, 1999
* Bill Paul <wpaul@ctr.columbia.edu>. All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in the
* documentation and/or other materials provided with the distribution.
* 3. All advertising materials mentioning features or use of this software
* must display the following acknowledgement:
* This product includes software developed by Bill Paul.
* 4. Neither the name of the author nor the names of any co-contributors
* may be used to endorse or promote products derived from this software
* without specific prior written permission.
*
* THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
* ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD
* BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
* CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
* SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
* INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
* CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
* ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
* THE POSSIBILITY OF SUCH DAMAGE.
*
1999-08-28 01:08:13 +00:00
* $FreeBSD$
*/
/*
* Sundance PCI device/vendor ID for the
* ST201 chip.
*/
#define ST_VENDORID 0x13F0
#define ST_DEVICEID_ST201 0x0201
/*
* D-Link PCI device/vendor ID for the DFE-550TX.
*/
#define DL_VENDORID 0x1186
#define DL_DEVICEID_550TX 0x1002
/*
* Register definitions for the Sundance Technologies ST201 PCI
* fast ethernet controller. The register space is 128 bytes long and
* can be accessed using either PCI I/O space or PCI memory mapping.
* There are 32-bit, 16-bit and 8-bit registers.
*/
#define STE_DMACTL 0x00
#define STE_TX_DMALIST_PTR 0x04
#define STE_TX_DMABURST_THRESH 0x08
#define STE_TX_DMAURG_THRESH 0x09
#define STE_TX_DMAPOLL_PERIOD 0x0A
#define STE_RX_DMASTATUS 0x0C
#define STE_RX_DMALIST_PTR 0x10
#define STE_RX_DMABURST_THRESH 0x14
#define STE_RX_DMAURG_THRESH 0x15
#define STE_RX_DMAPOLL_PERIOD 0x16
#define STE_DEBUGCTL 0x1A
#define STE_ASICCTL 0x30
#define STE_EEPROM_DATA 0x34
#define STE_EEPROM_CTL 0x36
#define STE_FIFOCTL 0x3A
#define STE_TX_STARTTHRESH 0x3C
#define STE_RX_EARLYTHRESH 0x3E
#define STE_EXT_ROMADDR 0x40
#define STE_EXT_ROMDATA 0x44
#define STE_WAKE_EVENT 0x45
#define STE_TX_STATUS 0x46
#define STE_TX_FRAMEID 0x47
#define STE_COUNTDOWN 0x48
#define STE_ISR_ACK 0x4A
#define STE_IMR 0x4C
#define STE_ISR 0x4E
#define STE_MACCTL0 0x50
#define STE_MACCTL1 0x52
#define STE_PAR0 0x54
#define STE_PAR1 0x56
#define STE_PAR2 0x58
#define STE_MAX_FRAMELEN 0x5A
#define STE_RX_MODE 0x5C
#define STE_TX_RECLAIM_THRESH 0x5D
#define STE_PHYCTL 0x5E
#define STE_MAR0 0x60
#define STE_MAR1 0x62
#define STE_MAR2 0x64
#define STE_MAR3 0x66
#define STE_STATS 0x68
Fixes for the D-Link DFE-580 card. This is pretty much fixes any issue I can find: - Watchdog timeouts were due to starting the TX DMA engine before we had a packet ready for it. So the first packet sent never got out only if we sent more then one packet at a time did the others make it out and not blow up. Of course reseting the chip then caused us not to transmit the first packet again ie. catch-22. This required logic changes. - Combine interrupts on TX packets being queued up. - Don't keep running around the RX ring since we might get out of sync so only go around once per receive - Let the RX engine recover via the poll interface which is similar to the TX interface. This way the chip wakes up with no effort when we read enough packets. - Do better hand-shaking on RX & TX packets so they don't start of to soon. - Force a duplex setting when the link comes up after an ste_init or it will default to half-duplex and be really slow. This only happens on subsequent ste_init. The first one worked. - Don't call stat_update for every overflow. We only monitor the collisions so the tick interval is good enough for that. Just read in the collision stats to minimize bus reads. - Don't read the miibus every tick since it uses delays and delays are not good for performance. - Tie link events directly to the miibus code so the port gets set correctly if someone changes the port settings. - Reduce the extreme number of {R,T}FD's. They would consume 130K of kernel memory for each NIC. - Set the TX_THRESH to wait for the DMA engine to complete before running the TX FIFO. This hurts peak TX performance but under bi-directional load the DMA engine can't keep up with the FIFO. Testing shows that we end up in the case anyways (a la dc(4) issues but worse since the RX engine hogs everything). - When stopping the card do a reset since the reset verifies the card has stopped. Otherwise on heavy RX load the RX DMA engine is still stuffing packets into memory. If that happens after we free the DMA area memory bits get scribled in memory and bad things happen. This card still has seemingly unfixable issues under heavy RX load in which the card takes over the PCI bus. Sponsored by: Vernier Networks MFC after: 1 week
2002-08-07 22:31:27 +00:00
#define STE_LATE_COLLS 0x75
#define STE_MULTI_COLLS 0x76
#define STE_SINGLE_COLLS 0x77
#define STE_DMACTL_RXDMA_STOPPED 0x00000001
#define STE_DMACTL_TXDMA_CMPREQ 0x00000002
#define STE_DMACTL_TXDMA_STOPPED 0x00000004
#define STE_DMACTL_RXDMA_COMPLETE 0x00000008
#define STE_DMACTL_TXDMA_COMPLETE 0x00000010
#define STE_DMACTL_RXDMA_STALL 0x00000100
#define STE_DMACTL_RXDMA_UNSTALL 0x00000200
#define STE_DMACTL_TXDMA_STALL 0x00000400
#define STE_DMACTL_TXDMA_UNSTALL 0x00000800
#define STE_DMACTL_TXDMA_INPROG 0x00004000
#define STE_DMACTL_DMA_HALTINPROG 0x00008000
#define STE_DMACTL_RXEARLY_ENABLE 0x00020000
#define STE_DMACTL_COUNTDOWN_SPEED 0x00040000
#define STE_DMACTL_COUNTDOWN_MODE 0x00080000
#define STE_DMACTL_MWI_DISABLE 0x00100000
#define STE_DMACTL_RX_DISCARD_OFLOWS 0x00400000
#define STE_DMACTL_COUNTDOWN_ENABLE 0x00800000
#define STE_DMACTL_TARGET_ABORT 0x40000000
#define STE_DMACTL_MASTER_ABORT 0x80000000
/*
* TX DMA burst thresh is the number of 32-byte blocks that
* must be loaded into the TX Fifo before a TXDMA burst request
* will be issued.
*/
#define STE_TXDMABURST_THRESH 0x1F
/*
* The number of 32-byte blocks in the TX FIFO falls below the
* TX DMA urgent threshold, a TX DMA urgent request will be
* generated.
*/
#define STE_TXDMAURG_THRESH 0x3F
/*
* Number of 320ns intervals between polls of the TXDMA next
* descriptor pointer (if we're using polling mode).
*/
#define STE_TXDMA_POLL_PERIOD 0x7F
#define STE_RX_DMASTATUS_FRAMELEN 0x00001FFF
#define STE_RX_DMASTATUS_RXERR 0x00004000
#define STE_RX_DMASTATUS_DMADONE 0x00008000
#define STE_RX_DMASTATUS_FIFO_OFLOW 0x00010000
#define STE_RX_DMASTATUS_RUNT 0x00020000
#define STE_RX_DMASTATUS_ALIGNERR 0x00040000
#define STE_RX_DMASTATUS_CRCERR 0x00080000
#define STE_RX_DMASTATUS_GIANT 0x00100000
#define STE_RX_DMASTATUS_DRIBBLE 0x00800000
#define STE_RX_DMASTATUS_DMA_OFLOW 0x01000000
/*
* RX DMA burst thresh is the number of 32-byte blocks that
* must be present in the RX FIFO before a RXDMA bus master
* request will be issued.
*/
#define STE_RXDMABURST_THRESH 0xFF
/*
* The number of 32-byte blocks in the RX FIFO falls below the
* RX DMA urgent threshold, a RX DMA urgent request will be
* generated.
*/
#define STE_RXDMAURG_THRESH 0x1F
/*
* Number of 320ns intervals between polls of the RXDMA complete
* bit in the status field on the current RX descriptor (if we're
* using polling mode).
*/
#define STE_RXDMA_POLL_PERIOD 0x7F
#define STE_DEBUGCTL_GPIO0_CTL 0x0001
#define STE_DEBUGCTL_GPIO1_CTL 0x0002
#define STE_DEBUGCTL_GPIO0_DATA 0x0004
#define STE_DEBUGCTL_GPIO1_DATA 0x0008
#define STE_ASICCTL_ROMSIZE 0x00000002
#define STE_ASICCTL_TX_LARGEPKTS 0x00000004
#define STE_ASICCTL_RX_LARGEPKTS 0x00000008
#define STE_ASICCTL_EXTROM_DISABLE 0x00000010
#define STE_ASICCTL_PHYSPEED_10 0x00000020
#define STE_ASICCTL_PHYSPEED_100 0x00000040
#define STE_ASICCTL_PHYMEDIA 0x00000080
#define STE_ASICCTL_FORCEDCONFIG 0x00000700
#define STE_ASICCTL_D3RESET_DISABLE 0x00000800
#define STE_ASICCTL_SPEEDUPMODE 0x00002000
#define STE_ASICCTL_LEDMODE 0x00004000
#define STE_ASICCTL_RSTOUT_POLARITY 0x00008000
#define STE_ASICCTL_GLOBAL_RESET 0x00010000
#define STE_ASICCTL_RX_RESET 0x00020000
#define STE_ASICCTL_TX_RESET 0x00040000
#define STE_ASICCTL_DMA_RESET 0x00080000
#define STE_ASICCTL_FIFO_RESET 0x00100000
#define STE_ASICCTL_NETWORK_RESET 0x00200000
#define STE_ASICCTL_HOST_RESET 0x00400000
#define STE_ASICCTL_AUTOINIT_RESET 0x00800000
#define STE_ASICCTL_EXTRESET_RESET 0x01000000
#define STE_ASICCTL_SOFTINTR 0x02000000
#define STE_ASICCTL_RESET_BUSY 0x04000000
#define STE_ASICCTL1_GLOBAL_RESET 0x0001
#define STE_ASICCTL1_RX_RESET 0x0002
#define STE_ASICCTL1_TX_RESET 0x0004
#define STE_ASICCTL1_DMA_RESET 0x0008
#define STE_ASICCTL1_FIFO_RESET 0x0010
#define STE_ASICCTL1_NETWORK_RESET 0x0020
#define STE_ASICCTL1_HOST_RESET 0x0040
#define STE_ASICCTL1_AUTOINIT_RESET 0x0080
#define STE_ASICCTL1_EXTRESET_RESET 0x0100
#define STE_ASICCTL1_SOFTINTR 0x0200
#define STE_ASICCTL1_RESET_BUSY 0x0400
#define STE_EECTL_ADDR 0x00FF
#define STE_EECTL_OPCODE 0x0300
#define STE_EECTL_BUSY 0x1000
#define STE_EEOPCODE_WRITE 0x0100
#define STE_EEOPCODE_READ 0x0200
#define STE_EEOPCODE_ERASE 0x0300
#define STE_FIFOCTL_RAMTESTMODE 0x0001
#define STE_FIFOCTL_OVERRUNMODE 0x0200
#define STE_FIFOCTL_RXFIFOFULL 0x0800
#define STE_FIFOCTL_TX_BUSY 0x4000
#define STE_FIFOCTL_RX_BUSY 0x8000
/*
* The number of bytes that must in present in the TX FIFO before
* transmission begins. Value should be in increments of 4 bytes.
*/
Fixes for the D-Link DFE-580 card. This is pretty much fixes any issue I can find: - Watchdog timeouts were due to starting the TX DMA engine before we had a packet ready for it. So the first packet sent never got out only if we sent more then one packet at a time did the others make it out and not blow up. Of course reseting the chip then caused us not to transmit the first packet again ie. catch-22. This required logic changes. - Combine interrupts on TX packets being queued up. - Don't keep running around the RX ring since we might get out of sync so only go around once per receive - Let the RX engine recover via the poll interface which is similar to the TX interface. This way the chip wakes up with no effort when we read enough packets. - Do better hand-shaking on RX & TX packets so they don't start of to soon. - Force a duplex setting when the link comes up after an ste_init or it will default to half-duplex and be really slow. This only happens on subsequent ste_init. The first one worked. - Don't call stat_update for every overflow. We only monitor the collisions so the tick interval is good enough for that. Just read in the collision stats to minimize bus reads. - Don't read the miibus every tick since it uses delays and delays are not good for performance. - Tie link events directly to the miibus code so the port gets set correctly if someone changes the port settings. - Reduce the extreme number of {R,T}FD's. They would consume 130K of kernel memory for each NIC. - Set the TX_THRESH to wait for the DMA engine to complete before running the TX FIFO. This hurts peak TX performance but under bi-directional load the DMA engine can't keep up with the FIFO. Testing shows that we end up in the case anyways (a la dc(4) issues but worse since the RX engine hogs everything). - When stopping the card do a reset since the reset verifies the card has stopped. Otherwise on heavy RX load the RX DMA engine is still stuffing packets into memory. If that happens after we free the DMA area memory bits get scribled in memory and bad things happen. This card still has seemingly unfixable issues under heavy RX load in which the card takes over the PCI bus. Sponsored by: Vernier Networks MFC after: 1 week
2002-08-07 22:31:27 +00:00
#define STE_TXSTART_THRESH 0x1FFC
/*
* Number of bytes that must be present in the RX FIFO before
* an RX EARLY interrupt is generated.
*/
Fixes for the D-Link DFE-580 card. This is pretty much fixes any issue I can find: - Watchdog timeouts were due to starting the TX DMA engine before we had a packet ready for it. So the first packet sent never got out only if we sent more then one packet at a time did the others make it out and not blow up. Of course reseting the chip then caused us not to transmit the first packet again ie. catch-22. This required logic changes. - Combine interrupts on TX packets being queued up. - Don't keep running around the RX ring since we might get out of sync so only go around once per receive - Let the RX engine recover via the poll interface which is similar to the TX interface. This way the chip wakes up with no effort when we read enough packets. - Do better hand-shaking on RX & TX packets so they don't start of to soon. - Force a duplex setting when the link comes up after an ste_init or it will default to half-duplex and be really slow. This only happens on subsequent ste_init. The first one worked. - Don't call stat_update for every overflow. We only monitor the collisions so the tick interval is good enough for that. Just read in the collision stats to minimize bus reads. - Don't read the miibus every tick since it uses delays and delays are not good for performance. - Tie link events directly to the miibus code so the port gets set correctly if someone changes the port settings. - Reduce the extreme number of {R,T}FD's. They would consume 130K of kernel memory for each NIC. - Set the TX_THRESH to wait for the DMA engine to complete before running the TX FIFO. This hurts peak TX performance but under bi-directional load the DMA engine can't keep up with the FIFO. Testing shows that we end up in the case anyways (a la dc(4) issues but worse since the RX engine hogs everything). - When stopping the card do a reset since the reset verifies the card has stopped. Otherwise on heavy RX load the RX DMA engine is still stuffing packets into memory. If that happens after we free the DMA area memory bits get scribled in memory and bad things happen. This card still has seemingly unfixable issues under heavy RX load in which the card takes over the PCI bus. Sponsored by: Vernier Networks MFC after: 1 week
2002-08-07 22:31:27 +00:00
#define STE_RXEARLY_THRESH 0x1FFC
#define STE_WAKEEVENT_WAKEPKT_ENB 0x01
#define STE_WAKEEVENT_MAGICPKT_ENB 0x02
#define STE_WAKEEVENT_LINKEVT_ENB 0x04
#define STE_WAKEEVENT_WAKEPOLARITY 0x08
#define STE_WAKEEVENT_WAKEPKTEVENT 0x10
#define STE_WAKEEVENT_MAGICPKTEVENT 0x20
#define STE_WAKEEVENT_LINKEVENT 0x40
#define STE_WAKEEVENT_WAKEONLAN_ENB 0x80
#define STE_TXSTATUS_RECLAIMERR 0x02
#define STE_TXSTATUS_STATSOFLOW 0x04
#define STE_TXSTATUS_EXCESSCOLLS 0x08
#define STE_TXSTATUS_UNDERRUN 0x10
#define STE_TXSTATUS_TXINTR_REQ 0x40
#define STE_TXSTATUS_TXDONE 0x80
#define STE_ISRACK_INTLATCH 0x0001
#define STE_ISRACK_HOSTERR 0x0002
#define STE_ISRACK_TX_DONE 0x0004
#define STE_ISRACK_MACCTL_FRAME 0x0008
#define STE_ISRACK_RX_DONE 0x0010
#define STE_ISRACK_RX_EARLY 0x0020
#define STE_ISRACK_SOFTINTR 0x0040
#define STE_ISRACK_STATS_OFLOW 0x0080
#define STE_ISRACK_LINKEVENT 0x0100
#define STE_ISRACK_TX_DMADONE 0x0200
#define STE_ISRACK_RX_DMADONE 0x0400
#define STE_IMR_HOSTERR 0x0002
#define STE_IMR_TX_DONE 0x0004
#define STE_IMR_MACCTL_FRAME 0x0008
#define STE_IMR_RX_DONE 0x0010
#define STE_IMR_RX_EARLY 0x0020
#define STE_IMR_SOFTINTR 0x0040
#define STE_IMR_STATS_OFLOW 0x0080
#define STE_IMR_LINKEVENT 0x0100
#define STE_IMR_TX_DMADONE 0x0200
#define STE_IMR_RX_DMADONE 0x0400
#define STE_INTRS \
Fixes for the D-Link DFE-580 card. This is pretty much fixes any issue I can find: - Watchdog timeouts were due to starting the TX DMA engine before we had a packet ready for it. So the first packet sent never got out only if we sent more then one packet at a time did the others make it out and not blow up. Of course reseting the chip then caused us not to transmit the first packet again ie. catch-22. This required logic changes. - Combine interrupts on TX packets being queued up. - Don't keep running around the RX ring since we might get out of sync so only go around once per receive - Let the RX engine recover via the poll interface which is similar to the TX interface. This way the chip wakes up with no effort when we read enough packets. - Do better hand-shaking on RX & TX packets so they don't start of to soon. - Force a duplex setting when the link comes up after an ste_init or it will default to half-duplex and be really slow. This only happens on subsequent ste_init. The first one worked. - Don't call stat_update for every overflow. We only monitor the collisions so the tick interval is good enough for that. Just read in the collision stats to minimize bus reads. - Don't read the miibus every tick since it uses delays and delays are not good for performance. - Tie link events directly to the miibus code so the port gets set correctly if someone changes the port settings. - Reduce the extreme number of {R,T}FD's. They would consume 130K of kernel memory for each NIC. - Set the TX_THRESH to wait for the DMA engine to complete before running the TX FIFO. This hurts peak TX performance but under bi-directional load the DMA engine can't keep up with the FIFO. Testing shows that we end up in the case anyways (a la dc(4) issues but worse since the RX engine hogs everything). - When stopping the card do a reset since the reset verifies the card has stopped. Otherwise on heavy RX load the RX DMA engine is still stuffing packets into memory. If that happens after we free the DMA area memory bits get scribled in memory and bad things happen. This card still has seemingly unfixable issues under heavy RX load in which the card takes over the PCI bus. Sponsored by: Vernier Networks MFC after: 1 week
2002-08-07 22:31:27 +00:00
(STE_IMR_RX_DMADONE|STE_IMR_TX_DMADONE| \
STE_IMR_TX_DONE|STE_IMR_HOSTERR| \
STE_IMR_LINKEVENT)
#define STE_ISR_INTLATCH 0x0001
#define STE_ISR_HOSTERR 0x0002
#define STE_ISR_TX_DONE 0x0004
#define STE_ISR_MACCTL_FRAME 0x0008
#define STE_ISR_RX_DONE 0x0010
#define STE_ISR_RX_EARLY 0x0020
#define STE_ISR_SOFTINTR 0x0040
#define STE_ISR_STATS_OFLOW 0x0080
#define STE_ISR_LINKEVENT 0x0100
#define STE_ISR_TX_DMADONE 0x0200
#define STE_ISR_RX_DMADONE 0x0400
/*
* Note: the Sundance manual gives the impression that the's
* only one 32-bit MACCTL register. In fact, there are two
* 16-bit registers side by side, and you have to access them
* separately.
*/
#define STE_MACCTL0_IPG 0x0003
#define STE_MACCTL0_FULLDUPLEX 0x0020
#define STE_MACCTL0_RX_GIANTS 0x0040
#define STE_MACCTL0_FLOWCTL_ENABLE 0x0100
#define STE_MACCTL0_RX_FCS 0x0200
#define STE_MACCTL0_FIFOLOOPBK 0x0400
#define STE_MACCTL0_MACLOOPBK 0x0800
#define STE_MACCTL1_COLLDETECT 0x0001
#define STE_MACCTL1_CARRSENSE 0x0002
#define STE_MACCTL1_TX_BUSY 0x0004
#define STE_MACCTL1_TX_ERROR 0x0008
#define STE_MACCTL1_STATS_ENABLE 0x0020
#define STE_MACCTL1_STATS_DISABLE 0x0040
#define STE_MACCTL1_STATS_ENABLED 0x0080
#define STE_MACCTL1_TX_ENABLE 0x0100
#define STE_MACCTL1_TX_DISABLE 0x0200
#define STE_MACCTL1_TX_ENABLED 0x0400
#define STE_MACCTL1_RX_ENABLE 0x0800
#define STE_MACCTL1_RX_DISABLE 0x1000
#define STE_MACCTL1_RX_ENABLED 0x2000
#define STE_MACCTL1_PAUSED 0x4000
#define STE_IPG_96BT 0x00000000
#define STE_IPG_128BT 0x00000001
#define STE_IPG_224BT 0x00000002
#define STE_IPG_544BT 0x00000003
#define STE_RXMODE_UNICAST 0x01
#define STE_RXMODE_ALLMULTI 0x02
#define STE_RXMODE_BROADCAST 0x04
#define STE_RXMODE_PROMISC 0x08
#define STE_RXMODE_MULTIHASH 0x10
#define STE_RXMODE_ALLIPMULTI 0x20
#define STE_PHYCTL_MCLK 0x01
#define STE_PHYCTL_MDATA 0x02
#define STE_PHYCTL_MDIR 0x04
#define STE_PHYCTL_CLK25_DISABLE 0x08
#define STE_PHYCTL_DUPLEXPOLARITY 0x10
#define STE_PHYCTL_DUPLEXSTAT 0x20
#define STE_PHYCTL_SPEEDSTAT 0x40
#define STE_PHYCTL_LINKSTAT 0x80
/*
* EEPROM offsets.
*/
#define STE_EEADDR_CONFIGPARM 0x00
#define STE_EEADDR_ASICCTL 0x02
#define STE_EEADDR_SUBSYS_ID 0x04
#define STE_EEADDR_SUBVEN_ID 0x08
#define STE_EEADDR_NODE0 0x10
#define STE_EEADDR_NODE1 0x12
#define STE_EEADDR_NODE2 0x14
/* PCI registers */
#define STE_PCI_VENDOR_ID 0x00
#define STE_PCI_DEVICE_ID 0x02
#define STE_PCI_COMMAND 0x04
#define STE_PCI_STATUS 0x06
#define STE_PCI_CLASSCODE 0x09
#define STE_PCI_LATENCY_TIMER 0x0D
#define STE_PCI_HEADER_TYPE 0x0E
#define STE_PCI_LOIO 0x10
#define STE_PCI_LOMEM 0x14
#define STE_PCI_BIOSROM 0x30
#define STE_PCI_INTLINE 0x3C
#define STE_PCI_INTPIN 0x3D
#define STE_PCI_MINGNT 0x3E
#define STE_PCI_MINLAT 0x0F
#define STE_PCI_CAPID 0x50 /* 8 bits */
#define STE_PCI_NEXTPTR 0x51 /* 8 bits */
#define STE_PCI_PWRMGMTCAP 0x52 /* 16 bits */
#define STE_PCI_PWRMGMTCTRL 0x54 /* 16 bits */
#define STE_PSTATE_MASK 0x0003
#define STE_PSTATE_D0 0x0000
#define STE_PSTATE_D1 0x0002
#define STE_PSTATE_D2 0x0002
#define STE_PSTATE_D3 0x0003
#define STE_PME_EN 0x0010
#define STE_PME_STATUS 0x8000
struct ste_stats {
u_int32_t ste_rx_bytes;
u_int32_t ste_tx_bytes;
u_int16_t ste_tx_frames;
u_int16_t ste_rx_frames;
u_int8_t ste_carrsense_errs;
u_int8_t ste_late_colls;
u_int8_t ste_multi_colls;
u_int8_t ste_single_colls;
u_int8_t ste_tx_frames_defered;
u_int8_t ste_rx_lost_frames;
u_int8_t ste_tx_excess_defers;
u_int8_t ste_tx_abort_excess_colls;
u_int8_t ste_tx_bcast_frames;
u_int8_t ste_rx_bcast_frames;
u_int8_t ste_tx_mcast_frames;
u_int8_t ste_rx_mcast_frames;
};
struct ste_frag {
u_int32_t ste_addr;
u_int32_t ste_len;
};
#define STE_FRAG_LAST 0x80000000
#define STE_FRAG_LEN 0x00001FFF
Fixes for the D-Link DFE-580 card. This is pretty much fixes any issue I can find: - Watchdog timeouts were due to starting the TX DMA engine before we had a packet ready for it. So the first packet sent never got out only if we sent more then one packet at a time did the others make it out and not blow up. Of course reseting the chip then caused us not to transmit the first packet again ie. catch-22. This required logic changes. - Combine interrupts on TX packets being queued up. - Don't keep running around the RX ring since we might get out of sync so only go around once per receive - Let the RX engine recover via the poll interface which is similar to the TX interface. This way the chip wakes up with no effort when we read enough packets. - Do better hand-shaking on RX & TX packets so they don't start of to soon. - Force a duplex setting when the link comes up after an ste_init or it will default to half-duplex and be really slow. This only happens on subsequent ste_init. The first one worked. - Don't call stat_update for every overflow. We only monitor the collisions so the tick interval is good enough for that. Just read in the collision stats to minimize bus reads. - Don't read the miibus every tick since it uses delays and delays are not good for performance. - Tie link events directly to the miibus code so the port gets set correctly if someone changes the port settings. - Reduce the extreme number of {R,T}FD's. They would consume 130K of kernel memory for each NIC. - Set the TX_THRESH to wait for the DMA engine to complete before running the TX FIFO. This hurts peak TX performance but under bi-directional load the DMA engine can't keep up with the FIFO. Testing shows that we end up in the case anyways (a la dc(4) issues but worse since the RX engine hogs everything). - When stopping the card do a reset since the reset verifies the card has stopped. Otherwise on heavy RX load the RX DMA engine is still stuffing packets into memory. If that happens after we free the DMA area memory bits get scribled in memory and bad things happen. This card still has seemingly unfixable issues under heavy RX load in which the card takes over the PCI bus. Sponsored by: Vernier Networks MFC after: 1 week
2002-08-07 22:31:27 +00:00
#define STE_MAXFRAGS 8
struct ste_desc {
u_int32_t ste_next;
u_int32_t ste_ctl;
struct ste_frag ste_frags[STE_MAXFRAGS];
};
struct ste_desc_onefrag {
u_int32_t ste_next;
u_int32_t ste_status;
struct ste_frag ste_frag;
};
#define STE_TXCTL_WORDALIGN 0x00000003
#define STE_TXCTL_FRAMEID 0x000003FC
#define STE_TXCTL_NOCRC 0x00002000
#define STE_TXCTL_TXINTR 0x00008000
#define STE_TXCTL_DMADONE 0x00010000
#define STE_TXCTL_DMAINTR 0x80000000
#define STE_RXSTAT_FRAMELEN 0x00001FFF
#define STE_RXSTAT_FRAME_ERR 0x00004000
#define STE_RXSTAT_DMADONE 0x00008000
#define STE_RXSTAT_FIFO_OFLOW 0x00010000
#define STE_RXSTAT_RUNT 0x00020000
#define STE_RXSTAT_ALIGNERR 0x00040000
#define STE_RXSTAT_CRCERR 0x00080000
#define STE_RXSTAT_GIANT 0x00100000
#define STE_RXSTAT_DRIBBLEBITS 0x00800000
#define STE_RXSTAT_DMA_OFLOW 0x01000000
#define STE_RXATAT_ONEBUF 0x10000000
/*
* register space access macros
*/
#define CSR_WRITE_4(sc, reg, val) \
bus_space_write_4(sc->ste_btag, sc->ste_bhandle, reg, val)
#define CSR_WRITE_2(sc, reg, val) \
bus_space_write_2(sc->ste_btag, sc->ste_bhandle, reg, val)
#define CSR_WRITE_1(sc, reg, val) \
bus_space_write_1(sc->ste_btag, sc->ste_bhandle, reg, val)
#define CSR_READ_4(sc, reg) \
bus_space_read_4(sc->ste_btag, sc->ste_bhandle, reg)
#define CSR_READ_2(sc, reg) \
bus_space_read_2(sc->ste_btag, sc->ste_bhandle, reg)
#define CSR_READ_1(sc, reg) \
bus_space_read_1(sc->ste_btag, sc->ste_bhandle, reg)
#define STE_TIMEOUT 1000
#define STE_MIN_FRAMELEN 60
#define STE_PACKET_SIZE 1536
#define ETHER_ALIGN 2
Fixes for the D-Link DFE-580 card. This is pretty much fixes any issue I can find: - Watchdog timeouts were due to starting the TX DMA engine before we had a packet ready for it. So the first packet sent never got out only if we sent more then one packet at a time did the others make it out and not blow up. Of course reseting the chip then caused us not to transmit the first packet again ie. catch-22. This required logic changes. - Combine interrupts on TX packets being queued up. - Don't keep running around the RX ring since we might get out of sync so only go around once per receive - Let the RX engine recover via the poll interface which is similar to the TX interface. This way the chip wakes up with no effort when we read enough packets. - Do better hand-shaking on RX & TX packets so they don't start of to soon. - Force a duplex setting when the link comes up after an ste_init or it will default to half-duplex and be really slow. This only happens on subsequent ste_init. The first one worked. - Don't call stat_update for every overflow. We only monitor the collisions so the tick interval is good enough for that. Just read in the collision stats to minimize bus reads. - Don't read the miibus every tick since it uses delays and delays are not good for performance. - Tie link events directly to the miibus code so the port gets set correctly if someone changes the port settings. - Reduce the extreme number of {R,T}FD's. They would consume 130K of kernel memory for each NIC. - Set the TX_THRESH to wait for the DMA engine to complete before running the TX FIFO. This hurts peak TX performance but under bi-directional load the DMA engine can't keep up with the FIFO. Testing shows that we end up in the case anyways (a la dc(4) issues but worse since the RX engine hogs everything). - When stopping the card do a reset since the reset verifies the card has stopped. Otherwise on heavy RX load the RX DMA engine is still stuffing packets into memory. If that happens after we free the DMA area memory bits get scribled in memory and bad things happen. This card still has seemingly unfixable issues under heavy RX load in which the card takes over the PCI bus. Sponsored by: Vernier Networks MFC after: 1 week
2002-08-07 22:31:27 +00:00
#define STE_RX_LIST_CNT 64
#define STE_TX_LIST_CNT 64
#define STE_INC(x, y) (x) = (x + 1) % y
Fixes for the D-Link DFE-580 card. This is pretty much fixes any issue I can find: - Watchdog timeouts were due to starting the TX DMA engine before we had a packet ready for it. So the first packet sent never got out only if we sent more then one packet at a time did the others make it out and not blow up. Of course reseting the chip then caused us not to transmit the first packet again ie. catch-22. This required logic changes. - Combine interrupts on TX packets being queued up. - Don't keep running around the RX ring since we might get out of sync so only go around once per receive - Let the RX engine recover via the poll interface which is similar to the TX interface. This way the chip wakes up with no effort when we read enough packets. - Do better hand-shaking on RX & TX packets so they don't start of to soon. - Force a duplex setting when the link comes up after an ste_init or it will default to half-duplex and be really slow. This only happens on subsequent ste_init. The first one worked. - Don't call stat_update for every overflow. We only monitor the collisions so the tick interval is good enough for that. Just read in the collision stats to minimize bus reads. - Don't read the miibus every tick since it uses delays and delays are not good for performance. - Tie link events directly to the miibus code so the port gets set correctly if someone changes the port settings. - Reduce the extreme number of {R,T}FD's. They would consume 130K of kernel memory for each NIC. - Set the TX_THRESH to wait for the DMA engine to complete before running the TX FIFO. This hurts peak TX performance but under bi-directional load the DMA engine can't keep up with the FIFO. Testing shows that we end up in the case anyways (a la dc(4) issues but worse since the RX engine hogs everything). - When stopping the card do a reset since the reset verifies the card has stopped. Otherwise on heavy RX load the RX DMA engine is still stuffing packets into memory. If that happens after we free the DMA area memory bits get scribled in memory and bad things happen. This card still has seemingly unfixable issues under heavy RX load in which the card takes over the PCI bus. Sponsored by: Vernier Networks MFC after: 1 week
2002-08-07 22:31:27 +00:00
#define STE_NEXT(x, y) (x + 1) % y
struct ste_type {
u_int16_t ste_vid;
u_int16_t ste_did;
char *ste_name;
};
struct ste_list_data {
struct ste_desc_onefrag ste_rx_list[STE_RX_LIST_CNT];
struct ste_desc ste_tx_list[STE_TX_LIST_CNT];
u_int8_t ste_pad[STE_MIN_FRAMELEN];
};
struct ste_chain {
struct ste_desc *ste_ptr;
struct mbuf *ste_mbuf;
struct ste_chain *ste_next;
struct ste_chain *ste_prev;
u_int32_t ste_phys;
};
struct ste_chain_onefrag {
struct ste_desc_onefrag *ste_ptr;
struct mbuf *ste_mbuf;
struct ste_chain_onefrag *ste_next;
};
struct ste_chain_data {
struct ste_chain_onefrag ste_rx_chain[STE_RX_LIST_CNT];
struct ste_chain ste_tx_chain[STE_TX_LIST_CNT];
struct ste_chain_onefrag *ste_rx_head;
int ste_tx_prod;
int ste_tx_cons;
int ste_tx_cnt;
};
struct ste_softc {
struct arpcom arpcom;
bus_space_tag_t ste_btag;
bus_space_handle_t ste_bhandle;
struct resource *ste_res;
struct resource *ste_irq;
void *ste_intrhand;
struct ste_type *ste_info;
device_t ste_miibus;
Fixes for the D-Link DFE-580 card. This is pretty much fixes any issue I can find: - Watchdog timeouts were due to starting the TX DMA engine before we had a packet ready for it. So the first packet sent never got out only if we sent more then one packet at a time did the others make it out and not blow up. Of course reseting the chip then caused us not to transmit the first packet again ie. catch-22. This required logic changes. - Combine interrupts on TX packets being queued up. - Don't keep running around the RX ring since we might get out of sync so only go around once per receive - Let the RX engine recover via the poll interface which is similar to the TX interface. This way the chip wakes up with no effort when we read enough packets. - Do better hand-shaking on RX & TX packets so they don't start of to soon. - Force a duplex setting when the link comes up after an ste_init or it will default to half-duplex and be really slow. This only happens on subsequent ste_init. The first one worked. - Don't call stat_update for every overflow. We only monitor the collisions so the tick interval is good enough for that. Just read in the collision stats to minimize bus reads. - Don't read the miibus every tick since it uses delays and delays are not good for performance. - Tie link events directly to the miibus code so the port gets set correctly if someone changes the port settings. - Reduce the extreme number of {R,T}FD's. They would consume 130K of kernel memory for each NIC. - Set the TX_THRESH to wait for the DMA engine to complete before running the TX FIFO. This hurts peak TX performance but under bi-directional load the DMA engine can't keep up with the FIFO. Testing shows that we end up in the case anyways (a la dc(4) issues but worse since the RX engine hogs everything). - When stopping the card do a reset since the reset verifies the card has stopped. Otherwise on heavy RX load the RX DMA engine is still stuffing packets into memory. If that happens after we free the DMA area memory bits get scribled in memory and bad things happen. This card still has seemingly unfixable issues under heavy RX load in which the card takes over the PCI bus. Sponsored by: Vernier Networks MFC after: 1 week
2002-08-07 22:31:27 +00:00
device_t ste_dev;
int ste_unit;
int ste_tx_thresh;
u_int8_t ste_link;
int ste_if_flags;
Fixes for the D-Link DFE-580 card. This is pretty much fixes any issue I can find: - Watchdog timeouts were due to starting the TX DMA engine before we had a packet ready for it. So the first packet sent never got out only if we sent more then one packet at a time did the others make it out and not blow up. Of course reseting the chip then caused us not to transmit the first packet again ie. catch-22. This required logic changes. - Combine interrupts on TX packets being queued up. - Don't keep running around the RX ring since we might get out of sync so only go around once per receive - Let the RX engine recover via the poll interface which is similar to the TX interface. This way the chip wakes up with no effort when we read enough packets. - Do better hand-shaking on RX & TX packets so they don't start of to soon. - Force a duplex setting when the link comes up after an ste_init or it will default to half-duplex and be really slow. This only happens on subsequent ste_init. The first one worked. - Don't call stat_update for every overflow. We only monitor the collisions so the tick interval is good enough for that. Just read in the collision stats to minimize bus reads. - Don't read the miibus every tick since it uses delays and delays are not good for performance. - Tie link events directly to the miibus code so the port gets set correctly if someone changes the port settings. - Reduce the extreme number of {R,T}FD's. They would consume 130K of kernel memory for each NIC. - Set the TX_THRESH to wait for the DMA engine to complete before running the TX FIFO. This hurts peak TX performance but under bi-directional load the DMA engine can't keep up with the FIFO. Testing shows that we end up in the case anyways (a la dc(4) issues but worse since the RX engine hogs everything). - When stopping the card do a reset since the reset verifies the card has stopped. Otherwise on heavy RX load the RX DMA engine is still stuffing packets into memory. If that happens after we free the DMA area memory bits get scribled in memory and bad things happen. This card still has seemingly unfixable issues under heavy RX load in which the card takes over the PCI bus. Sponsored by: Vernier Networks MFC after: 1 week
2002-08-07 22:31:27 +00:00
int ste_tx_prev_idx;
struct ste_list_data *ste_ldata;
struct ste_chain_data ste_cdata;
struct callout_handle ste_stat_ch;
struct mtx ste_mtx;
u_int8_t ste_one_phy;
};
Change and clean the mutex lock interface. mtx_enter(lock, type) becomes: mtx_lock(lock) for sleep locks (MTX_DEF-initialized locks) mtx_lock_spin(lock) for spin locks (MTX_SPIN-initialized) similarily, for releasing a lock, we now have: mtx_unlock(lock) for MTX_DEF and mtx_unlock_spin(lock) for MTX_SPIN. We change the caller interface for the two different types of locks because the semantics are entirely different for each case, and this makes it explicitly clear and, at the same time, it rids us of the extra `type' argument. The enter->lock and exit->unlock change has been made with the idea that we're "locking data" and not "entering locked code" in mind. Further, remove all additional "flags" previously passed to the lock acquire/release routines with the exception of two: MTX_QUIET and MTX_NOSWITCH The functionality of these flags is preserved and they can be passed to the lock/unlock routines by calling the corresponding wrappers: mtx_{lock, unlock}_flags(lock, flag(s)) and mtx_{lock, unlock}_spin_flags(lock, flag(s)) for MTX_DEF and MTX_SPIN locks, respectively. Re-inline some lock acq/rel code; in the sleep lock case, we only inline the _obtain_lock()s in order to ensure that the inlined code fits into a cache line. In the spin lock case, we inline recursion and actually only perform a function call if we need to spin. This change has been made with the idea that we generally tend to avoid spin locks and that also the spin locks that we do have and are heavily used (i.e. sched_lock) do recurse, and therefore in an effort to reduce function call overhead for some architectures (such as alpha), we inline recursion for this case. Create a new malloc type for the witness code and retire from using the M_DEV type. The new type is called M_WITNESS and is only declared if WITNESS is enabled. Begin cleaning up some machdep/mutex.h code - specifically updated the "optimized" inlined code in alpha/mutex.h and wrote MTX_LOCK_SPIN and MTX_UNLOCK_SPIN asm macros for the i386/mutex.h as we presently need those. Finally, caught up to the interface changes in all sys code. Contributors: jake, jhb, jasone (in no particular order)
2001-02-09 06:11:45 +00:00
#define STE_LOCK(_sc) mtx_lock(&(_sc)->ste_mtx)
#define STE_UNLOCK(_sc) mtx_unlock(&(_sc)->ste_mtx)
struct ste_mii_frame {
u_int8_t mii_stdelim;
u_int8_t mii_opcode;
u_int8_t mii_phyaddr;
u_int8_t mii_regaddr;
u_int8_t mii_turnaround;
u_int16_t mii_data;
};
/*
* MII constants
*/
#define STE_MII_STARTDELIM 0x01
#define STE_MII_READOP 0x02
#define STE_MII_WRITEOP 0x01
#define STE_MII_TURNAROUND 0x02
#ifdef __alpha__
#undef vtophys
#define vtophys(va) alpha_XXX_dmamap((vm_offset_t)va)
#endif