From: Grant Likely <grant.likely@secretlab.ca>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Pantelis Antoniou <pantelis.antoniou@gmail.com>,
Vitaly Bordug <vbordug@ru.mvista.com>,
linuxppc-dev@ozlabs.org, netdev@vger.kernel.org,
Wolfgang Denk <wd@denx.de>
Subject: Re: [RFC] net/fs_enet: send a reset request to the PHY on init
Date: Fri, 4 Sep 2009 09:45:54 -0600 [thread overview]
Message-ID: <fa686aa40909040845v7410446eqe16a537c398252b7@mail.gmail.com> (raw)
In-Reply-To: <4AA1347A.5060702@linutronix.de>
On Fri, Sep 4, 2009 at 9:38 AM, Sebastian Andrzej
Siewior<bigeasy@linutronix.de> wrote:
> Grant Likely wrote:
> > What version of the kernel are you using? The line numbers don't
>>
>> match up with kernel mainline, so I wonder if this is before or after
>> the OF MDIO rework changes.
>
> It is the kernel which was shipped in ads5121's bsp which is 2.6.24.
Okay, I can safely ignore this then. Wolfgang may be interested
though. He's been doing some work to get 5121 support mainlined.
> I have no network support in boot loader so I can't do it there. Doing it at
> phy-probe time sounds reasonable.
> So all other boards are doing this kind of reset in u-boot?
In general I take the approach that as much as possible firmware
should have devices in a sane state before booting the kernel just to
avoid doing board specific fixup stuff in the kernel tree. But this
isn't law, just more of a rule of thumb that I go by. 2nd resort is
to create a board specific platform code file and put it there
(arch/powerpc/platforms/*).
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
prev parent reply other threads:[~2009-09-04 15:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 11:04 [RFC] net/fs_enet: send a reset request to the PHY on init Sebastian Andrzej Siewior
2009-09-03 16:48 ` Grant Likely
2009-09-04 15:38 ` Sebastian Andrzej Siewior
2009-09-04 15:45 ` Grant Likely [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=fa686aa40909040845v7410446eqe16a537c398252b7@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=bigeasy@linutronix.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=pantelis.antoniou@gmail.com \
--cc=vbordug@ru.mvista.com \
--cc=wd@denx.de \
/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).