From: Alex Dubov <oakad@yahoo•com>
To: Andy Fleming <afleming@gmail•com>
Cc: Andrew Morton <akpm@linux-foundation•org>,
David Daney <ddaney@caviumnetworks•com>,
netdev@vger•kernel.org, bugzilla-daemon@bugzilla•kernel.org,
bugme-daemon@bugzilla•kernel.org,
Grant Likely <grant.likely@secretlab•ca>,
Andy Fleming <afleming@freescale•com>
Subject: Re: [Bugme-new] [Bug 33042] New: Marvell 88E1145 phy configured incorrectly in fiber mode
Date: Thu, 14 Apr 2011 00:59:26 -0700 (PDT) [thread overview]
Message-ID: <903944.53826.qm@web37604.mail.mud.yahoo.com> (raw)
In-Reply-To: <BANLkTikH09jMZZk1ZgeQi+HOoeFqgTpdBA@mail.gmail.com>
--- On Thu, 14/4/11, Andy Fleming <afleming@gmail•com> wrote:
>
> I've just rewritten the U-Boot code for PHY management, so
> I'd be
> interested in hearing if this breaks your board. But
> what's
> interesting to me is that, in order for U-Boot to report
> that the link
> is a "fiber" link, something had to set the TSEC_FIBER
> flag, and only
> one PHY in the public source did. This implies to me
> that your board
> isn't supported by mainline U-Boot, and suggests that
> someone may have
> modified the 88e1145 driver. Otherwise, I don't see any
> fiber-related
> differences between the U-Boot 1145 driver, and the Linux
> one.
I had not seen any difference, that's true. But the problem somehow
creeps in.
The u-boot is standard stock u-boot pulled from the recent git,
no special configuration involved.
I actually managed to make kernel transmit stuff by playing with register
values from other marvell phy varieties, but it keeps receiving garbage,
so the link is still not operational.
I tried to prevent kernel from reconfiguring the phy, but to no avail.
It seems very weird to me, because I did quite a lot of testing with
u-boot and network just works on that interface. However, when kernel
starts booting it suddenly looses the ability to talk to it.
I have a copper link attached to the same transceiver and it works fine
all along.
>
>
>
> Reading the configuration from U-Boot is
> straightforward. use the
> "mii" command to read the registers. But don't forget
> to set register
> 22 (16 - mii command only reads hex) to 1, and read all of
> the
> registers that way, too.
I have no recourse but to keep investigating.
>
> You will either need to add some code to detect when the
> PHY is using
> fiber, and change the phydev->port to PORT_FIBRE, or you
> will need to
> add a board-level "fixup" to change the port to PORT_FIBRE
> on your
> board.
>
> Then the PHY driver should use that information to do the
> right configuration.
>
> Andy
>
next prev parent reply other threads:[~2011-04-14 7:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-33042-10286@https.bugzilla.kernel.org/>
2011-04-11 21:02 ` [Bugme-new] [Bug 33042] New: Marvell 88E1145 phy configured incorrectly in fiber mode Andrew Morton
2011-04-11 21:18 ` David Daney
2011-04-12 3:45 ` Alex Dubov
2011-04-12 16:34 ` David Daney
2011-04-13 18:01 ` Andy Fleming
2011-04-14 7:59 ` Alex Dubov [this message]
2011-04-15 20:57 ` Andy Fleming
2011-04-18 5:44 ` Alex Dubov
2011-04-18 6:43 ` Alex Dubov
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=903944.53826.qm@web37604.mail.mud.yahoo.com \
--to=oakad@yahoo$(echo .)com \
--cc=afleming@freescale$(echo .)com \
--cc=afleming@gmail$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=bugme-daemon@bugzilla$(echo .)kernel.org \
--cc=bugzilla-daemon@bugzilla$(echo .)kernel.org \
--cc=ddaney@caviumnetworks$(echo .)com \
--cc=grant.likely@secretlab$(echo .)ca \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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