From: Wang Jian <lark@linux.net.cn>
To: "Welch, Martyn (GE EntSol,
Intelligent Platforms)" <martyn.welch@gefanuc.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 0/2] Fix register misuse in drivers/net/phy/marvel.c
Date: Thu, 10 Jul 2008 22:32:31 +0800 [thread overview]
Message-ID: <48761D7F.4050502@linux.net.cn> (raw)
In-Reply-To: <1CADFA951940554D86FBD8B24BBFF3A0019BEA37@LONMLVEM08.e2k.ad.ge.com>
Welch, Martyn (GE EntSol, Intelligent Platforms) 写道:
> Wang Jian wrote:
>> It may not be appropriate to post here instead of netdev, but I am
>> using
>> powerpc dev board and I think there will be someone here who has board
>> to test.
>>
>> Wang Jian 写道:
>>> These 2 patches fixed misuse of register for 88e1111.
>>>
>>> Notice: These two patches didn't fix some auto selection problem
>>> yet. I will discuss the problem in seperate email.
>>>
>
> Hi,
>
> I have a board here with a pair of 88e1111's, though I'm not sure how to go about testing these patches. It's not the applying or compiling that the problem, but how to test it...
>
> Do you have any test case in mind?
>
Hi,
The problem I want to fix is:
1. Plug the fiber and start the board in u-boot, the fiber link is
established, you can transfer data using fiber link;
2. boot the kernel (not fixed one), when you "ifconfig ethX up" (ethX
uses 88e1111), the fiber link light goes off, the fiber link is lost;
After apply the patch #1, for the step 2, you can "ifconfig ethX
w.x.y.z" and fiber link is ok. You can use the fiber link to transfer data.
I my case, the chip is in GMII mode. The patch #2 is obvious but I can't
test it myself.
BTW, the two patches doesn't fix the problem when you unplug the fiber
then plug back. That is another problem I have _partially_ fixed by
patch marvell_read_status().
prev parent reply other threads:[~2008-07-10 14:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-10 2:14 [PATCH 0/2] Fix register misuse in drivers/net/phy/marvel.c Wang Jian
2008-07-10 2:41 ` Wang Jian
[not found] ` <1CADFA951940554D86FBD8B24BBFF3A0019BEA37@LONMLVEM08.e2k.ad.ge.com>
2008-07-10 14:32 ` Wang Jian [this message]
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=48761D7F.4050502@linux.net.cn \
--to=lark@linux.net.cn \
--cc=linuxppc-dev@ozlabs.org \
--cc=martyn.welch@gefanuc.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;
as well as URLs for NNTP newsgroup(s).