From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Stefan Jeglinski <jeglin@4pi.com>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: ethtool failure with tulip 21143
Date: Mon, 17 Dec 2001 00:38:53 +0100 [thread overview]
Message-ID: <20011216233853.23752@smtp.wanadoo.fr> (raw)
In-Reply-To: <p04330101b842de27485b@[24.163.44.170]>
>A long time ago (2.2.13 or so), I could not use another card on the
>6500 for very long with the de4x5 driver as well. At that time, Paul
>provided a patch for the de4x5 driver which fixed the problem. He
>also described the issue as a cache coherency problem.
Yes, paul's patch is what I'm talking about.
>Well, I wonder if that was the fix that Paul put in. Some time ago
>(early 2.4) I tried the de4x5 driver with this Farallon 10/100 card
>but it worked even more poorly than the tulip driver of that time did.
Yup.
>
>>Try defining CACHE_ALIGN to CAL_32LONG, and DESC_ALIGN to u32 dummy[4]
>>(as in the commented out example).
>
>I will look at the de4x5 code again and try this. It's all vaguely
>familiar to me... Thanks much!
That should be the same patch paul did.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-12-16 23:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-16 17:53 ethtool failure with tulip 21143 Stefan Jeglinski
2001-12-16 18:13 ` Jeff Garzik
2001-12-16 18:37 ` Stefan Jeglinski
2001-12-16 21:59 ` Benjamin Herrenschmidt
2001-12-16 23:31 ` Stefan Jeglinski
2001-12-16 23:38 ` Benjamin Herrenschmidt [this message]
2001-12-27 4:13 ` Stefan Jeglinski
2001-12-27 13:41 ` Kevin B. Hendricks
2001-12-27 15:22 ` Benjamin Herrenschmidt
2001-12-16 18:25 ` Benjamin Herrenschmidt
2001-12-16 21:24 ` Tony 'Nicoya' Mantler
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=20011216233853.23752@smtp.wanadoo.fr \
--to=benh@kernel.crashing.org \
--cc=jeglin@4pi.com \
--cc=linuxppc-dev@lists.linuxppc.org \
/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.