[tulip] RE: tulip digest, Vol 1 #478 - Lynksys LNE100TX

Tue Feb 19 13:49:00 2002

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------ =_NextPart_001_01C1B975.1C8A3E7E
Content-Type: text/plain

>> >> Instead I attempted to reset the bit when the "PCI
>> >> Fatal Error" message is issued.  Based on the way the code acted, the
>> >> "Parity Error Response" was not set, yet the error continued to be
posted.
>> I'm not sure that I've  completely understood all the steps you've taken
>> but when such an error occurs one has to clear the error bits in the PCI
>> status
>> register of the device (by writing "1" to the appropriate bits (same as
when
>> clearing
>> CSR5 interrupt bits))and then clear CSR5. failing to do so will cause the
>> device to reissue its PCI error "message".

>> can you please send me the changes you've done that didn't work ?

>> Moti H.

Since the change didn't work, I remove the change and didn't save it.
Basically the changed consisted of adding code behind the:

	printk(KERN_ERR, "%s: PCI Fatal Error ...

message to read the PCI command register.  If the "Parity Error Response"
bit was 1, I wrote the PCI command register with the "Parity Error Response"
bit set to 1 (all other bits set to zero) to turn off "Parity Error
Response".  Based on the messages I included in the change, the "Parity
Error Response" bit had to be zero at the time the "PCI Fatal Error" message
was issued.  Unless, I used the functions to read and write the PCI
registers incorrectly, I did nothing with the "PCI Status Register" or with
CSR5.

I would like to insure that "Parity Error Response" is zero at
initialization time.  However, I have not been able to figure out the
structure of the tulip driver well enough to know the best place to make the
change.  I'll make another attempt with your suggestions.

Thank you.

Bob Ludwig
EKC, Inc.
10400 W. Higgins Rd.,  Suite 200
Rosemont, IL  60018
(847) 296-8010
(847) 296-8016 (Fax)
RobertL@EKCInc.com
www.EKCInc.com

------ =_NextPart_001_01C1B975.1C8A3E7E
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DUS-ASCII">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.0.1460.9">
<TITLE>RE: tulip digest, Vol 1 #478 - Lynksys LNE100TX </TITLE>
</HEAD>
<BODY>

&gt;&gt; =
&gt;&gt; Instead I =
attempted to reset the bit when the &quot;PCI
 &gt;&gt; =
&gt;&gt; Fatal =
Error&quot; message is issued.&nbsp; Based on the way the code acted, =
the
 &gt;&gt; =
&gt;&gt; &quot;Parity =
Error Response&quot; was not set, yet the error continued to =
be posted.
 &gt;&gt; =
I'm not sure that =
I've&nbsp; completely understood all the steps you've taken
 &gt;&gt; =
but when such an error =
occurs one has to clear the error bits in the PCI
 &gt;&gt; =
status
 &gt;&gt; =
register of the device =
(by writing &quot;1&quot; to the appropriate bits (same as when
 &gt;&gt; =
clearing
 &gt;&gt; =
CSR5 interrupt =
bits))and then clear CSR5. failing to do so will cause the
 &gt;&gt; =
device to reissue its =
PCI error &quot;message&quot;.

<P><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Arial">&gt;&gt;</FONT> =
<FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Arial">can you please send me =
the changes you've done that didn't work ?</FONT>
</P>

<P><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Arial">&gt;&gt;</FONT> =
<FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Arial">Moti H.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Since the change didn't work, I remove =
the change and didn't save it.&nbsp; Basically the changed consisted of =
adding code behind the:</FONT></P>
<UL>
<P><FONT SIZE=3D2 FACE=3D"Arial">printk(KERN_ERR, &quot;%s: PCI Fatal =
Error ...</FONT>
</P>
</UL>
<P><FONT SIZE=3D2 FACE=3D"Arial">message to read the PCI command =
register.&nbsp; If the &quot;Parity Error Response&quot; bit was 1, I =
wrote the PCI command register with the &quot;Parity Error =
Response&quot; bit set to 1 (all other bits set to zero) to turn off =
&quot;Parity Error Response&quot;.&nbsp; Based on the messages I =
included in the change, the &quot;Parity Error Response&quot; bit had =
to be zero at the time the &quot;PCI Fatal Error&quot; message was =
issued.&nbsp; Unless, I used the functions to read and write the PCI =
registers incorrectly, I did nothing with the &quot;PCI Status =
Register&quot; or with CSR5.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I would like to insure that =
&quot;Parity Error Response&quot; is zero at initialization time.&nbsp; =
However, I have not been able to figure out the structure of the tulip =
driver well enough to know the best place to make the change.&nbsp; =
I'll make another attempt with your suggestions.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Thank you.</FONT>
</P>

<P><B><I><FONT SIZE=3D5 FACE=3D"Arial">Bob Ludwig</FONT></I></B><I></I>
<BR><B><FONT FACE=3D"Arial">EKC, Inc.</FONT></B>
<BR><FONT SIZE=3D2 FACE=3D"Arial">10400 W. Higgins Rd.,&nbsp; Suite =
200</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Rosemont, IL&nbsp; 60018</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">(847) 296-8010</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">(847) 296-8016 (Fax)</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">RobertL@EKCInc.com</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">www.EKCInc.com</FONT>
</P>

</BODY>
</HTML>
------ =_NextPart_001_01C1B975.1C8A3E7E--