The patch titled
IP100A: Correct initial and close hardware step
has been removed from the -mm tree. Its filename is
ip100a-correct-initial-and-close-hardware-step.patch
This patch was dropped because it's a mess
------------------------------------------------------
Subject: IP100A: Correct initial and close hardware step
From: Jesse Huang <jesse@xxxxxxxxxxxxx>
Correct initial and close hardware step.
Signed-off-by: Jesse Huang <jesse@xxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxx>
---
drivers/net/sundance.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff -puN drivers/net/sundance.c~ip100a-correct-initial-and-close-hardware-step drivers/net/sundance.c
--- a/drivers/net/sundance.c~ip100a-correct-initial-and-close-hardware-step
+++ a/drivers/net/sundance.c
@@ -789,6 +789,7 @@ static int netdev_open(struct net_device
{
struct netdev_private *np = netdev_priv(dev);
void __iomem *ioaddr = np->base;
+ unsigned long flags;
int i;
/* Do we need to reset the chip??? */
@@ -833,6 +834,10 @@ static int netdev_open(struct net_device
iowrite8(0x01, ioaddr + DebugCtrl1);
netif_start_queue(dev);
+ spin_lock_irqsave(&np->lock, flags);
+ reset_tx(dev);
+ spin_unlock_irqrestore(&np->lock, flags);
+
iowrite16 (StatsEnable | RxEnable | TxEnable, ioaddr + MACCtrl1);
if (netif_msg_ifup(np))
@@ -1651,6 +1656,9 @@ static int netdev_close(struct net_devic
/* Disable interrupts by clearing the interrupt mask. */
iowrite16(0x0000, ioaddr + IntrEnable);
+ /* Disable Rx and Tx DMA for safely release resource */
+ iowrite32(0x500, ioaddr + DMACtrl);
+
/* Stop the chip's Tx and Rx processes. */
iowrite16(TxDisable | RxDisable | StatsDisable, ioaddr + MACCtrl1);
_
Patches currently in -mm which might be from jesse@xxxxxxxxxxxxx are
ip100a-fix-tx-pause-bug-reset_tx-intr_handler.patch
ip100a-correct-initial-and-close-hardware-step.patch
ip100a-solve-host-error-problem-in-low-performance.patch
sundance-restore-the-original-tx-fifo-overflow-process.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
