From: Don Fry <brazilnut@us.ibm.com>
To: akpm@osdl.org
Cc: davem@davemloft.net, jgarzik@pobox.com, netdev@oss.sgi.com,
steven.hardy@astrium.eads.net
Subject: Re: [patch 12/13] pcnet32 79C975 fiber fix
Date: Tue, 15 Mar 2005 16:56:30 -0800 [thread overview]
Message-ID: <20050316005630.GA9421@us.ibm.com> (raw)
In-Reply-To: <200503152222.j2FMMiLB016826@shell0.pdx.osdl.net>
I had not seen this problem until now. The patch looks ok and
probably should have been written that way initially. I have been
able to do a quick touch test with a 970A, 971, 972, 973, 975, 976, and
978 (some on ia32 and others on ppc64) without any adverse effects.
The 975 I have is copper not fiber.
Since only bit 12 is needed to enable LED writes, the code could
really be "a->write_bcr(ioaddr, 2, a->read_bcr(ioaddr, 2) | 0x1000);"
During pcnet32_open the ASEL bit is changed anyway.
This change should also be applied to 2.4.30 as well.
On Tue, Mar 15, 2005 at 02:22:48PM -0800, akpm@osdl.org wrote:
>
> From: "HARDY, Steven" <steven.hardy@astrium.eads.net>
>
> I have found a bug in the pcnet32 driver (drivers/net/pcnet32.c) affecting
> all ethernet cards based on the AMD79C975 chip, using the fiber interface.
>
> It's a one line fix, where some config registers get corrupted during
> initialisation (which stops the Fiber interface working with this chip)
>
> This bug was introduced somewhere betweeen 2.4.17 and 2.6.x (noticed whilst
> upgrading to 2.6), and it may affect other chips too. I have checked all
> versions up to 2.6.11-bk6 and they are all broken.
>
> Signed-off-by: Andrew Morton <akpm@osdl.org>
> ---
>
> 25-akpm/drivers/net/pcnet32.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletion(-)
>
> diff -puN drivers/net/pcnet32.c~pcnet32-bug-79c975-fiber-fix drivers/net/pcnet32.c
> --- 25/drivers/net/pcnet32.c~pcnet32-bug-79c975-fiber-fix Tue Mar 15 14:19:55 2005
> +++ 25-akpm/drivers/net/pcnet32.c Tue Mar 15 14:19:55 2005
> @@ -1351,7 +1351,8 @@ pcnet32_probe1(unsigned long ioaddr, int
> printk(KERN_INFO "%s: registered as %s\n", dev->name, lp->name);
> cards_found++;
>
> - a->write_bcr(ioaddr, 2, 0x1002); /* enable LED writes */
> + /* enable LED writes */
> + a->write_bcr(ioaddr, 2, a->read_bcr(ioaddr, 2) | 0x1002);
>
> return 0;
>
> _
>
--
Don Fry
brazilnut@us.ibm.com
next prev parent reply other threads:[~2005-03-16 0:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-15 22:22 [patch 12/13] pcnet32 79C975 fiber fix akpm
2005-03-16 0:56 ` Don Fry [this message]
2005-03-16 1:03 ` Andrew Morton
2005-03-22 19:14 ` Jeff Garzik
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=20050316005630.GA9421@us.ibm.com \
--to=brazilnut@us.ibm.com \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=jgarzik@pobox.com \
--cc=netdev@oss.sgi.com \
--cc=steven.hardy@astrium.eads.net \
/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.