[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20110411140239.646ace73.akpm@linux-foundation.org>
Date: Mon, 11 Apr 2011 14:02:39 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: netdev@...r.kernel.org
Cc: bugzilla-daemon@...zilla.kernel.org,
bugme-daemon@...zilla.kernel.org, Alex Dubov <oakad@...oo.com>,
Grant Likely <grant.likely@...retlab.ca>,
David Daney <ddaney@...iumnetworks.com>
Subject: Re: [Bugme-new] [Bug 33042] New: Marvell 88E1145 phy configured
incorrectly in fiber mode
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Mon, 11 Apr 2011 09:28:18 GMT
bugzilla-daemon@...zilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=33042
>
> Summary: Marvell 88E1145 phy configured incorrectly in fiber
> mode
> Product: Drivers
> Version: 2.5
> Kernel Version: Linux-2.6.39-rc1-00191
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: Network
> AssignedTo: drivers_network@...nel-bugs.osdl.org
> ReportedBy: oakad@...oo.com
> Regression: No
>
>
> On my board, Marvell 88E1145 phy is attached to Freescale gianfar controller.
> Backplane connection is detected by u-boot as 1000/Full fiber mode.
>
> The network works perfectly in u-boot (dhcp, tftp of large files, ntp). Upon
> booting, kernel detects the link as 100/Full and no data can be exchanged over
> the interface.
>
> As a quick fix, I tried setting .read_settings method of the 1145 driver to
> marvell_read_status (instead of genphy_read_status). Now the link is correctly
> detected as 1000/Full, but the data still can not be exchanged.
>
> I assume, there's a configuration bit missing on the kernel side, as there are
> no such problems in u-boot.
>
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists