linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrey Savochkin <saw@saw.sw.com.sg>
To: CaT <cat@zip.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: eepro100 + 2.2.18 + laptop problems
Date: Tue, 13 Feb 2001 09:26:38 +0800	[thread overview]
Message-ID: <20010213092638.A11218@saw.sw.com.sg> (raw)
In-Reply-To: <20010211224033.G352@zip.com.au>
In-Reply-To: <20010211224033.G352@zip.com.au>; from "CaT" on Sun, Feb 11, 2001 at 10:40:33PM

[-- Attachment #1: Type: text/plain, Size: 309 bytes --]

On Sun, Feb 11, 2001 at 10:40:33PM +1100, CaT wrote:
[snip]
> Feb 11 22:30:18 theirongiant kernel: eepro100: cmd_wait for(0x70) timedout with(0x70)!

Please try the attached patch.
Actually, it's designed to solve another problem, but may be your one has the
same origin as that other.

Best regards
		Andrey

[-- Attachment #2: res --]
[-- Type: text/plain, Size: 1248 bytes --]

Index: eepro100.c
===================================================================
RCS file: /home/oursoft/eepro100/eepro100.c,v
retrieving revision 1.20.2.13
diff -u -r1.20.2.13 eepro100.c
--- eepro100.c	2000/09/14 04:41:58	1.20.2.13
+++ eepro100.c	2001/02/13 01:22:07
@@ -726,6 +726,7 @@
 	   This takes less than 10usec and will easily finish before the next
 	   action. */
 	outl(PortReset, ioaddr + SCBPort);
+	inl(ioaddr + SCBPort);
 	/* Honor PortReset timing. */
 	udelay(10);
 
@@ -814,6 +815,7 @@
 #endif  /* kernel_bloat */
 
 	outl(PortReset, ioaddr + SCBPort);
+	inl(ioaddr + SCBPort);
 	/* Honor PortReset timing. */
 	udelay(10);
 
@@ -1037,6 +1039,9 @@
 	/* Set the segment registers to '0'. */
 	wait_for_cmd_done(ioaddr + SCBCmd);
 	outl(0, ioaddr + SCBPointer);
+	/* impose a delay to avoid a bug */
+	inl(ioaddr + SCBPointer);
+	udelay(10);
 	outb(RxAddrLoad, ioaddr + SCBCmd);
 	wait_for_cmd_done(ioaddr + SCBCmd);
 	outb(CUCmdBase, ioaddr + SCBCmd);
@@ -1298,6 +1303,7 @@
 		end_bh_atomic();
 		/* Reset the Tx and Rx units. */
 		outl(PortReset, ioaddr + SCBPort);
+		inl(ioaddr + SCBPort);
 		/* We may get spurious interrupts here.  But I don't think that they
 		   may do much harm.  1999/12/09 SAW */
 		udelay(10);

  reply	other threads:[~2001-02-13  1:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-11 11:40 eepro100 + 2.2.18 + laptop problems CaT
2001-02-13  1:26 ` Andrey Savochkin [this message]
2001-02-13  4:14   ` CaT
2001-02-19 22:21     ` CaT
2001-02-19 22:49       ` Andrey Savochkin
2001-02-20  0:18         ` Ion Badulescu
2001-02-20  0:31           ` CaT
2001-02-20  7:40             ` CaT
2001-02-20 10:00               ` Ion Badulescu
2001-02-20 10:18                 ` CaT
2001-02-19 23:37       ` Dragan Stancevic
2001-02-19 22:33         ` CaT
2001-02-19 23:44           ` Dragan Stancevic
2001-02-19 22:42             ` CaT
2001-03-04 22:23   ` CaT

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=20010213092638.A11218@saw.sw.com.sg \
    --to=saw@saw.sw.com.sg \
    --cc=cat@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).