From: Wang Jian <lark@linux.net.cn>
To: netdev@vger.kernel.org
Cc: Alexandr Smirnov <asmirnov@ru.mvista.com>,
Andy Fleming <afleming@freescale.com>
Subject: [PATCH 0/2] Fix register misuse in drivers/net/phy/marvel.c
Date: Fri, 11 Jul 2008 08:55:18 +0800 [thread overview]
Message-ID: <4876AF76.6020105@linux.net.cn> (raw)
These 2 patches fixed misuse of register for 88e1111.
The problem can be reproduced in my powerpc dev board.
With fiber plugged, start the board in u-boot, the fiber link is
established and data transfer is ok. Booting into kernel with current
marvell.c implementation, and "ifconfig ethX up", the fiber link is lost.
The #1 patch fixed this.
The #2 patch is obvious but I can't test it myself because the board I
have using 88e1111 in GMII mode.
Notice: These two patches didn't fix some auto selection problem yet. I
will discuss the problem in seperate email.
next reply other threads:[~2008-07-11 1:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-11 0:55 Wang Jian [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-16 13:45 [PATCH 0/2] Fix register misuse in drivers/net/phy/marvel.c Wang Jian
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=4876AF76.6020105@linux.net.cn \
--to=lark@linux.net.cn \
--cc=afleming@freescale.com \
--cc=asmirnov@ru.mvista.com \
--cc=netdev@vger.kernel.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 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).