All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: Andrew Morton <akpm@zip.com.au>
Cc: Urban Widmark <urban@teststation.com>,
	Martin Eriksson <nitrax@giron.wox.org>,
	Justin A <justin@bouncybouncy.net>,
	Andy Carlson <naclos@swbell.net>,
	linux-kernel@vger.kernel.org
Subject: Re: via-rhine timeouts
Date: Thu, 24 Jan 2002 00:25:53 +0100	[thread overview]
Message-ID: <200201232325.AAA12824@webserver.ithnet.com> (raw)
In-Reply-To: <3C4F20A5.F88EA471@zip.com.au>

> Urban Widmark wrote:                                                
> >                                                                   
> >     writeb(readb(ioaddr + TxConfig) | 0x80, ioaddr + TxConfig);   
> >     np->tx_thresh = 0x20;                                         
> > (linuxfet.c)                                                      
> >                                                                   
> >         writeb(0x20, ioaddr + TxConfig);                          
> >         np->tx_thresh = 0x20;                                     
> > (via-rhine.c)                                                     
> >                                                                   
> > Note how the linuxfet driver sets a higher value but does not make
the                                                                   
> > tx_thresh follow, so if it later gets a "IntrTxUnderrun" it will  
lower the                                                             
> > threshold. But the chosen value is probably large enough.         
> >                                                                   
> > Those of you with this problem could try changing the 0x80 to 0x20
in the                                                                
> > linuxfet.c driver and see if the problem returns (or the other way
around                                                                
> > in the via-rhine.c driver).                                       
> >                                                                   
>                                                                     
> That would certainly explain why people are seeing success          
> with linuxfet.                                                      
>                                                                     
> Here's the test patch which you describe.  It would be              
> useful if people could try it..                                     
                                                                      
Forgive me being stupid, but shouldn't the comment behind follow      
somehow?                                                              
I may be dead wrong, but you're increasing the initial treshold here, 
or not?                                                               
Please ignore me if I am way off.                                     
                                                                      
Regards,                                                              
Stephan                                                               
                                                                      
                                                                      
--- linux-2.4.18-pre6/drivers/net/via-rhine.c	Tue Jan 22 12:38:30 2002
+++ linux-akpm/drivers/net/via-rhine.c	Wed Jan 23 12:42:18 2002       
@@ -965,7 +965,7 @@ static void init_registers(struct net_de          
 	/* Initialize other registers. */                                   
 	writew(0x0006, ioaddr + PCIBusConfig);	/* Tune configuration??? */  
 	/* Configure the FIFO thresholds. */                                
-	writeb(0x20, ioaddr + TxConfig);	/* Initial threshold 32 bytes */   
+	writeb(0x80, ioaddr + TxConfig);	/* Initial threshold 128 bytes */  
 	np->tx_thresh = 0x20;                                               
 	np->rx_thresh = 0x60;			/* Written in via_rhine_set_rx_mode(). */   
                                                                      
                                                                      

  reply	other threads:[~2002-01-23 23:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-22 23:42 via-rhine timeouts Justin A
2002-01-23  0:37 ` Urban Widmark
2002-01-23  1:02   ` Justin A
2002-01-23  9:44     ` Urban Widmark
2002-01-23 10:16       ` Stephan von Krawczynski
2002-01-23  1:07 ` Andy Carlson
2002-01-23  1:58   ` Justin A
2002-01-23 10:36     ` Martin Eriksson
2002-01-23 12:04       ` Urban Widmark
2002-01-23 20:44         ` Andrew Morton
2002-01-23 23:25           ` Stephan von Krawczynski [this message]
2002-01-23 23:53             ` Urban Widmark
2002-01-23 23:41           ` Justin A
2002-01-23 23:49             ` Urban Widmark
2002-01-24  8:38             ` Martin Eriksson
2002-01-24 13:01               ` Andy Carlson
2002-01-24 14:42                 ` Martin Eriksson
2002-01-24  1:25           ` Andy Carlson
2002-01-23 10:12 ` AW: " Roland Schwarz
     [not found] <Pine.LNX.4.33.0201261559580.4687-200000@cola.teststation.com>
2002-01-29  2:13 ` Justin A
2002-01-29 21:06   ` Urban Widmark
2002-01-30  0:15     ` Justin A

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=200201232325.AAA12824@webserver.ithnet.com \
    --to=skraw@ithnet.com \
    --cc=akpm@zip.com.au \
    --cc=justin@bouncybouncy.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=naclos@swbell.net \
    --cc=nitrax@giron.wox.org \
    --cc=urban@teststation.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.