From: "'Roger Luethi'" <rl@hellgate.ch>
To: "Richard B. Johnson" <root@chaos.analogic.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] #2 VIA Rhine stalls: TxAbort handling
Date: Fri, 17 May 2002 18:25:42 +0200 [thread overview]
Message-ID: <20020517162542.GB1175@k3.hellgate.ch> (raw)
In-Reply-To: <20020517001534.GA3632@k3.hellgate.ch> <Pine.LNX.3.95.1020517084216.4475A-100000@chaos.analogic.com>
> Well, maybe the fashion of the day. Do `grep karound *.c` in
> ../linux/drivers/net and see all the 'workarounds' that exist for
> chip problems. Some of the problems are induced by the coding and
> most are real hardware problems.
Nobody's debating the need for workarounds. I just prefer to look for a
more subtle method before taking out the sledge-hammer several times a
second(!) to reprogram the chip from scratch.
Roger
next prev parent reply other threads:[~2002-05-17 16:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-16 10:03 [PATCH] #2 VIA Rhine stalls: TxAbort handling Shing Chuang
2002-05-16 18:03 ` 'Roger Luethi'
2002-05-16 18:25 ` Richard B. Johnson
2002-05-16 20:31 ` 'Roger Luethi'
2002-05-16 16:39 ` Ivan G.
2002-05-17 2:54 ` [PATCH] #3 VIA Rhine stalls: Wait for the chip? 'Roger Luethi'
2002-05-16 21:05 ` [PATCH] #2 VIA Rhine stalls: TxAbort handling Richard B. Johnson
2002-05-17 0:16 ` 'Roger Luethi'
2002-05-17 12:51 ` Richard B. Johnson
2002-05-17 16:25 ` 'Roger Luethi' [this message]
[not found] <369B0912E1F5D511ACA5003048222B75A3C06E@EXCHANGE2>
[not found] ` <20020518040143.GA9318@k3.hellgate.ch>
2002-05-17 23:13 ` Ivan G.
2002-05-18 19:11 ` 'Roger Luethi'
-- strict thread matches above, loose matches on Subject: below --
2002-05-17 18:46 Manfred Spraul
2002-05-17 19:56 ` 'Roger Luethi'
2002-05-18 10:08 ` David Woodhouse
2002-05-16 3:13 Roger Luethi
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=20020517162542.GB1175@k3.hellgate.ch \
--to=rl@hellgate.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.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