From: Jeff Garzik <jgarzik@pobox.com>
To: "Fu, Michael" <michael.fu@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] e100 driver fails to initialize the hardware after ker nel bootup through kexec
Date: Mon, 27 Jan 2003 21:59:45 -0500 [thread overview]
Message-ID: <3E35F221.8050606@pobox.com> (raw)
In-Reply-To: <957BD1C2BF3CD411B6C500A0C944CA2602E947F0@pdsmsx32.pd.intel.com>
Fu, Michael wrote:
> On Sat, 2003-01-25 at 00:07, Jeff Garzik wrote:
> On Fri, Jan 24, 2003 at 05:57:55PM +0300, Andrey Nekrasov wrote:
>
>>>or "e100" driver and with patch:
>>>
>>>
>>>--- drivers/net/e100/e100.h- Wed Dec 4 15:16:08 2002
>>>+++ drivers/net/e100/e100.h Wed Dec 4 15:16:20 2002
>>>@@ -100,7 +100,7 @@
>>>
>>> #define E100_MAX_NIC 16
>>>
>>>-#define E100_MAX_SCB_WAIT 100 /* Max udelays in wait_scb */
>>>+#define E100_MAX_SCB_WAIT 5000 /* Max udelays in wait_scb */
>>> #define E100_MAX_CU_IDLE_WAIT 50 /* Max udelays in wait_cus_idle
> Which release your patch applies for ? I failed to compile it on 2.5.52. It
> seems that function e100_disable_clear_intr is not defined.
This wasn't my patch :) But anyway, 2.4.x series is actually ahead of
2.5.x in terms of e100 bugfixes, owing to Linus's vacation. If you use
BitKeeper, you can obtain the latest by issuing
bk pull http://linux.bkbits.net/linux-2.4
or wait another day or so for Marcelo to release 2.4.21-pre4 :)
The 2.5 and 2.4 versions of e100 are kept in sync, so it is trivial to
take 2.4's e100 and use it in 2.5 [and vice versa].
Jeff
next prev parent reply other threads:[~2003-01-28 2:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-27 3:14 [BUG] e100 driver fails to initialize the hardware after ker nel bootup through kexec Fu, Michael
2003-01-28 2:59 ` Jeff Garzik [this message]
2003-01-29 4:28 ` Eric W. Biederman
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=3E35F221.8050606@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.fu@intel.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