From: Louis Zhuang <louis.zhuang@linux.co.intel.com>
To: jgarzik@redhat.com, scott.feldman@intel.com
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [BUG FIX] e100 initialization issue on STL2 motherboard
Date: 14 Jan 2003 13:51:55 +0800 [thread overview]
Message-ID: <1042523515.3951.12.camel@hawk.sh.intel.com> (raw)
Dear Jeff,
The patch will increase waiting time in SCB initialization. It will
resolve the issue on STL2 motherboard. Pls apply.
--
Yours truly,
Louis Zhuang
---------------
Fault Injection Test Harness Project
BK tree: http://fault-injection.bkbits.net/linux-2.5
Home Page: http://sf.net/projects/fault-injection
You can import this changeset into BK by piping this whole message to:
'| bk receive [path to repository]' or apply the patch as usual.
===================================================================
ChangeSet@1.1019, 2003-01-14 13:45:36+08:00, louis@hawk.sh.intel.com
fix e100 initialization issue on STL2 motherboard
e100.h | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
diff -Nru a/drivers/net/e100/e100.h b/drivers/net/e100/e100.h
--- a/drivers/net/e100/e100.h Tue Jan 14 13:46:26 2003
+++ b/drivers/net/e100/e100.h Tue Jan 14 13:46:26 2003
@@ -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 */
/* HWI feature related constant */
===================================================================
This BitKeeper patch contains the following changesets:
1.1019
## Wrapped with gzip_uu ##
begin 664 bkpatch4832
M'XL(`#*D(SX``\U4:VO;,!3]'/V*"_W6$OM>V7)20T;2!UMIRTH?;-^":LNU
M%ML:EM(7_O%3G)%22O9B@TG"$KK2T3WG'KP#-U:UZ:`R2VW9#GPPUJ6#4CXL
M`EL&NG&J"C)3^\BE,3X2EJ9687\ZY($8%IKYV(5T60GWJK7I@()HL^.>OJIT
M<'G\_N9L=LG89`*'I6SNU)5R,)DP9]I[6>5V*EU9F29PK6QLK9Q</=EMCG8<
MD?LN:!2A2#I*,!YU&>5$,B:5(X_'2<RLDTVEGJ:U;)S.3*M>,7@-%R%1[`'C
M*.G\;1&S(Z"`D/8!HQ`II!@H2F.11LD>CE-$Z#E/WR@#>P1#9`?P=\D<L@P*
M_0B*_-.ZT4[+2C]+ITT#VMJE`K^XNC[C4!M7JO;6R#9GI\!%A)Q=O.C,AK_9
M&$.)[!U\N9/MLUZLY,Q;N5#6%*ZGDK=Z5>FP42Y<I==_@G)-+,(1CCGG48>C
M?2&Z0JJ"N,!1,LYX,8ZWR?@CU._%BCVUE5R4]$[:<F'EJW^3^@:V57DI?PKH
ML\:($W).'8G]9&TQ3F\,AK]@,/IO#+8NP$<8M@_]\(:YV%:+/_#>D1<-B)VL
MIYU<%;I1<.SAYN>SS_.KPX/YI]G)]4`@XB#<A7/Y",M<5?+)>A;P(+6;V^P6
;=L.7_U)6JFQAE_5D7,1"B$*P;QI*PE?V!```
`
end
next reply other threads:[~2003-01-14 5:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-14 5:51 Louis Zhuang [this message]
2003-01-14 6:01 ` [BUG FIX] e100 initialization issue on STL2 motherboard Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2003-01-15 7:09 Feldman, Scott
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=1042523515.3951.12.camel@hawk.sh.intel.com \
--to=louis.zhuang@linux.co.intel.com \
--cc=jgarzik@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=scott.feldman@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.