All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Waugh <twaugh@redhat.com>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Gigabit Ethernet support for forcedeth
Date: Fri, 30 Jul 2004 17:20:23 +0100	[thread overview]
Message-ID: <20040730162023.GD8175@redhat.com> (raw)
In-Reply-To: <410A4A1C.4040608@colorfullife.com>

[-- Attachment #1: Type: text/plain, Size: 801 bytes --]

On Fri, Jul 30, 2004 at 03:16:12PM +0200, Manfred Spraul wrote:

> Tim Waugh wrote:
> 
> >Works fine if I back out that patch.
> >
> > 
> >
> The patch rewrites the phy initialization. Backing it out is not really 
> a solution: I have one report that it fixes the link detection, without 
> the patch no link is detected.

I wasn't suggesting it as a solution, just trying to provide data.
Now you have a report that it breaks link detection. :-)

> Which phy is used by your board? Could you enable dprintk (near line 
> 115) and reload the driver?

I've enabled dprintk and captured *.debug syslog output from a normal
boot.  Here is the result:

http://cyberelk.net/tim/tmp/forcedeth-debug

Hope you can make some sense of it.  Let me know what else I can try.

Tim.
*/

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2004-07-30 16:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-30 10:04 [PATCH] Gigabit Ethernet support for forcedeth Tim Waugh
     [not found] ` <410A4A1C.4040608@colorfullife.com>
2004-07-30 16:20   ` Tim Waugh [this message]
2004-07-30 16:52     ` Manfred Spraul
2004-07-30 17:16       ` Tim Waugh
2004-07-30 17:29         ` Manfred Spraul
2004-08-02 11:51           ` Tim Waugh
  -- strict thread matches above, loose matches on Subject: below --
2004-06-30  5:44 Manfred Spraul
2004-06-30  6:10 ` Jeff Garzik
2004-06-30 16:11   ` Manfred Spraul
2004-06-30 18:55     ` Manfred Spraul
2004-07-02 15:51       ` Jeff Garzik
2004-07-02 19:29         ` Manfred Spraul
2004-07-03  6:17           ` Jeff Garzik
2004-07-04 18:27 ` Pavel Machek

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=20040730162023.GD8175@redhat.com \
    --to=twaugh@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.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.