From: Stephan von Krawczynski <skraw@ithnet.com>
To: Burton W <bwindle@fint.org>
Cc: tulip-users@lists.sourceforge.net, jgarzik@mandrakesoft.com,
linux-kernel@vger.kernel.org
Subject: Re: 2.4.17-pre7: Oops with Tulip
Date: Mon, 10 Dec 2001 14:27:07 +0100 [thread overview]
Message-ID: <20011210142707.6210b33b.skraw@ithnet.com> (raw)
In-Reply-To: <Pine.LNX.4.43.0112100105140.211-100000@morpheus>
In-Reply-To: <Pine.LNX.4.43.0112100105140.211-100000@morpheus>
On Mon, 10 Dec 2001 01:08:28 -0500 (EST)
Burton W <bwindle@fint.org> wrote:
Just to test a theory: please try attached patch.
Regards,
Stephan
--- eeprom.c-orig Mon Dec 10 14:24:35 2001
+++ eeprom.c Mon Dec 10 14:25:41 2001
@@ -130,9 +130,9 @@
}
controller_index = 0;
- if (ee_data[19] > 1) { /* Multiport board. */
- last_ee_data = ee_data;
- }
+
+ last_ee_data = ee_data;
+
subsequent_board:
if (ee_data[27] == 0) { /* No valid media table. */
next prev parent reply other threads:[~2001-12-10 13:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-10 6:08 2.4.17-pre7: Oops with Tulip Burton W
2001-12-10 13:27 ` Stephan von Krawczynski [this message]
[not found] <Pine.LNX.4.43.0112101918080.204-100000@morpheus>
2001-12-11 2:40 ` Stephan von Krawczynski
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=20011210142707.6210b33b.skraw@ithnet.com \
--to=skraw@ithnet.com \
--cc=bwindle@fint.org \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tulip-users@lists.sourceforge.net \
/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