From: Mark Brown <broonie@sirena.org.uk>
To: "Rafał Bilski" <rafalbilski@interia.pl>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: Natsemi DP83815 driver spaming
Date: Tue, 1 May 2007 22:27:51 +0100 [thread overview]
Message-ID: <20070501212750.GC31630@sirena.org.uk> (raw)
In-Reply-To: <46379A7E.3000109@interia.pl>
[-- Attachment #1: Type: text/plain, Size: 940 bytes --]
On Tue, May 01, 2007 at 09:52:30PM +0200, Rafał Bilski wrote:
> > * 2) check for sudden death of the NIC:
> > * It seems that a reference set for this chip went out with incorrect info,
> > * and there exist boards that aren't quite right. An unexpected voltage
> > * drop can cause the PHY to get itself in a weird state (basically reset).
> > * NOTE: this only seems to affect revC chips.
> Code commented out and NIC is working OK. Strange.
> eth0: DSPCFG accepted after 0 usec.
> eth0: link up.
> eth0: Setting full-duplex based on negotiated link capability.
> dspcfg = 0x00000000 np->dspcfg = 0x00005060
Oh, that's entertaining. I have to confess that I've never seen an that
triggered the workaround before - adding the maintainer, Tim Hockin, who
may be able to shed some light on the expected behaviour here?
--
"You grabbed my hand and we fell into it, like a daydream - or a fever."
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 307 bytes --]
next prev parent reply other threads:[~2007-05-01 21:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 20:58 Natsemi DP83815 driver spaming Rafał Bilski
2007-05-01 3:55 ` Andrew Morton
2007-05-01 7:17 ` Rafał Bilski
2007-05-01 8:23 ` Rafał Bilski
2007-05-01 8:35 ` Andrew Morton
2007-05-01 10:40 ` Rafał Bilski
2007-05-01 8:46 ` Mark Brown
2007-05-01 10:25 ` Rafał Bilski
2007-05-01 18:08 ` Mark Brown
2007-05-01 19:10 ` Rafał Bilski
2007-05-01 19:52 ` Rafał Bilski
2007-05-01 21:27 ` Mark Brown [this message]
[not found] ` <b3ece790705011543gdca3a9ei905d3499b6c18dc8@mail.gmail.com>
2007-05-02 5:54 ` Rafał Bilski
[not found] ` <b3ece790705012303x1e5a2d03xddf6c14aec5a99d8@mail.gmail.com>
2007-05-02 6:34 ` Rafał Bilski
2007-05-02 6:51 ` Tim Hockin
2007-05-02 8:22 ` Mark Brown
[not found] ` <b3ece790705020744p2e73bb5fo2c0acad947a5de15@mail.gmail.com>
2007-05-02 20:05 ` Rafał Bilski
2007-05-02 20:48 ` Tim Hockin
2007-05-02 21:41 ` Mark Brown
2007-05-03 6:33 ` Rafał Bilski
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=20070501212750.GC31630@sirena.org.uk \
--to=broonie@sirena.org.uk \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rafalbilski@interia.pl \
/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.