From: Torben Mathiasen <torben@kernel.dk>
To: saw@saw.sw.com.sg, jgarzik@mandrakesoft.com
Cc: linux-kernel@vger.kernel.org, scott@tranzoa.com
Subject: Re: eepro100 problems in 2.4.0
Date: Fri, 26 Jan 2001 12:13:37 +0100 [thread overview]
Message-ID: <E14M6oz-0000dk-00@virtualhost.dk> (raw)
[-- Attachment #1: Type: text/plain, Size: 747 bytes --]
On Friday, 26 January 2001, saw@saw.sw.com.sg wrote:
> Hi,
>
> On Thu, Jan 25, 2001 at 04:19:27PM -0500, Jeff Garzik wrote:
> > Oops, sorry guys. Thanks to DaveM for correcting me -- my patch has
> > nothing to do with the "card reports no resources" problem. My
> > apologies.
>
> No problems.
>
> However, there is a real problem with eepro100 when the system resumes
> operations after a sleep.
> May be, you could guess what's wrong in this case?
>
I had to add this small patch to make it work properly with my Armada
M700. It basiclly just does something similar to what happens when we
get TX timeouts. Its just a quick hack, as I got tired of the eepro100
driver dumping the tx/rx queues when resuming.
Regards,
Torben Mathiasen
[-- Attachment #2: ee100apm.diff --]
[-- Type: application/octet-stream, Size: 976 bytes --]
--- /opt/kernel/kernels/linux/drivers/net/eepro100.c Tue Nov 28 02:58:32 2000
+++ linux/drivers/net/eepro100.c Wed Jan 24 16:26:14 2001
@@ -2145,7 +2145,7 @@
{
struct net_device *dev = pdev->driver_data;
struct speedo_private *sp = (struct speedo_private *)dev->priv;
- long ioaddr = dev->base_addr;
+ long ioaddr = dev->base_addr, flags;
/* I'm absolutely uncertain if this part of code may work.
The problems are:
@@ -2154,12 +2154,19 @@
reinitialization;
- serialization with other driver calls.
2000/03/08 SAW */
+ outl(PortReset, ioaddr + SCBPort);
+ udelay(10);
outw(SCBMaskAll, ioaddr + SCBCmd);
+ synchronize_irq();
+ spin_lock_irqsave(&sp->lock, flags);
speedo_resume(dev);
- netif_device_attach(dev);
+ dev->trans_start = jiffies;
sp->rx_mode = -1;
+ spin_unlock_irqrestore(&sp->lock, flags);
+ netif_device_attach(dev);
sp->flow_ctrl = sp->partner = 0;
set_rx_mode(dev);
+ reset_mii(dev);
}
#endif /* CONFIG_EEPRO100_PM */
next reply other threads:[~2001-01-26 11:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-26 11:13 Torben Mathiasen [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-25 20:54 eepro100 problems in 2.4.0 Micah Gorrell
2001-01-25 21:05 ` [PATCH] " Jeff Garzik
2001-01-25 21:19 ` Jeff Garzik
2001-01-26 0:50 ` Andrey Savochkin
2001-01-27 16:30 ` Jeff Garzik
2001-01-25 21:06 ` Sergey Kubushin
2001-01-25 20:20 Micah Gorrell
2001-01-25 20:29 ` Sergey Kubushin
2001-01-25 20:44 ` Tom Sightler
2001-01-29 9:13 ` Andrey Savochkin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E14M6oz-0000dk-00@virtualhost.dk \
--to=torben@kernel.dk \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=saw@saw.sw.com.sg \
--cc=scott@tranzoa.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox